home.social

#homeasistant — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #homeasistant, aggregated by home.social.

  1. I have 2 main hvac devices in my room.
    The Midea is a heat pump window unit, does heat and AC. But it can't heat when its below 42° F, so there's the electric heater. I have #HomeAsistant automations about this.
    The Midea flags when the filter needs cleaning, HA reminds me. The heater, also connected to HA, doesn't have such a sensor. I want to make a reminder based on run time for it's filters. I'm looking for suggestions on how many run hours to trigger that reminder

  2. I have 2 main hvac devices in my room.
    The Midea is a heat pump window unit, does heat and AC. But it can't heat when its below 42° F, so there's the electric heater. I have #HomeAsistant automations about this.
    The Midea flags when the filter needs cleaning, HA reminds me. The heater, also connected to HA, doesn't have such a sensor. I want to make a reminder based on run time for it's filters. I'm looking for suggestions on how many run hours to trigger that reminder

  3. I have 2 main hvac devices in my room.
    The Midea is a heat pump window unit, does heat and AC. But it can't heat when its below 42° F, so there's the electric heater. I have #HomeAsistant automations about this.
    The Midea flags when the filter needs cleaning, HA reminds me. The heater, also connected to HA, doesn't have such a sensor. I want to make a reminder based on run time for it's filters. I'm looking for suggestions on how many run hours to trigger that reminder

  4. I have 2 main hvac devices in my room.
    The Midea is a heat pump window unit, does heat and AC. But it can't heat when its below 42° F, so there's the electric heater. I have #HomeAsistant automations about this.
    The Midea flags when the filter needs cleaning, HA reminds me. The heater, also connected to HA, doesn't have such a sensor. I want to make a reminder based on run time for it's filters. I'm looking for suggestions on how many run hours to trigger that reminder

  5. Trying to setup home assistant for the first time just because I thought it was easy and I could do it while watching a live stream.

    > Config flow could not be loaded: {"message":"Invalid handler specified"}

    For almost all of the integrations.

    Guess I'll just uninstall it again and come back to it another day when I've more patience dealing with this shit...

    #HomeAsistant

  6. Trying to setup home assistant for the first time just because I thought it was easy and I could do it while watching a live stream.

    > Config flow could not be loaded: {"message":"Invalid handler specified"}

    For almost all of the integrations.

    Guess I'll just uninstall it again and come back to it another day when I've more patience dealing with this shit...

    #HomeAsistant

  7. Trying to setup home assistant for the first time just because I thought it was easy and I could do it while watching a live stream.

    > Config flow could not be loaded: {"message":"Invalid handler specified"}

    For almost all of the integrations.

    Guess I'll just uninstall it again and come back to it another day when I've more patience dealing with this shit...

    #HomeAsistant

  8. Trying to setup home assistant for the first time just because I thought it was easy and I could do it while watching a live stream.

    > Config flow could not be loaded: {"message":"Invalid handler specified"}

    For almost all of the integrations.

    Guess I'll just uninstall it again and come back to it another day when I've more patience dealing with this shit...

    #HomeAsistant

  9. Had a look at what data was available and came up with this card for #HomeAsistant, turns out my car shares plenty, with a few conditional colours and thought on what would be useful at a glance it came out rather well for a first attempt 🤖

    #VW #ID3

  10. Had a look at what data was available and came up with this card for #HomeAsistant, turns out my car shares plenty, with a few conditional colours and thought on what would be useful at a glance it came out rather well for a first attempt 🤖

    #VW #ID3

  11. Had a look at what data was available and came up with this card for #HomeAsistant, turns out my car shares plenty, with a few conditional colours and thought on what would be useful at a glance it came out rather well for a first attempt 🤖

    #VW #ID3

  12. Anyone know a good smart lock that doesnt require an app for setup? The latest #Nuki #HAPodcast episode got me wanting smart locks but the app requirement makes it a non-starter!

    #homeasistant #smarthome #zigbee #ZWave

  13. @derphilipp die iOS App von #homeasistant kann das nativ. #android wahrscheinlich auch. Chatten geht nicht.

  14. @derphilipp die iOS App von #homeasistant kann das nativ. #android wahrscheinlich auch. Chatten geht nicht.

  15. @derphilipp die iOS App von #homeasistant kann das nativ. #android wahrscheinlich auch. Chatten geht nicht.

  16. @derphilipp die iOS App von #homeasistant kann das nativ. #android wahrscheinlich auch. Chatten geht nicht.

  17. @thoralf @ente @jwildeboer Ich hatte ein Problem mit der neuen Remote Backup Funktionalität von #HomeAsistant über WebDAV. Da gibt es definitiv ein File Upload Limit, allerdings habe ich dort Dateien mit 8GB+ synchronisiert bekommen, d.h. das Limit scheint eher bei 10GB zu liegen. Und dürfte ein anderes sein als das File Size Limit (so es ein solches gibt)

  18. @thoralf @ente @jwildeboer Ich hatte ein Problem mit der neuen Remote Backup Funktionalität von #HomeAsistant über WebDAV. Da gibt es definitiv ein File Upload Limit, allerdings habe ich dort Dateien mit 8GB+ synchronisiert bekommen, d.h. das Limit scheint eher bei 10GB zu liegen. Und dürfte ein anderes sein als das File Size Limit (so es ein solches gibt)

  19. @thoralf @ente @jwildeboer Ich hatte ein Problem mit der neuen Remote Backup Funktionalität von #HomeAsistant über WebDAV. Da gibt es definitiv ein File Upload Limit, allerdings habe ich dort Dateien mit 8GB+ synchronisiert bekommen, d.h. das Limit scheint eher bei 10GB zu liegen. Und dürfte ein anderes sein als das File Size Limit (so es ein solches gibt)

  20. @thoralf @ente @jwildeboer Ich hatte ein Problem mit der neuen Remote Backup Funktionalität von #HomeAsistant über WebDAV. Da gibt es definitiv ein File Upload Limit, allerdings habe ich dort Dateien mit 8GB+ synchronisiert bekommen, d.h. das Limit scheint eher bei 10GB zu liegen. Und dürfte ein anderes sein als das File Size Limit (so es ein solches gibt)

  21. @thoralf @ente @jwildeboer Ich hatte ein Problem mit der neuen Remote Backup Funktionalität von #HomeAsistant über WebDAV. Da gibt es definitiv ein File Upload Limit, allerdings habe ich dort Dateien mit 8GB+ synchronisiert bekommen, d.h. das Limit scheint eher bei 10GB zu liegen. Und dürfte ein anderes sein als das File Size Limit (so es ein solches gibt)

  22. Hat hier jemand eine Idee, wie ich in #Homeasistant zählen könnte, wie oft die Spülmaschine oder auch die Waschmaschine gelaufen ist?
    Beide werden mit einem #shelly gemessen.

    Ich hab nicht so recht eine Idee und wäre dankbar über Tipps oder vlt schon erfolgreiche Umsetzungen.

    Danke euch

  23. Hat hier jemand eine Idee, wie ich in #Homeasistant zählen könnte, wie oft die Spülmaschine oder auch die Waschmaschine gelaufen ist?
    Beide werden mit einem #shelly gemessen.

    Ich hab nicht so recht eine Idee und wäre dankbar über Tipps oder vlt schon erfolgreiche Umsetzungen.

    Danke euch

  24. Hat hier jemand eine Idee, wie ich in #Homeasistant zählen könnte, wie oft die Spülmaschine oder auch die Waschmaschine gelaufen ist?
    Beide werden mit einem #shelly gemessen.

    Ich hab nicht so recht eine Idee und wäre dankbar über Tipps oder vlt schon erfolgreiche Umsetzungen.

    Danke euch

  25. Hat hier jemand eine Idee, wie ich in #Homeasistant zählen könnte, wie oft die Spülmaschine oder auch die Waschmaschine gelaufen ist?
    Beide werden mit einem #shelly gemessen.

    Ich hab nicht so recht eine Idee und wäre dankbar über Tipps oder vlt schon erfolgreiche Umsetzungen.

    Danke euch

  26. Hat hier jemand eine Idee, wie ich in #Homeasistant zählen könnte, wie oft die Spülmaschine oder auch die Waschmaschine gelaufen ist?
    Beide werden mit einem #shelly gemessen.

    Ich hab nicht so recht eine Idee und wäre dankbar über Tipps oder vlt schon erfolgreiche Umsetzungen.

    Danke euch

  27. I had previously written most of my sensors using the OLD #HomeAsistant #YAML syntax in one massive "sensor.yaml" file.

    Now I've split it out using the new method, using a bunch of good old !include statements.

    What was a single 600+ line Yaml file is now split into relevant sections! Woop!

  28. I had previously written most of my sensors using the OLD #HomeAsistant #YAML syntax in one massive "sensor.yaml" file.

    Now I've split it out using the new method, using a bunch of good old !include statements.

    What was a single 600+ line Yaml file is now split into relevant sections! Woop!

  29. I had previously written most of my sensors using the OLD #HomeAsistant #YAML syntax in one massive "sensor.yaml" file.

    Now I've split it out using the new method, using a bunch of good old !include statements.

    What was a single 600+ line Yaml file is now split into relevant sections! Woop!

  30. I had previously written most of my sensors using the OLD #HomeAsistant #YAML syntax in one massive "sensor.yaml" file.

    Now I've split it out using the new method, using a bunch of good old !include statements.

    What was a single 600+ line Yaml file is now split into relevant sections! Woop!

  31. I had previously written most of my sensors using the OLD #HomeAsistant #YAML syntax in one massive "sensor.yaml" file.

    Now I've split it out using the new method, using a bunch of good old !include statements.

    What was a single 600+ line Yaml file is now split into relevant sections! Woop!

  32. Does anybody has any experience with this indoor air quality monitor and Home assistant? I'm thinking in getting one.
    #homeasistant #airquality #openhardware

    Indoor Air Quality Monitor
    airgradient.com/indoor/

  33. Does anybody has any experience with this indoor air quality monitor and Home assistant? I'm thinking in getting one.
    #homeasistant #airquality #openhardware

    Indoor Air Quality Monitor
    airgradient.com/indoor/

  34. Does anybody has any experience with this indoor air quality monitor and Home assistant? I'm thinking in getting one.
    #homeasistant #airquality #openhardware

    Indoor Air Quality Monitor
    airgradient.com/indoor/

  35. Does anybody has any experience with this indoor air quality monitor and Home assistant? I'm thinking in getting one.
    #homeasistant #airquality #openhardware

    Indoor Air Quality Monitor
    airgradient.com/indoor/

  36. Run Glances at RBPI startup

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

    If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

    After a bit of googling, I found out there are at least 4 different ways to do it.

    Firstly, I tried to make glances to start using crontab method:

    sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

    It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

    Second try – rc.local:

    I tinkered a bit with rc.local but I gave up quickly.

    Third try – systemd – it worked!

    1. Go to systemd directory

    cd /etc/systemd/system

    2. create a definition file for the service

    sudo nano glances_w.service

    3. Add the following text to glances_w.service file:

    [Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

    Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

    4. Enable and start service

    sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

    5. Check the status of the service

    systemctl status glances_w.service

    It should give you something like:

    Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

    So I had to find it out using:

    groupsgroups tomi

    The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

    Tags: #homeasistant #glances #raspberrypi #systemd

    https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

    #glances #homeasistant #raspberrypi #systemd #then

  37. Run Glances at RBPI startup

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

    If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

    After a bit of googling, I found out there are at least 4 different ways to do it.

    Firstly, I tried to make glances to start using crontab method:

    sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

    It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

    Second try – rc.local:

    I tinkered a bit with rc.local but I gave up quickly.

    Third try – systemd – it worked!

    1. Go to systemd directory

    cd /etc/systemd/system

    2. create a definition file for the service

    sudo nano glances_w.service

    3. Add the following text to glances_w.service file:

    [Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

    Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

    4. Enable and start service

    sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

    5. Check the status of the service

    systemctl status glances_w.service

    It should give you something like:

    Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

    So I had to find it out using:

    groupsgroups tomi

    The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

    Tags: #homeasistant #glances #raspberrypi #systemd

    https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

    #glances #homeasistant #raspberrypi #systemd #then

  38. Run Glances at RBPI startup

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

    If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

    After a bit of googling, I found out there are at least 4 different ways to do it.

    Firstly, I tried to make glances to start using crontab method:

    sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

    It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

    Second try – rc.local:

    I tinkered a bit with rc.local but I gave up quickly.

    Third try – systemd – it worked!

    1. Go to systemd directory

    cd /etc/systemd/system

    2. create a definition file for the service

    sudo nano glances_w.service

    3. Add the following text to glances_w.service file:

    [Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

    Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

    4. Enable and start service

    sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

    5. Check the status of the service

    systemctl status glances_w.service

    It should give you something like:

    Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

    So I had to find it out using:

    groupsgroups tomi

    The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

    Tags: #homeasistant #glances #raspberrypi #systemd

    https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

    #glances #homeasistant #raspberrypi #systemd #then

  39. Run Glances at RBPI startup

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

    If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

    After a bit of googling, I found out there are at least 4 different ways to do it.

    Firstly, I tried to make glances to start using crontab method:

    sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

    It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

    Second try – rc.local:

    I tinkered a bit with rc.local but I gave up quickly.

    Third try – systemd – it worked!

    1. Go to systemd directory

    cd /etc/systemd/system

    2. create a definition file for the service

    sudo nano glances_w.service

    3. Add the following text to glances_w.service file:

    [Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

    Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

    4. Enable and start service

    sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

    5. Check the status of the service

    systemctl status glances_w.service

    It should give you something like:

    Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

    So I had to find it out using:

    groupsgroups tomi

    The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

    Tags: #homeasistant #glances #raspberrypi #systemd

    https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

    #glances #homeasistant #raspberrypi #systemd #then

  40. Run Glances at RBPI startup

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

    If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

    After a bit of googling, I found out there are at least 4 different ways to do it.

    Firstly, I tried to make glances to start using crontab method:

    sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

    It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

    Second try – rc.local:

    I tinkered a bit with rc.local but I gave up quickly.

    Third try – systemd – it worked!

    1. Go to systemd directory

    cd /etc/systemd/system

    2. create a definition file for the service

    sudo nano glances_w.service

    3. Add the following text to glances_w.service file:

    [Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

    Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

    4. Enable and start service

    sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

    5. Check the status of the service

    systemctl status glances_w.service

    It should give you something like:

    Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

    So I had to find it out using:

    groupsgroups tomi

    The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

    Tags: #homeasistant #glances #raspberrypi #systemd

    https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

    #glances #homeasistant #raspberrypi #systemd #then

  41. Tämään klo 14.15 se tapahtui: Öljypoltin sammui tälläerää viimeisen kerran ja #maalämpö -aikakausi alkoi. Eri kätevä kampe tuo Nibe S1255 sarjan invertteripumppu. Saa melko mukavasti #homeasistant -ohjaukseen suoraan integraatiolla ja #modbus tcp:n kautta ilman pilvipalvelua.

    #villentalliprojekti2024

  42. Few years ago (2019?) it was like:

    pip install glances

    And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

    After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

    Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

    1. Create virtual environment in Python just for Glances (venv something something)
      • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
      • probably not needed
      • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
    2. Install Glances
      • <path to venv>/bin/pip3 install glances
    3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
      • <path to venv>/bin/glances -w
    4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
      • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
    5. Install Fastapi (web framework)
      • <path to venv>/bin/pip3 install fastapi
    6. Run Glances again to find out more of stuff is missing (uvicorn)
    7. Install Uvicorn (web server)
      • <path to venv>/bin/pip3 install uvicorn
    8. Run Glances again to find out more of stuff is missing (jinja2)
    9. Install Jinja2 (templating language)
      • <path to venv>/bin/pip3 install jinja2

    But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

    Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

    The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

    Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

    I wonder if there is a tool to monitor CPU that is not CPU intensive…

    Tags: #homeasistant #glances #raspberrypi

    https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

    #glances #homeasistant #homeassistant #raspberrypi

  43. Monitoring RBPi with Glances & Home Assistant in 2024

    If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

    Few years ago (2019?) it was like:

    pip install glances

    And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory serves but it probably doesn’t).

    After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

    Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

    1. Create virtual environment in Python just for Glances (venv something something)
      • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
      • probably not needed
      • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
    2. Install Glances
      • <path to venv>/bin/pip3 install glances
    3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
      • <path to venv>/bin/glances -w
    4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
      • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
    5. Install Fastapi (web framework)
      • <path to venv>/bin/pip3 install fastapi
    6. Run Glances again to find out more of stuff is missing (uvicorn)
    7. Install Uvicorn (web server)
      • <path to venv>/bin/pip3 install uvicorn
    8. Run Glances again to find out more of stuff is missing (jinja2)
    9. Install Jinja2 (templating language)
      • <path to venv>/bin/pip3 install jinja2

    But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

    Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

    The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

    Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

    I wonder if there is a tool to monitor CPU that is not CPU intensive…

    Update: if I don’t access it via web browser (only via Home Assistant), the CPU usage is 12%. Much better.

    Tags: #homeasistant #glances #raspberrypi

    https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

    #glances #homeasistant #homeassistant #raspberrypi

  44. Few years ago (2019?) it was like:

    pip install glances

    And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

    After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

    Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

    1. Create virtual environment in Python just for Glances (venv something something)
      • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
      • probably not needed
      • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
    2. Install Glances
      • <path to venv>/bin/pip3 install glances
    3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
      • <path to venv>/bin/glances -w
    4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
      • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
    5. Install Fastapi (web framework)
      • <path to venv>/bin/pip3 install fastapi
    6. Run Glances again to find out more of stuff is missing (uvicorn)
    7. Install Uvicorn (web server)
      • <path to venv>/bin/pip3 install uvicorn
    8. Run Glances again to find out more of stuff is missing (jinja2)
    9. Install Jinja2 (templating language)
      • <path to venv>/bin/pip3 install jinja2

    But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

    Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

    The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

    Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

    I wonder if there is a tool to monitor CPU that is not CPU intensive…

    Tags: #homeasistant #glances #raspberrypi

    https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

    #glances #homeasistant #homeassistant #raspberrypi

  45. Few years ago (2019?) it was like:

    pip install glances

    And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

    After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

    Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

    1. Create virtual environment in Python just for Glances (venv something something)
      • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
      • probably not needed
      • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
    2. Install Glances
      • <path to venv>/bin/pip3 install glances
    3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
      • <path to venv>/bin/glances -w
    4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
      • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
    5. Install Fastapi (web framework)
      • <path to venv>/bin/pip3 install fastapi
    6. Run Glances again to find out more of stuff is missing (uvicorn)
    7. Install Uvicorn (web server)
      • <path to venv>/bin/pip3 install uvicorn
    8. Run Glances again to find out more of stuff is missing (jinja2)
    9. Install Jinja2 (templating language)
      • <path to venv>/bin/pip3 install jinja2

    But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

    Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

    The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

    Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

    I wonder if there is a tool to monitor CPU that is not CPU intensive…

    Tags: #homeasistant #glances #raspberrypi

    https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

    #glances #homeasistant #homeassistant #raspberrypi