https://www.etcwiki.org/api.php?action=feedcontributions&user=Ddxfish&feedformat=atomETCwiki - User contributions [en]2024-03-29T00:44:14ZUser contributionsMediaWiki 1.33.1https://www.etcwiki.org/index.php?title=Yootheme_-_Enable_Toolbar_on_Mobile&diff=3975Yootheme - Enable Toolbar on Mobile2023-03-24T18:34:12Z<p>Ddxfish: </p>
<hr />
<div>This code snipped enables the Toolbar in Yootheme on mobile mode. Usually the toolbar disappears on mobile mode, which makes the social and toolbar-left and toolbar-right all disappear. <br />
<br />
'''Post this in your Additional CSS'''<br />
.tm-toolbar{display:inherit !important; position:absolute; width:100%; top:0px; z-index:9999}<br />
.tm-header .uk-navbar{margin-top:50px}<br />
.tm-header-mobile .uk-navbar{margin-top:50px}<br />
.tm-header .uk-navbar-sticky nav.uk-navbar{margin-top:10px;}<br />
.tm-header-mobile .uk-navbar-sticky nav.uk-navbar{margin-top:20px;}<br />
.uk-navbar-sticky{padding-top:0 !important}<br />
<br />
===External Resources===<br />
*[https://yootheme.com/support/question/151078 Failed attempt to make toolbar on mobile]<br />
*[https://yootheme.com/support/question/134572 Failed again]<br />
*[https://yootheme.com/support/question/155839 They made it work but PHP modifications required]<br />
<br />
<br />
[[Category:Web Design]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Category:Web_Design&diff=3974Category:Web Design2023-03-24T18:24:54Z<p>Ddxfish: Created page with "web design articles"</p>
<hr />
<div>web design articles</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Yootheme_-_Enable_Toolbar_on_Mobile&diff=3973Yootheme - Enable Toolbar on Mobile2023-03-24T18:24:40Z<p>Ddxfish: </p>
<hr />
<div>This code snipped enables the Toolbar in Yootheme on mobile mode. Usually the toolbar disappears on mobile mode, which makes the social and toolbar-left and toolbar-right all disappear. <br />
<br />
'''Post this in your Additional CSS'''<br />
.tm-toolbar{display:inherit !important; position:absolute; width:100%; top:0px; z-index:9999}<br />
.tm-header .uk-navbar{margin-top:50px}<br />
.tm-header-mobile .uk-navbar{margin-top:50px}<br />
<br />
===External Resources===<br />
*[https://yootheme.com/support/question/151078 Failed attempt to make toolbar on mobile]<br />
*[https://yootheme.com/support/question/134572 Failed again]<br />
*[https://yootheme.com/support/question/155839 They made it work but PHP modifications required]<br />
<br />
<br />
[[Category:Web Design]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3972MediaWiki:Sidebar2023-03-24T18:24:24Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Mycroft|Mycroft<br />
** http://www.etcwiki.org/wiki/Category:Home_Assistant|Home Assistant<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
** http://www.etcwiki.org/wiki/Category:Web_Design|Web Design<br />
*ETCwiki Spotlight<br />
** https://www.etcwiki.org/wiki/Yootheme_-_Enable_Toolbar_on_Mobile| Yootheme - Mobile Toolbar<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_Python_API_Client|Home Assistant - Python API Client<br />
** https://www.etcwiki.org/wiki/Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023|RPi 4 Screen Blanking<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_NUT_UPS_Energy_Tracking|Home Assistant UPS Energy Tracking<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Yootheme_-_Enable_Toolbar_on_Mobile&diff=3971Yootheme - Enable Toolbar on Mobile2023-03-24T18:21:46Z<p>Ddxfish: </p>
<hr />
<div>This code snipped enables the Toolbar in Yootheme on mobile mode. Usually the toolbar disappears on mobile mode, which makes the social and toolbar-left and toolbar-right all disappear. <br />
<br />
'''Post this in your Additional CSS'''<br />
.tm-toolbar{display:inherit !important; position:absolute; width:100%; top:0px; z-index:9999}<br />
.tm-header .uk-navbar{margin-top:50px}<br />
.tm-header-mobile .uk-navbar{margin-top:50px}<br />
<br />
===External Resources===<br />
*[https://yootheme.com/support/question/151078 Failed attempt to make toolbar on mobile]<br />
*[https://yootheme.com/support/question/134572 Failed again]<br />
*[https://yootheme.com/support/question/155839 They made it work but PHP modifications required]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Yootheme_-_Enable_Toolbar_on_Mobile&diff=3970Yootheme - Enable Toolbar on Mobile2023-03-24T18:20:02Z<p>Ddxfish: Created page with "This code snipped enables the Toolbar in Yootheme on mobile mode. Usually the toolbar disappears on mobile mode, which makes the social and toolbar-left and toolbar-right all..."</p>
<hr />
<div>This code snipped enables the Toolbar in Yootheme on mobile mode. Usually the toolbar disappears on mobile mode, which makes the social and toolbar-left and toolbar-right all disappear. <br />
<br />
'''Post this in your Additional CSS'''<br />
.tm-toolbar{display:inherit !important; position:absolute; width:100%; top:0px; z-index:9999}<br />
.tm-header .uk-navbar{margin-top:50px}<br />
.tm-header-mobile .uk-navbar{margin-top:50px}</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3969Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:59:30Z<p>Ddxfish: </p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
==Disable and Enable Screen Blanking on RPi 4==<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
===Description of xset screen blanking commands on raspberry pi===<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
===Auto start===<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Disable RPi screen blanking in console==<br />
'''This section is for an older Pi, I haven't tested on Pi 4'''<br />
<br />
If your screen goes black during command line after 30 minutes or so, you have screen blanking enabled most likely. If you want to turn it off:<br />
<br />
Edit the file '''/etc/kbd/config'''<br />
Change these lines:<br />
BLANK_TIME=0<br />
BLANK_DPMS=off<br />
POWERDOWN_TIME=0<br />
<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/| Screen Blanking - this helped me a ton]<br />
<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/| Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3968Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:58:50Z<p>Ddxfish: </p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
==Disable and Enable Screen Blanking on RPi 4==<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset screen blanking commands on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Disable RPi screen blanking in console==<br />
'''This section is for an older Pi, I haven't tested on Pi 4'''<br />
<br />
If your screen goes black during command line after 30 minutes or so, you have screen blanking enabled most likely. If you want to turn it off:<br />
<br />
Edit the file '''/etc/kbd/config'''<br />
Change these lines:<br />
BLANK_TIME=0<br />
BLANK_DPMS=off<br />
POWERDOWN_TIME=0<br />
<br />
<br />
==Auto start==<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/| Screen Blanking - this helped me a ton]<br />
<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/| Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3967Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:58:08Z<p>Ddxfish: </p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset screen blanking commands on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Disable RPi screen blanking in console==<br />
'''This section is for an older Pi, I haven't tested on Pi 4'''<br />
<br />
If your screen goes black during command line after 30 minutes or so, you have screen blanking enabled most likely. If you want to turn it off:<br />
<br />
Edit the file '''/etc/kbd/config'''<br />
Change these lines:<br />
BLANK_TIME=0<br />
BLANK_DPMS=off<br />
POWERDOWN_TIME=0<br />
<br />
<br />
==Auto start==<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/| Screen Blanking - this helped me a ton]<br />
<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/| Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3966Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:52:46Z<p>Ddxfish: /* External Links */</p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset screen blanking commands on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Auto start==<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/| Screen Blanking - this helped me a ton]<br />
<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/| Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3965Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:52:31Z<p>Ddxfish: /* External Links */</p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset screen blanking commands on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Auto start==<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/|Screen Blanking - this helped me a ton]<br />
<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/|Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3964Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:51:11Z<p>Ddxfish: </p>
<hr />
<div>This is how to disable screen blanking on Raspberry Pi in 2023. This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to actually do screen blanking for some reason. This was my solution.<br />
<br />
* Tested on Raspberry Pi 4 (Jan 18, 2023)<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking on rpi 4 so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset screen blanking commands on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Auto start==<br />
This command does not persist reboots. To run on every boot, create a script and add it to your startup items in your GUI. Or add to crontab -e on startup. Or make a systemd startup script. rc.local may even work if you're lazy.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if the screen goes/doesn't go blank in the way you want. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
* Disable screen blanking in raspi-config<br />
* Disable screensaver app, and in settings uncheck DPMS<br />
* Check system settings (MATE or Lubuntu power settings etc)<br />
* export DISPLAY=:0 is only needed if you run it via crontab or SSH.<br />
<br />
==External Links==<br />
[https://pimylifeup.com/raspberry-pi-disable-screen-blanking/|Screen Blanking - this helped me a ton]<br />
[https://www.geeks3d.com/hacklab/20160108/how-to-disable-the-blank-screen-on-raspberry-pi-raspbian/|Disable screen blanking - includes with auto-start]<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Disable_screensaver_and_screen_blanking_Raspberry_Pi&diff=3963Disable screensaver and screen blanking Raspberry Pi2023-01-18T18:42:42Z<p>Ddxfish: Redirected page to Raspberry Pi 4 - Screen Blanking manually via command line 2023</p>
<hr />
<div>#REDIRECT[[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]<br />
<br />
'''This is for an old Raspberry Pi. See our new documentation here: [[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]'''<br />
<br />
'''This is for an old Raspberry Pi. See our new documentation here: [[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]'''<br />
<br />
This is how to disable screen blanking on the Raspberry Pi running debian (raspbian) which will stop the screensaver (a blank screen) from starting during command line usage.<br />
<br />
==Disable RPi screen blanking in console==<br />
If your screen goes black during command line after 30 minutes or so, you have screen blanking enabled most likely. If you want to turn it off:<br />
<br />
Edit the file '''/etc/kbd/config'''<br />
Change these lines:<br />
BLANK_TIME=0<br />
BLANK_DPMS=off<br />
POWERDOWN_TIME=0<br />
<br />
<br />
<br />
==Disable screensaver and blanking RPi in Pixel Raspbian==<br />
This will disable screen blanking and blacking etc while within X on the Pi. This is for Raspbian Pixel<br />
*edit /etc/xdg/lxsession/LXDE-pi/autostart as root<br />
sudo nano /etc/xdg/lxsession/LXDE-pi/autostart<br />
*Add these lines if they do not already exist<br />
@xset s noblank <br />
@xset s off <br />
@xset -dpms<br />
<br />
<br />
==External Links==<br />
*[https://www.raspberrypi.org/forums/viewtopic.php?t=57552 How to disable screensaver Raspberry Pi] - Same solution as here<br />
*[http://raspberrypi.stackexchange.com/questions/752/how-do-i-prevent-the-screen-from-going-blank StackExchange] - Similar/Same question<br />
<br />
<br />
[[Category: Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Disable_screen_blanking_raspberry_pi&diff=3962Disable screen blanking raspberry pi2023-01-18T18:41:15Z<p>Ddxfish: Redirected page to Raspberry Pi 4 - Screen Blanking manually via command line 2023</p>
<hr />
<div><br />
#REDIRECT[[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]<br />
<br />
The raspberry pi using the most recent Raspbian image will make the display turn off every 30 minutes by default if no input is detected. This is how to disable it:<br />
*edit the file /etc/kbd/config<br />
sudo nano /etc/kbd/config<br />
*Locate: BLANK_TIME=30<br />
**Change value to 0<br />
*Locate: POWERDOWN_TIME=30<br />
**Change value to 0<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Disable_screensaver_and_screen_blanking_Raspberry_Pi&diff=3961Disable screensaver and screen blanking Raspberry Pi2023-01-18T18:40:30Z<p>Ddxfish: </p>
<hr />
<div>'''This is for an old Raspberry Pi. See our new documentation here: [[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]'''<br />
<br />
'''This is for an old Raspberry Pi. See our new documentation here: [[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]'''<br />
<br />
'''This is for an old Raspberry Pi. See our new documentation here: [[Raspberry Pi 4 - Screen Blanking manually via command line 2023]]'''<br />
<br />
This is how to disable screen blanking on the Raspberry Pi running debian (raspbian) which will stop the screensaver (a blank screen) from starting during command line usage.<br />
<br />
==Disable RPi screen blanking in console==<br />
If your screen goes black during command line after 30 minutes or so, you have screen blanking enabled most likely. If you want to turn it off:<br />
<br />
Edit the file '''/etc/kbd/config'''<br />
Change these lines:<br />
BLANK_TIME=0<br />
BLANK_DPMS=off<br />
POWERDOWN_TIME=0<br />
<br />
<br />
<br />
==Disable screensaver and blanking RPi in Pixel Raspbian==<br />
This will disable screen blanking and blacking etc while within X on the Pi. This is for Raspbian Pixel<br />
*edit /etc/xdg/lxsession/LXDE-pi/autostart as root<br />
sudo nano /etc/xdg/lxsession/LXDE-pi/autostart<br />
*Add these lines if they do not already exist<br />
@xset s noblank <br />
@xset s off <br />
@xset -dpms<br />
<br />
<br />
==External Links==<br />
*[https://www.raspberrypi.org/forums/viewtopic.php?t=57552 How to disable screensaver Raspberry Pi] - Same solution as here<br />
*[http://raspberrypi.stackexchange.com/questions/752/how-do-i-prevent-the-screen-from-going-blank StackExchange] - Similar/Same question<br />
<br />
<br />
[[Category: Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3960MediaWiki:Sidebar2023-01-18T18:36:16Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Mycroft|Mycroft<br />
** http://www.etcwiki.org/wiki/Category:Home_Assistant|Home Assistant<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
*ETCwiki Spotlight<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_Python_API_Client|Home Assistant - Python API Client<br />
** https://www.etcwiki.org/wiki/Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023|RPi 4 Screen Blanking<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_NUT_UPS_Energy_Tracking|Home Assistant UPS Energy Tracking<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3959Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:34:13Z<p>Ddxfish: </p>
<hr />
<div>This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to do what I wanted.<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset settings on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if it's what you want. export DISPLAY=:0 is only needed if you run it via crontab or SSH. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.<br />
<br />
<br />
[[Category:Raspberry Pi]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Raspberry_Pi_4_-_Screen_Blanking_manually_via_command_line_2023&diff=3958Raspberry Pi 4 - Screen Blanking manually via command line 20232023-01-18T18:33:46Z<p>Ddxfish: Created page with "This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and ras..."</p>
<hr />
<div>This would go in a crontab or can be manually run via the command line. I wanted my rpi screen to power off at night, then be on all day. Most guides seemed confusing, and raspi-config didn't seem to do what I wanted.<br />
<br />
'''Enable screen blanking on rpi4 so screen will automatically sleep after a while'''<br />
export DISPLAY=:0; xset +dpms; xset s blank; xset s off; xset dpms force on<br />
<br />
'''Disable screen blanking so screen is always on'''<br />
export DISPLAY=:0;xset s noblank; xset s off; xset -dpms<br />
<br />
==Description of xset settings on raspberry pi==<br />
* xset s noblank<br />
** Sets the screen to not blank<br />
* xset s off<br />
** Sets the screensaver off (if applicable)<br />
* xset -dpms<br />
** Turns off Display Power Management (dpms won't trigger the screen to sleep)<br />
* xset +dpms<br />
** This forces Display Power Management to kick in and sleep the monitor after a while<br />
* xset dpms force on<br />
** (not sure) I think this is +dpms but also forces the monitor to turn on.<br />
<br />
==Troubleshooting==<br />
Allow 15 minutes with each setting to see if it's what you want. export DISPLAY=:0 is only needed if you run it via crontab or SSH. There may be other things that blank your screen, like system settings in MATE or other DE's, so look there too.</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_-_Use_light_ring_on_Seeed_Respeaker_4-mic_for_Raspberry_Pi&diff=3957Mycroft - Use light ring on Seeed Respeaker 4-mic for Raspberry Pi2021-11-16T01:38:40Z<p>Ddxfish: </p>
<hr />
<div>This is a Mycroft skill for Raspberry Pi users who have the ***"Seeed Respeaker 4-mic Array for Raspberry Pi"***. The Respeaker 4-mic has a ring of LED lights that Mycroft core does not control. This skill makes the Seeed "pixel ring" on the Respeaker activate various patterns of lights when Mycroft is listening, thinking, or speaking.<br />
<br />
==Mycroft - Respeaker 4-mic Light Ring Control==<br />
<br />
GitHub: https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
<br />
==External Links==<br />
*https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
*https://wiki.seeedstudio.com/ReSpeaker_4_Mic_Array_for_Raspberry_Pi/<br />
*https://github.com/respeaker/seeed-voicecard<br />
*https://mycroft.ai/<br />
<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_-_Use_light_ring_on_Seeed_Respeaker_4-mic_for_Raspberry_Pi&diff=3956Mycroft - Use light ring on Seeed Respeaker 4-mic for Raspberry Pi2021-11-16T01:38:01Z<p>Ddxfish: </p>
<hr />
<div>= Mycroft - Respeaker 4-mic Light Ring Control =<br />
<br />
This is a Mycroft skill for Raspberry Pi users who have the ***"Seeed Respeaker 4-mic Array for Raspberry Pi"***. The Respeaker 4-mic has a ring of LED lights that Mycroft core does not control. This skill makes the Seeed "pixel ring" on the Respeaker activate various patterns of lights when Mycroft is listening, thinking, or speaking.<br />
<br />
GitHub: https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
<br />
==External Links==<br />
*https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
*https://wiki.seeedstudio.com/ReSpeaker_4_Mic_Array_for_Raspberry_Pi/<br />
*https://github.com/respeaker/seeed-voicecard<br />
*https://mycroft.ai/<br />
<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_-_Use_light_ring_on_Seeed_Respeaker_4-mic_for_Raspberry_Pi&diff=3955Mycroft - Use light ring on Seeed Respeaker 4-mic for Raspberry Pi2021-11-16T01:37:49Z<p>Ddxfish: Created page with "= Mycroft - Respeaker 4-mic Light Ring Control = This is a Mycroft skill for Raspberry Pi users who have the ***"Seeed Respeaker 4-mic Array for Raspberry Pi"***. The Respeak..."</p>
<hr />
<div>= Mycroft - Respeaker 4-mic Light Ring Control =<br />
<br />
This is a Mycroft skill for Raspberry Pi users who have the ***"Seeed Respeaker 4-mic Array for Raspberry Pi"***. The Respeaker 4-mic has a ring of LED lights that Mycroft core does not control. This skill makes the Seeed "pixel ring" on the Respeaker activate various patterns of lights when Mycroft is listening, thinking, or speaking.<br />
<br />
***GitHub***: https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
<br />
==External Links==<br />
*https://github.com/ddxfish/picroft-respeaker-4mic-light-ring<br />
*https://wiki.seeedstudio.com/ReSpeaker_4_Mic_Array_for_Raspberry_Pi/<br />
*https://github.com/respeaker/seeed-voicecard<br />
*https://mycroft.ai/<br />
<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_blacklisted_skills_not_working&diff=3954Mycroft blacklisted skills not working2021-11-10T23:16:57Z<p>Ddxfish: </p>
<hr />
<div>To blacklist skills, you have to edit your mycroft.conf file. I had trouble removing some of the default skills in Mycroft and it was simply finding the right names to add to the blacklisted skills section.<br />
<br />
==Find skill name to blacklist==<br />
Find the exact skill name using mycroft-cli-client. Use the Mycroft command:<br />
: skills<br />
<br />
==Blacklist a default Mycroft skill==<br />
Backup your mycroft.conf! Put this in your skills section of the conf. Edit to your needs, this blocks everything. NOTE that final comma after the array.<br />
"blacklisted_skills": ["fallback-query.mycroftai","fallback-unknown.mycroftai","fallback-wolfram-alpha.mycroftai","mycroft-alarm.mycroftai","mycroft-audio-record.mycroftai","mycroft-configuration.mycroftai","mycroft-date-time.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-naptime.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai","mycroft-version-checker.mycroftai"],<br />
<br />
Here is a version that keeps a few critical skills and fallback + wolfram alpha. This is more practical than the line above.<br />
"blacklisted_skills": ["fallback-unknown.mycroftai","mycroft-alarm.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai"],<br />
<br />
After you blacklist, you can remove anything you don't want, or everything at all. Default apps that aren't blacklisted will be reinstalled at next startup of mycroft. You can put this in rm-mycroft-defaults.sh and run it if you want to remove all default skills. Edit the list to your needs. <br />
msm remove mycroft-stop <br />
msm remove mycroft-volume <br />
msm remove mycroft-naptime <br />
msm remove fallback-query <br />
msm remove mycroft-reminder <br />
msm remove mycroft-weather <br />
msm remove mycroft-support-helper <br />
msm remove mycroft-installer <br />
msm remove fallback-wolfram-alpha <br />
msm remove mycroft-alarm <br />
msm remove mycroft-audio-record <br />
msm remove mycroft-pairing <br />
msm remove mycroft-timer <br />
msm remove mycroft-ip <br />
msm remove mycroft-configuration <br />
msm remove mycroft-personal <br />
msm remove mycroft-fallback-duck-duck-go <br />
msm remove mycroft-spelling <br />
msm remove mycroft-playback-control <br />
msm remove mycroft-wiki <br />
msm remove fallback-unknown <br />
msm remove mycroft-speak <br />
msm remove mycroft-version-checker <br />
msm remove mycroft-joke <br />
msm remove mycroft-hello-world <br />
msm remove mycroft-singing <br />
msm remove mycroft-date-time<br />
<br />
==External Resources==<br />
*https://community.mycroft.ai/t/permanently-disable-default-skills/3278/9 - this is where I found the answer<br />
*https://mycroft-ai.gitbook.io/docs/skill-development/faq#how-do-i-disable-a-skill - THIS IS WRONG. Don't use it.<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_blacklisted_skills_not_working&diff=3953Mycroft blacklisted skills not working2021-11-10T23:15:58Z<p>Ddxfish: </p>
<hr />
<div>To blacklist skills, you have to edit your mycroft.conf file. I had trouble removing some of the default skills in Mycroft and it was simply finding the right names to add to the blacklisted skills section.<br />
<br />
==Find skill name to blacklist==<br />
Find the exact skill name using mycroft-cli-client. Use the Mycroft command:<br />
: skills<br />
<br />
==Blacklist a default Mycroft skill==<br />
Backup your mycroft.conf! Put this in your skills section of the conf. Edit to your needs, this blocks everything. NOTE that final comma after the array.<br />
"blacklisted_skills": ["fallback-query.mycroftai","fallback-unknown.mycroftai","fallback-wolfram-alpha.mycroftai","mycroft-alarm.mycroftai","mycroft-audio-record.mycroftai","mycroft-configuration.mycroftai","mycroft-date-time.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-naptime.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai","mycroft-version-checker.mycroftai"],<br />
<br />
Here is a version that keeps a few critical skills and fallback + wolfram alpha. This is more practical than the line above.<br />
"blacklisted_skills": ["fallback-unknown.mycroftai","mycroft-alarm.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai"],<br />
<br />
After you blacklist, you can remove anything you don't want, or everything at all. Default apps that aren't blacklisted will be reinstalled at next startup of mycroft. You can put this in rm-mycroft-defaults.sh and run it if you want to remove all default skills. Edit the list to your needs.<br />
msm remove mycroft-stop <br />
msm remove mycroft-volume <br />
msm remove mycroft-naptime <br />
msm remove fallback-query <br />
msm remove mycroft-reminder <br />
msm remove mycroft-weather <br />
msm remove mycroft-support-helper <br />
msm remove mycroft-installer <br />
msm remove fallback-wolfram-alpha <br />
msm remove mycroft-alarm <br />
msm remove mycroft-audio-record <br />
msm remove mycroft-pairing <br />
msm remove mycroft-timer <br />
msm remove mycroft-ip <br />
msm remove mycroft-configuration <br />
msm remove mycroft-personal <br />
msm remove mycroft-fallback-duck-duck-go <br />
msm remove mycroft-spelling <br />
msm remove mycroft-playback-control <br />
msm remove mycroft-wiki <br />
msm remove fallback-unknown <br />
msm remove mycroft-krem.ddxfish <br />
msm remove mycroft-speak <br />
msm remove mycroft-version-checker <br />
msm remove mycroft-joke <br />
msm remove mycroft-hello-world <br />
msm remove mycroft-singing <br />
msm remove mycroft-date-time<br />
<br />
==External Resources==<br />
*https://community.mycroft.ai/t/permanently-disable-default-skills/3278/9 - this is where I found the answer<br />
*https://mycroft-ai.gitbook.io/docs/skill-development/faq#how-do-i-disable-a-skill - THIS IS WRONG. Don't use it.<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_blacklisted_skills_not_working&diff=3952Mycroft blacklisted skills not working2021-11-04T21:12:06Z<p>Ddxfish: </p>
<hr />
<div>To blacklist skills, you have to edit your mycroft.conf file. I had trouble removing some of the default skills in Mycroft and it was simply finding the right names to add to the blacklisted skills section.<br />
<br />
==Find skill name to blacklist==<br />
Find the exact skill name using mycroft-cli-client. Use the Mycroft command:<br />
: skills<br />
<br />
==Blacklist a default Mycroft skill==<br />
Backup your mycroft.conf! Put this in your skills section of the conf. Edit to your needs, this blocks everything. NOTE that final comma after the array.<br />
"blacklisted_skills": ["fallback-query.mycroftai","fallback-unknown.mycroftai","fallback-wolfram-alpha.mycroftai","mycroft-alarm.mycroftai","mycroft-audio-record.mycroftai","mycroft-configuration.mycroftai","mycroft-date-time.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-naptime.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai","mycroft-version-checker.mycroftai"],<br />
<br />
Here is a version that keeps a few critical skills and fallback + wolfram alpha. This is more practical than the line above.<br />
"blacklisted_skills": ["fallback-unknown.mycroftai","mycroft-alarm.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai"],<br />
<br />
<br />
==External Resources==<br />
*https://community.mycroft.ai/t/permanently-disable-default-skills/3278/9 - this is where I found the answer<br />
*https://mycroft-ai.gitbook.io/docs/skill-development/faq#how-do-i-disable-a-skill - THIS IS WRONG. Don't use it.<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Category:Mycroft&diff=3951Category:Mycroft2021-11-04T20:58:53Z<p>Ddxfish: Created page with "Mycroft is a voice assistant. Forums: https://community.mycroft.ai/"</p>
<hr />
<div>Mycroft is a voice assistant. <br />
<br />
Forums: https://community.mycroft.ai/</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_blacklisted_skills_not_working&diff=3950Mycroft blacklisted skills not working2021-11-04T20:58:08Z<p>Ddxfish: Created page with "To blacklist skills, you have to edit your mycroft.conf file. I had trouble removing some of the default skills in Mycroft and it was simply finding the right names to add to..."</p>
<hr />
<div>To blacklist skills, you have to edit your mycroft.conf file. I had trouble removing some of the default skills in Mycroft and it was simply finding the right names to add to the blacklisted skills section.<br />
<br />
==Find skill name to blacklist==<br />
Find the exact skill name using mycroft-cli-client. Use the Mycroft command:<br />
: skills<br />
<br />
==Blacklist a default Mycroft skill==<br />
Backup your mycroft.conf! Put this in your skills section of the conf. Edit to your needs, this blocks everything. NOTE that final comma after the array.<br />
"blacklisted_skills": ["fallback-query.mycroftai","fallback-unknown.mycroftai","fallback-wolfram-alpha.mycroftai","mycroft-alarm.mycroftai","mycroft-audio-record.mycroftai","mycroft-configuration.mycroftai","mycroft-date-time.mycroftai","mycroft-fallback-duck-duck-go.mycroftai","mycroft-hello-world.mycroftai","mycroft-installer.mycroftai","mycroft-ip.mycroftai","mycroft-joke.mycroftai","mycroft-naptime.mycroftai","mycroft-npr-news.mycroftai","mycroft-personal.mycroftai","mycroft-playback-control.mycroftai","mycroft-reminder.mycroftai","mycroft-singing.mycroftai","mycroft-speak.mycroftai","mycroft-spelling.mycroftai","mycroft-wiki.mycroftai","mycroft-support-helper.mycroftai","mycroft-timer.mycroftai","mycroft-volume.mycroftai","mycroft-weather.mycroftai","mycroft-version-checker.mycroftai"],<br />
<br />
==External Resources==<br />
*https://community.mycroft.ai/t/permanently-disable-default-skills/3278/9 - this is where I found the answer<br />
*https://mycroft-ai.gitbook.io/docs/skill-development/faq#how-do-i-disable-a-skill - THIS IS WRONG. Don't use it.<br />
<br />
[[Category:Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3949MediaWiki:Sidebar2021-10-24T19:40:09Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Mycroft|Mycroft<br />
** http://www.etcwiki.org/wiki/Category:Home_Assistant|Home Assistant<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
*ETCwiki Spotlight<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_Python_API_Client|Home Assistant - Python API Client<br />
** https://etcwiki.org/wiki/Mycroft_Watchdog_Script|Mycroft Watchdog Script<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_NUT_UPS_Energy_Tracking|Home Assistant UPS Energy Tracking<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_Python_API_Client&diff=3948Home Assistant - Python API Client2021-10-24T19:39:17Z<p>Ddxfish: </p>
<hr />
<div>This script allows us to access our Home Assistant server (HASS) through Python scripts. I posted this on GitHub and will keep it more updated there, so please check it out there. <br />
<br />
<br />
== Updated Python API Client == <br />
Go here. It is more updated. <br />
* https://github.com/ddxfish/home-assistant-python-api-client<br />
<br />
<br />
== Use the GitHub Version instead of this ==<br />
Updates get put in GitHub. https://github.com/ddxfish/home-assistant-python-api-client/<br />
<br />
<br />
from requests import get, post<br />
import json <br />
class HassRestAPIClient:<br />
def __init__(self):<br />
#Change to your Home Assistant API URL (ex. http://192.168.1.100:8123/api )<br />
self.hassurl = "http://192.168.1.100:8123/api"<br />
#Make sure you enter your own Long Time Access token (Bearer token) from Home Assistant<br />
self.headers = {<br />
"Authorization": "Bearer BEARERTOKENGOESHERE",<br />
"content-type": "application/json",<br />
} <br />
#Get information from home assistant states<br />
def getHassStates(self, entitysearch="", key="all", exactmatch=0):<br />
url = self.hassurl + "/states"<br />
response = get(url, headers=self.headers)<br />
entities = response.json()<br />
result = []<br />
for entity in entities:<br />
if exactmatch == 0:<br />
if entitysearch.lower() in entity['entity_id'].lower() or entitysearch.lower() in entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
result.append(entity)<br />
if key == "basic":<br />
result.append([entity['entity_id'],entity['attributes']['friendly_name'],entity['state']])<br />
else:<br />
try:<br />
result.append(entity[key])<br />
except KeyError:<br />
try:<br />
result.append(entity['attributes'][key])<br />
except KeyError:<br />
result.append("no key named " + key)<br />
if exactmatch == 1:<br />
if entitysearch.lower() == entity['entity_id'].lower() or entitysearch.lower() == entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
return entity<br />
if key == "basic":<br />
return [entity['entity_id'],entity['attributes']['friendly_name'],entity['state']]<br />
else:<br />
try:<br />
return entity[key]<br />
except KeyError:<br />
try:<br />
return entity['attributes'][key]<br />
except KeyError:<br />
return "no key named " + key<br />
return result <br />
#Custom service call <br />
def callHassService(self, entity_id, service, action):<br />
payload = json.dumps({"entity_id": entity_id})<br />
entityurl = self.hassurl + "/services/" + service + "/" + action<br />
result = post(entityurl, headers=self.headers, data=payload)<br />
return result<br />
<br />
== Examples == <br />
Examples moved to GitHub: https://github.com/ddxfish/home-assistant-python-api-client/blob/master/hass-api-client.py<br />
<br />
== External Links ==<br />
* https://github.com/ddxfish/home-assistant-python-api-client/blob/master/hass-api-client.py - Python API Client - Github - more updated version of this<br />
<br />
<br />
[[Category:Home Assistant]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_Python_API_Client&diff=3947Home Assistant - Python API Client2021-10-24T19:38:19Z<p>Ddxfish: </p>
<hr />
<div>This script allows us to access our Home Assistant server (HASS) through Python scripts. I posted this on GitHub and will keep it more updated there, so please check it out there. <br />
<br />
<br />
== Updated Python API Client == <br />
Go here. It is more updated. <br />
* https://github.com/ddxfish/home-assistant-python-api-client<br />
<br />
<br />
== Use the GitHub Version instead of this ==<br />
<br />
from requests import get, post<br />
import json <br />
class HassRestAPIClient:<br />
def __init__(self):<br />
#Change to your Home Assistant API URL (ex. http://192.168.1.100:8123/api )<br />
self.hassurl = "http://192.168.1.100:8123/api"<br />
#Make sure you enter your own Long Time Access token (Bearer token) from Home Assistant<br />
self.headers = {<br />
"Authorization": "Bearer BEARERTOKENGOESHERE",<br />
"content-type": "application/json",<br />
} <br />
#Get information from home assistant states<br />
def getHassStates(self, entitysearch="", key="all", exactmatch=0):<br />
url = self.hassurl + "/states"<br />
response = get(url, headers=self.headers)<br />
entities = response.json()<br />
result = []<br />
for entity in entities:<br />
if exactmatch == 0:<br />
if entitysearch.lower() in entity['entity_id'].lower() or entitysearch.lower() in entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
result.append(entity)<br />
if key == "basic":<br />
result.append([entity['entity_id'],entity['attributes']['friendly_name'],entity['state']])<br />
else:<br />
try:<br />
result.append(entity[key])<br />
except KeyError:<br />
try:<br />
result.append(entity['attributes'][key])<br />
except KeyError:<br />
result.append("no key named " + key)<br />
if exactmatch == 1:<br />
if entitysearch.lower() == entity['entity_id'].lower() or entitysearch.lower() == entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
return entity<br />
if key == "basic":<br />
return [entity['entity_id'],entity['attributes']['friendly_name'],entity['state']]<br />
else:<br />
try:<br />
return entity[key]<br />
except KeyError:<br />
try:<br />
return entity['attributes'][key]<br />
except KeyError:<br />
return "no key named " + key<br />
return result <br />
#Custom service call <br />
def callHassService(self, entity_id, service, action):<br />
payload = json.dumps({"entity_id": entity_id})<br />
entityurl = self.hassurl + "/services/" + service + "/" + action<br />
result = post(entityurl, headers=self.headers, data=payload)<br />
return result<br />
<br />
<br />
== External Links ==<br />
* https://github.com/ddxfish/home-assistant-python-api-client/blob/master/hass-api-client.py - Python API Client - Github - more updated version of this<br />
<br />
<br />
[[Category:Home Assistant]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_Python_API_Client&diff=3946Home Assistant - Python API Client2021-10-24T19:37:16Z<p>Ddxfish: </p>
<hr />
<div>This script allows us to access our Home Assistant server (HASS) through Python scripts. I posted this on GitHub and will keep it more updated there, so please check it out there. <br />
<br />
<br />
== Updated Python API Client == <br />
Go here. It is more updated.<br />
https://github.com/ddxfish/home-assistant-python-api-client<br />
<br />
<br />
== Original v1 client ==<br />
<br />
from requests import get, post<br />
import json <br />
class HassRestAPIClient:<br />
def __init__(self):<br />
#Change to your Home Assistant API URL (ex. http://192.168.1.100:8123/api )<br />
self.hassurl = "http://192.168.1.100:8123/api"<br />
#Make sure you enter your own Long Time Access token (Bearer token) from Home Assistant<br />
self.headers = {<br />
"Authorization": "Bearer BEARERTOKENGOESHERE",<br />
"content-type": "application/json",<br />
} <br />
#Get information from home assistant states<br />
def getHassStates(self, entitysearch="", key="all", exactmatch=0):<br />
url = self.hassurl + "/states"<br />
response = get(url, headers=self.headers)<br />
entities = response.json()<br />
result = []<br />
for entity in entities:<br />
if exactmatch == 0:<br />
if entitysearch.lower() in entity['entity_id'].lower() or entitysearch.lower() in entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
result.append(entity)<br />
if key == "basic":<br />
result.append([entity['entity_id'],entity['attributes']['friendly_name'],entity['state']])<br />
else:<br />
try:<br />
result.append(entity[key])<br />
except KeyError:<br />
try:<br />
result.append(entity['attributes'][key])<br />
except KeyError:<br />
result.append("no key named " + key)<br />
if exactmatch == 1:<br />
if entitysearch.lower() == entity['entity_id'].lower() or entitysearch.lower() == entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
return entity<br />
if key == "basic":<br />
return [entity['entity_id'],entity['attributes']['friendly_name'],entity['state']]<br />
else:<br />
try:<br />
return entity[key]<br />
except KeyError:<br />
try:<br />
return entity['attributes'][key]<br />
except KeyError:<br />
return "no key named " + key<br />
return result <br />
#Custom service call <br />
def callHassService(self, entity_id, service, action):<br />
payload = json.dumps({"entity_id": entity_id})<br />
entityurl = self.hassurl + "/services/" + service + "/" + action<br />
result = post(entityurl, headers=self.headers, data=payload)<br />
return result<br />
<br />
<br />
== External Links ==<br />
* https://github.com/ddxfish/home-assistant-python-api-client/blob/master/hass-api-client.py - Python API Client - Github - more updated version of this</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_Python_API_Client&diff=3945Home Assistant - Python API Client2021-10-24T19:36:03Z<p>Ddxfish: Created page with "This script allows us to access our Home Assistant server (HASS) through Python scripts. I posted this on GitHub and will keep it more updated there, so please check it out th..."</p>
<hr />
<div>This script allows us to access our Home Assistant server (HASS) through Python scripts. I posted this on GitHub and will keep it more updated there, so please check it out there. <br />
<br />
https://github.com/ddxfish/home-assistant-python-api-client<br />
<br />
<br />
from requests import get, post<br />
import json <br />
class HassRestAPIClient:<br />
def __init__(self):<br />
#Change to your Home Assistant API URL (ex. http://192.168.1.100:8123/api )<br />
self.hassurl = "http://192.168.1.100:8123/api"<br />
#Make sure you enter your own Long Time Access token (Bearer token) from Home Assistant<br />
self.headers = {<br />
"Authorization": "Bearer BEARERTOKENGOESHERE",<br />
"content-type": "application/json",<br />
} <br />
#Get information from home assistant states<br />
def getHassStates(self, entitysearch="", key="all", exactmatch=0):<br />
url = self.hassurl + "/states"<br />
response = get(url, headers=self.headers)<br />
entities = response.json()<br />
result = []<br />
for entity in entities:<br />
if exactmatch == 0:<br />
if entitysearch.lower() in entity['entity_id'].lower() or entitysearch.lower() in entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
result.append(entity)<br />
if key == "basic":<br />
result.append([entity['entity_id'],entity['attributes']['friendly_name'],entity['state']])<br />
else:<br />
try:<br />
result.append(entity[key])<br />
except KeyError:<br />
try:<br />
result.append(entity['attributes'][key])<br />
except KeyError:<br />
result.append("no key named " + key)<br />
if exactmatch == 1:<br />
if entitysearch.lower() == entity['entity_id'].lower() or entitysearch.lower() == entity['attributes']['friendly_name'].lower():<br />
if key == "all":<br />
return entity<br />
if key == "basic":<br />
return [entity['entity_id'],entity['attributes']['friendly_name'],entity['state']]<br />
else:<br />
try:<br />
return entity[key]<br />
except KeyError:<br />
try:<br />
return entity['attributes'][key]<br />
except KeyError:<br />
return "no key named " + key<br />
return result <br />
#Custom service call <br />
def callHassService(self, entity_id, service, action):<br />
payload = json.dumps({"entity_id": entity_id})<br />
entityurl = self.hassurl + "/services/" + service + "/" + action<br />
result = post(entityurl, headers=self.headers, data=payload)<br />
return result<br />
<br />
<br />
== External Links ==<br />
* https://github.com/ddxfish/home-assistant-python-api-client/blob/master/hass-api-client.py - Python API Client - Github - more updated version of this</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3944MediaWiki:Sidebar2021-10-24T19:31:54Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Mycroft|Mycroft<br />
** http://www.etcwiki.org/wiki/Category:Home_Assistant|Home Assistant<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
*ETCwiki Spotlight<br />
** https://etcwiki.org/wiki/Mycroft_Watchdog_Script|Mycroft Watchdog Script<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** https://www.etcwiki.org/wiki/Home_Assistant_-_NUT_UPS_Energy_Tracking|Home Assistant UPS Energy Tracking<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Category:Home_Assistant&diff=3943Category:Home Assistant2021-10-24T19:30:04Z<p>Ddxfish: Created page with "https://www.home-assistant.io/"</p>
<hr />
<div>https://www.home-assistant.io/</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3942Home Assistant - NUT UPS Energy Tracking2021-10-24T19:29:45Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
Platform: Linux (Debian)<br />
Skill level: Medium<br />
Time required: 30-90 minutes<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 15<br />
pollinterval = 15<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 25<br />
<br />
(optional) If your UPS goes stale, add or change this line<br />
MAXAGE 25<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Create template to calculate watts ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "<nowiki>{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}</nowiki>"<br />
state_class: measurement<br />
device_class: power<br />
<br />
=== Create a calculation of energy usage ===<br />
This interprets your Watt sensor we just made every so often (30 sec for me) and calculates the total energy used in Wh or kWh. This will not be an exact number, but it should be pretty close.<br />
<br />
sensor:<br />
- platform: integration<br />
source: sensor.ups_office_usage<br />
name: Office UPS Used<br />
method: left<br />
round: 6<br />
<br />
=== Track Energy of UPS in Home Assistant ===<br />
Bunch of options here. <br />
# Configuration > Energy > Add the sensor.ups_office_usage<br />
# Dashboard > Add Entities card > add our sensors<br />
<br />
== Troubleshooting == <br />
To test your setup, open a terminal and type<br />
upsc cyberpowerb<br />
or <br />
upsc cyberpowerb@192.168.1.101<br />
<br />
'''Connection Refused'''<br />
Check your firewall. Check your upsd.conf for syntax. No colon to separate the listen port in upsd.conf. Restart your NUT services like above. <br />
<br />
<br />
== External Links ==<br />
* https://networkupstools.org/ - Network UPS Tools<br />
* https://www.home-assistant.io/integrations/nut/ - Home Assistant - Network UPS Tools (NUT)<br />
* https://raspberrypi.stackexchange.com/questions/66611/nut-cyberpower-data-stale - Dealing with stale data <br />
* https://www.home-assistant.io/integrations/integration/ - Home Assistant - integrations and what method: left means<br />
* https://www.reddit.com/r/homeassistant/comments/p1z19p/want_to_add_ups_to_the_new_energy_monitoring/ - Got me through some rough times learning to pull sensor values<br />
<br />
[[Category:Home Assistant]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3941Home Assistant - NUT UPS Energy Tracking2021-10-24T19:23:25Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 15<br />
pollinterval = 15<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 25<br />
<br />
(optional) If your UPS goes stale, add or change this line<br />
MAXAGE 25<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Create template to calculate watts ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "<nowiki>{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}</nowiki>"<br />
state_class: measurement<br />
device_class: power<br />
<br />
=== Create a calculation of energy usage ===<br />
This interprets your Watt sensor we just made every so often (30 sec for me) and calculates the total energy used in Wh or kWh. This will not be an exact number, but it should be pretty close.<br />
<br />
sensor:<br />
- platform: integration<br />
source: sensor.ups_office_usage<br />
name: Office UPS Used<br />
method: left<br />
round: 6<br />
<br />
=== Track Energy of UPS in Home Assistant ===<br />
Bunch of options here. <br />
# Configuration > Energy > Add the sensor.ups_office_usage<br />
# Dashboard > Add Entities card > add our sensors<br />
<br />
<br />
== External Links ==<br />
* https://networkupstools.org/ - Network UPS Tools<br />
* https://www.home-assistant.io/integrations/nut/ - Home Assistant - Network UPS Tools (NUT)<br />
* https://raspberrypi.stackexchange.com/questions/66611/nut-cyberpower-data-stale - Dealing with stale data <br />
* https://www.home-assistant.io/integrations/integration/ - Home Assistant - integrations and what method: left means<br />
* https://www.reddit.com/r/homeassistant/comments/p1z19p/want_to_add_ups_to_the_new_energy_monitoring/ - Got me through some rough times learning to pull sensor values</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3940Home Assistant - NUT UPS Energy Tracking2021-10-24T19:18:59Z<p>Ddxfish: /* Create template to calculate watts */</p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 15<br />
pollinterval = 15<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 25<br />
<br />
(optional) If your UPS goes stale, add or change this line<br />
MAXAGE 25<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Create template to calculate watts ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "<nowiki>{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}</nowiki>"<br />
state_class: measurement<br />
device_class: power<br />
<br />
=== Create a calculation of energy usage ===<br />
This interprets your Watt sensor we just made every so often (30 sec for me) and calculates the total energy used in Wh or kWh. This will not be an exact number, but it should be pretty close.<br />
<br />
sensor:<br />
- platform: integration<br />
source: sensor.ups_office_usage<br />
name: Office UPS Used<br />
method: left<br />
round: 6<br />
<br />
=== Track Energy of UPS in Home Assistant ===<br />
Bunch of options here. <br />
# Configuration > Energy > Add the sensor.ups_office_usage<br />
# Dashboard > Add Entities card > add our sensors</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3939Home Assistant - NUT UPS Energy Tracking2021-10-24T19:18:24Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 15<br />
pollinterval = 15<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 25<br />
<br />
(optional) If your UPS goes stale, add or change this line<br />
MAXAGE 25<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Create template to calculate watts ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}"<br />
state_class: measurement<br />
device_class: power<br />
<br />
=== Create a calculation of energy usage ===<br />
This interprets your Watt sensor we just made every so often (30 sec for me) and calculates the total energy used in Wh or kWh. This will not be an exact number, but it should be pretty close.<br />
<br />
sensor:<br />
- platform: integration<br />
source: sensor.ups_office_usage<br />
name: Office UPS Used<br />
method: left<br />
round: 6<br />
<br />
=== Track Energy of UPS in Home Assistant ===<br />
Bunch of options here. <br />
# Configuration > Energy > Add the sensor.ups_office_usage<br />
# Dashboard > Add Entities card > add our sensors</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3938Home Assistant - NUT UPS Energy Tracking2021-10-24T19:16:15Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 30<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) You may want to change polling to be less frequent<br />
POLLFREQ 15<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 30<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Create template to calculate watts ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}"<br />
state_class: measurement<br />
device_class: power<br />
<br />
=== Create a calculation of energy usage ===<br />
This interprets your Watt sensor we just made every so often (30 sec for me) and calculates the total energy used in Wh or kWh. This will not be an exact number, but it should be pretty close.<br />
<br />
sensor:<br />
- platform: integration<br />
source: sensor.ups_office_usage<br />
name: Office UPS Used<br />
method: left<br />
round: 6<br />
<br />
=== Track Energy of UPS in Home Assistant ===<br />
Bunch of options here. <br />
# Configuration > Energy > Add the sensor.ups_office_usage<br />
# Dashboard > Add Entities card > add our sensors</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3937Home Assistant - NUT UPS Energy Tracking2021-10-24T18:52:56Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 30<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) You may want to change polling to be less frequent<br />
POLLFREQ 15<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 30<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Edit configuration.yaml ===<br />
This is where you may have to edit things to your needs. My UPS doesn't have a Watt reading. I take the max load of the UPS which is 600W and multiply it by the percentage given me by sensor.cyberpowerb_load. Note, my load percentage is actually an integer 0-100. To make up for this I multiply by 6 instead of 600 for my watts.<br />
template:<br />
- sensor: <br />
- name: UPS Office usage<br />
unit_of_measurement: kW<br />
state: "{{ states('sensor.cyberpowerb_load') | float * 6 / 1000 }}"<br />
state_class: measurement<br />
device_class: power</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3936Home Assistant - NUT UPS Energy Tracking2021-10-24T18:49:10Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 30<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) You may want to change polling to be less frequent<br />
POLLFREQ 15<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 30<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Home Assistant UPS Energy Tracking ==<br />
<br />
=== Add a NUT UPS to Home Assistant ===<br />
Log into your Home Assistant web interface.<br />
* Configuration > Integrations > Add Integration<br />
* Find or search for NUT in the list (Network UPS Tools) and add<br />
* Enter your server information we created above<br />
** Hostname is the ip of the server in the LISTEN line usually<br />
** User is local_mon (from upsd.users)<br />
** Pass is mysupersecretpass (upsd.users)<br />
* For my UPS I track sensor.cyberpowerb_load in the list of sensors to enable<br />
** My Sensor shows up as a load percentage (or really an integer 0-100)<br />
<br />
=== Edit configuration.yaml ===<br />
template:<br />
- sensor: <br />
- name: UPS LR usage<br />
unit_of_measurement: kW<br />
state: "{{ states('sensor.cyberpowera_load') | float * 6 / 1000 }}"<br />
state_class: measurement<br />
device_class: power</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3935Home Assistant - NUT UPS Energy Tracking2021-10-24T18:30:37Z<p>Ddxfish: </p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Network UPS Tools ==<br />
<br />
=== Install Network UPS Tools ===<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
=== Edit /etc/nut/nut.conf ===<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
=== Edit /etc/nut/ups.conf ===<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 30<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
=== Edit /etc/nut/upsd.conf ===<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
=== Edit /etc/nut/upsd.users ===<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
=== Edit /etc/nut/upsmon.conf ===<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(optional) You may want to change polling to be less frequent<br />
POLLFREQ 15<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 30<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno<br />
<br />
=== Restart NUT Services === <br />
This is for systemctl based distros of course.<br />
systemctl restart nut-driver<br />
systemctl restart nut-server<br />
systemctl restart nut-monitor<br />
<br />
=== Query NUT Server for info ===<br />
This will poll the ups for available monitoring stuff.<br />
upsc cyberpowerb@localhost<br />
<br />
== Add UPS to Home Assistant ==</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Home_Assistant_-_NUT_UPS_Energy_Tracking&diff=3934Home Assistant - NUT UPS Energy Tracking2021-10-24T18:22:26Z<p>Ddxfish: Created page with "If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking..."</p>
<hr />
<div>If you have a UPS (Uninterruptible Power Supply) that has either a USB connection or ethernet connection, you can likely add it to Home Assistant Server as an energy tracking device. This guide is generic enough to work with most USB UPS but I am using a Cyberpower CP1000, and have 2 of them showing up as an energy tracking device in my Home Assistant Energy section.<br />
<br />
== Install NUT ==<br />
Network UPS Tools also called NUT is the tool we run on Linux to track UPS features. <br />
sudo apt update<br />
sudo apt install nut<br />
<br />
== Edit /etc/nut/nut.conf ==<br />
The default mode is none, so lets change it to standalone in this file<br />
MODE=standalone<br />
<br />
== Edit /etc/nut/ups.conf ==<br />
We need to add our UPS to this file so NUT knows what driver to use. Add this section to your ups.conf. Name your ups in the square brackets, it doesn't have to say cyberpowerb, this is just mine.<br />
[cyberpowerb]<br />
driver = usbhid-ups<br />
port = auto<br />
desc = "Cyberpower CP1000 B"<br />
pollfreq = 30<br />
<br />
If you are having detection problems, add this line to your ups.conf config just under the driver line. Replace with your UPS vendor ID (find via lsusb)<br />
vendorid = 0764<br />
<br />
== Edit /etc/nut/upsd.conf ==<br />
Add a LISTEN directive, you can have more than one. Port separated by a space. Default is 3493. You may not want to open your LAN IP here.<br />
LISTEN 192.168.1.100 3493<br />
LISTEN 127.0.0.1 3493<br />
<br />
== Edit /etc/nut/upsd.users ==<br />
Add this to create a user that can read UPS stats.<br />
[local_mon]<br />
password = mysupersecretpass<br />
upsmon master<br />
<br />
== Edit /etc/nut/upsmon.conf ==<br />
Add your UPS to the bottom to be monitored<br />
MONITOR cyberpowerb@localhost 1 local_mon mysupersecretpass master<br />
<br />
(otional) You may want to change polling to be less frequent<br />
POLLFREQ 15<br />
<br />
(optional) If your UPS goes stale, change when it assumes it is dead<br />
DEADTIME 30<br />
<br />
(optional) I stopped the computer from turning off the UPS on reboot by adding "no" or anything else to the end<br />
POWERDOWNFLAG /etc/killpowerno</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_Watchdog_Script&diff=3933Mycroft Watchdog Script2021-10-19T17:44:02Z<p>Ddxfish: </p>
<hr />
<div>If you run Mycroft in Docker, you may have seen a ton of errors when it tries to connect to the Messagebus. I get '''Errno 111 Connection Refused''' on Mycroft a ton. In my situation, all I needed to do was /opt/mycroft/./stop-mycroft.sh and then /opt/mycroft/./start-mycroft.sh all and things would start working again. If this is your case too, try this watchdog script inside your Mycroft container.<br />
<br />
=== Add watchdog.sh to /opt/mycroft/startup.sh ===<br />
#!/bin/bash<br />
source /opt/mycroft/.venv/bin/activate<br />
/opt/mycroft/./start-mycroft.sh all<br />
/opt/mycroft/./watchdog.sh &<br />
tail -f /var/log/mycroft/*.log<br />
<br />
<br />
=== /opt/mycroft/watchdog.sh ===<br />
#!/bin/bash<br />
# If you run mycroft in docker you may get Errno 111: Connection Refused<br />
# On my container, a simple ./mycroft-stop and ./mycroft-start all fixes Error 111<br />
# This script checks your audio.log for Error 111 and will restart the mycroft service if it occurs<br />
# put the script in your container, then edit /opt/mycroft/startup.sh <br />
# Add your background watchdog script after mycroft starts in startup.sh, like: /opt/mycroft/./watchdog.sh &<br />
while true<br />
do<br />
thetime=`date +%s`<br />
echo watchdogtest $thetime | tee -a /var/log/mycroft/audio.log<br />
sleep 20<br />
oneelevens=`cat /var/log/mycroft/audio.log | sed -n "/$thetime/,$p" | grep -c "Errno 111"`<br />
echo "Watchdog: checking now" | tee -a /var/log/mycroft/audio.log<br />
if [[ $oneelevens -gt 0 ]]; then<br />
cd /opt/mycroft<br />
./mycroft-stop<br />
sleep 10<br />
./mycroft-start all<br />
echo "Watchdog: mycroft restart attempt finished $oneelevens" | tee -a /var/log/mycroft/audio.log<br />
else<br />
echo "Watchdog: mycroft was found without errors $oneelevens" | tee -a /var/log/mycroft/audio.log<br />
fi<br />
sleep 90<br />
done<br />
<br />
=== External Links ===<br />
* [https://gist.github.com/ddxfish/2f9a29aa589c2143cacefa954e767c01 Github mycroft watchdog script ]<br />
<br />
[[Category: Mycroft]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3932MediaWiki:Sidebar2021-10-19T17:43:30Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
** http://www.etcwiki.org/wiki/Category:Mycroft|Mycroft<br />
*ETCwiki Spotlight<br />
** https://etcwiki.org/wiki/Mycroft_Watchdog_Script|Mycroft Watchdog Script<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Mycroft_Watchdog_Script&diff=3931Mycroft Watchdog Script2021-10-19T17:41:12Z<p>Ddxfish: Created page with "If you run Mycroft in Docker, you may have seen a ton of errors when it tries to connect to the Messagebus. I get '''Errno 111 Connection Refused''' on Mycroft a ton. In my si..."</p>
<hr />
<div>If you run Mycroft in Docker, you may have seen a ton of errors when it tries to connect to the Messagebus. I get '''Errno 111 Connection Refused''' on Mycroft a ton. In my situation, all I needed to do was /opt/mycroft/./stop-mycroft.sh and then /opt/mycroft/./start-mycroft.sh all and things would start working again. If this is your case too, try this watchdog script inside your Mycroft container.<br />
<br />
=== Add watchdog.sh to /opt/mycroft/startup.sh ===<br />
#!/bin/bash<br />
source /opt/mycroft/.venv/bin/activate<br />
/opt/mycroft/./start-mycroft.sh all<br />
/opt/mycroft/./watchdog.sh &<br />
tail -f /var/log/mycroft/*.log<br />
<br />
<br />
=== /opt/mycroft/watchdog.sh ===<br />
#!/bin/bash<br />
# If you run mycroft in docker you may get Errno 111: Connection Refused<br />
# On my container, a simple ./mycroft-stop and ./mycroft-start all fixes Error 111<br />
# This script checks your audio.log for Error 111 and will restart the mycroft service if it occurs<br />
# put the script in your container, then edit /opt/mycroft/startup.sh <br />
# Add your background watchdog script after mycroft starts in startup.sh, like: /opt/mycroft/./watchdog.sh &<br />
while true<br />
do<br />
thetime=`date +%s`<br />
echo watchdogtest $thetime | tee -a /var/log/mycroft/audio.log<br />
sleep 20<br />
oneelevens=`cat /var/log/mycroft/audio.log | sed -n "/$thetime/,$p" | grep -c "Errno 111"`<br />
echo "Watchdog: checking now" | tee -a /var/log/mycroft/audio.log<br />
if [[ $oneelevens -gt 0 ]]; then<br />
cd /opt/mycroft<br />
./mycroft-stop<br />
sleep 10<br />
./mycroft-start all<br />
echo "Watchdog: mycroft restart attempt finished $oneelevens" | tee -a /var/log/mycroft/audio.log<br />
else<br />
echo "Watchdog: mycroft was found without errors $oneelevens" | tee -a /var/log/mycroft/audio.log<br />
fi<br />
sleep 90<br />
done<br />
<br />
=== External Links ===<br />
* [https://gist.github.com/ddxfish/2f9a29aa589c2143cacefa954e767c01 Github mycroft watchdog script ]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3930MediaWiki:Sidebar2021-07-28T23:51:38Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
*ETCwiki Spotlight<br />
** http://www.etcwiki.org/wiki/Setup_php-fpm_7_with_Apache_on_Debian_9_Stretch|Setup php-fpm 7 with Apache on Debian 9 Stretch<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** http://www.etcwiki.org/wiki/Install_Synergy_Raspberry_Pi_3_-_January_2017|Install Synergy Raspberry Pi 3 - January 2017<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://github.com/ddxfish|It's all good code, mostly</div>Ddxfishhttps://www.etcwiki.org/index.php?title=MediaWiki:Sidebar&diff=3929MediaWiki:Sidebar2020-06-03T15:24:09Z<p>Ddxfish: </p>
<hr />
<div>* ETCwiki Menu<br />
** mainpage|ETCwiki Home<br />
** Special:RecentChanges|Recent<br />
** Special:Allpages|All Pages<br />
* Popular Categories<br />
** http://www.etcwiki.org/wiki/Category:Bitcoin|Bitcoin<br />
** http://www.etcwiki.org/wiki/Category:Hardware|Hardware<br />
** http://www.etcwiki.org/wiki/Category:Internet|Internet<br />
** http://www.etcwiki.org/wiki/Category:Linux|Linux<br />
** http://www.etcwiki.org/wiki/Category:Raspberry_Pi|Raspberry Pi<br />
** http://www.etcwiki.org/wiki/Category:Software|Software<br />
** http://www.etcwiki.org/wiki/Category:Video_Games|Video Games<br />
*ETCwiki Spotlight<br />
** http://www.etcwiki.org/wiki/Setup_php-fpm_7_with_Apache_on_Debian_9_Stretch|Setup php-fpm 7 with Apache on Debian 9 Stretch<br />
** http://www.etcwiki.org/wiki/How_many_sunflower_seeds_are_in_a_bag%3F|How many sunflower seeds are in a bag?<br />
** http://www.etcwiki.org/wiki/Fallout:_New_Vegas_Cheats_and_Console|Fallout:New Vegas Cheats and Console<br />
** http://www.etcwiki.org/wiki/RichCopy_Guide|Richcopy Guide<br />
** http://www.etcwiki.org/wiki/Install_Synergy_Raspberry_Pi_3_-_January_2017|Install Synergy Raspberry Pi 3 - January 2017<br />
*Partners<br />
** https://www.beachsidetechnology.com/|WordPress Security and Web Design<br />
** https://thefemininjaproject.com/|The FemiNinja Project</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Use_htaccess_to_request_HTTPS_version_of_images_for_mixed_content_warning_in_SSL&diff=3928Use htaccess to request HTTPS version of images for mixed content warning in SSL2020-06-03T15:13:10Z<p>Ddxfish: </p>
<hr />
<div>You are using some web host to serve your website. You added an SSL certificate and now you can get your site properly loading on HTTPS. You now notice that you have links on your site to HTTP versions of your images and downloads. <br />
<br />
This article is to avoid having to rewrite all of your URL's in your website to serve secure versions of your content. This method does not use Rewrite's. <br />
<br />
'''Open .htaccess and add this line'''<br />
<IfModule mod_headers.c><br />
Header always set Content-Security-Policy "upgrade-insecure-requests;"<br />
</IfModule><br />
<br />
==External Links==<br />
*[https://help.dreamhost.com/hc/en-us/articles/215364618#content-security-policy Dreamhost htaccess stuff] - This is where I found this answer<br />
*[https://stackoverflow.com/questions/35112266/whats-correct-htaccess-rule-to-redirect-mixed-content-to-https StackOverflow Content-Security-Policy] - same answer but on StackOverflow<br />
[[Category:Internet]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Use_htaccess_to_request_HTTPS_version_of_images_for_mixed_content_warning_in_SSL&diff=3927Use htaccess to request HTTPS version of images for mixed content warning in SSL2020-06-03T15:12:57Z<p>Ddxfish: </p>
<hr />
<div>You are using some web host to serve your website. You added an SSL certificate and now you can get your site properly loading on HTTPS. You now notice that you have links on your site to HTTP versions of your images and downloads. <br />
<br />
This article is to avoid having to rewrite all of your URL's in your website to serve secure versions of your content. This method does not use Rewrite's. <br />
<br />
'''Open .htaccess and add this line'''<br />
<IfModule mod_headers.c><br />
Header always set Content-Security-Policy "upgrade-insecure-requests;"<br />
</IfModule><br />
<br />
==External Links==<br />
*[https://help.dreamhost.com/hc/en-us/articles/215364618#content-security-policy Dreamhost htaccess stuff] - This is where I found this answer<br />
*[https://stackoverflow.com/questions/35112266/whats-correct-htaccess-rule-to-redirect-mixed-content-to-https StackOverflow Content-Security-Policy] - same answer but on StackOverflow<br />
[[Category:Internet]]</div>Ddxfishhttps://www.etcwiki.org/index.php?title=Use_htaccess_to_request_HTTPS_version_of_images_for_mixed_content_warning_in_SSL&diff=3926Use htaccess to request HTTPS version of images for mixed content warning in SSL2020-03-31T00:32:53Z<p>Ddxfish: </p>
<hr />
<div>You are using some web host to serve your website. You added an SSL certificate and now you can get your site properly loading on HTTPS. You now notice that you have links on your site to HTTP versions of your images and downloads. <br />
<br />
This article is to avoid having to rewrite all of your URL's in your website to serve secure versions of your content. This method does not use Rewrite's. <br />
<br />
'''Open .htaccess and add this line'''<br />
Header always set Content-Security-Policy "upgrade-insecure-requests;"<br />
<br />
==External Links==<br />
*[https://help.dreamhost.com/hc/en-us/articles/215364618#content-security-policy Dreamhost htaccess stuff] - This is where I found this answer<br />
*[https://stackoverflow.com/questions/35112266/whats-correct-htaccess-rule-to-redirect-mixed-content-to-https StackOverflow Content-Security-Policy] - same answer but on StackOverflow<br />
[[Category:Internet]]</div>Ddxfish