#homeasistant — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #homeasistant, aggregated by home.social.
-
Ich habe bei #Homeasistant schon seit langem den unschönen Effekt, dass bei Neuladen der Konfiguration, z.B. nach Änderungen an der configuration.yaml, #Ausreißer entstehen. Dies betrifft ausschließlich #Entitäten, die ich in der configuration.yaml angelegt habe, immer die Gleichen, aber bei Weitem nicht alle.
Leider ergibt sich da immer ein Rattenschwanz, da ich #HA sehr stark für das Erfassen von Werten und Statistiken nutze (deshalb auch aus meiner Calc-Tabelle für die Hausverbäuche etc. historische Daten von der Zeit vor HA importiert habe) und diverse Berechnungen aus anderen Entitäten machen lasse. Wenn eine daran beteiligte Entität einen Ausreißer produziert, haben logischerweise alle daraus berechneten Entitäten ebenfalls Ausreißer. Da das bis vor 2 Versionen von HA wie gesagt immer nur beim Neuladen der Config auftrat, konnte ich gut damit leben.
Seit vorletzer Version von HA produziert es diese Ausweißer aber regelmäßig und nachvollziehbar immer zu denselben Zeitzpunkten: 0 Uhr, 6 Uhr, 12 Uhr, 18 Uhr 🤷♂️
Sieht für mich irgendwie nach Bug aus, da ich keine neuen oder geänderten Entitäten angelegt habe 🤔
Ein Beispiel für eine immer betroffene (mein Verdacht, eine der auslösenden) Entität:- sensor: - name: Gesamtertrag PV alt (mit Langzeitkorrektur) unique_id: gesamtertrag_pv_alt device_class: Energy state_class: total_increasing unit_of_measurement: "kWh" state: "{{ states('sensor.bitshake_smartmeterreader_ertrag_pv_alt') | float(2) + 56120.32 | float(2) }}"
Ich habe dann versucht, die Ausreißer abzufangen, indem ich das State Argument so verändert habe:
Im ersten Moment schien das zu funktionieren, aber dann hat's den Gesamtertrag, also den Zählerstand genullt, obwohl die Zahlen das nicht hergaben.state: > {% set new_value = states('sensor.bitshake_smartmeterreader_ertrag_pv_alt') | float(2) + 56120.32 | float(2) %} {% set old_value = states('sensor.gesamtertrag_pv_alt') | float(2) %} {# Neuer Wert wird ignoriert, wenn die Werte gleich sind oder weil er nicht kleiner sein kann als alter Wert #} {% if new_value <= old_value %} {{ old_value }} {# Wenn mehr als 0,5 kWh hinzugekommen -> wird als Ausreißer betrachtet und alter Wert genommen #} {% elif new_value - old_value > 0.5 %} {{ old_value }} {# Normale Werte #} {% else %} {{ new_value }} {% endif %}sensor.bitshake_smartmeterreader_ertrag_pv_althatte 6827,28, macht mit der Addiion von den historischen 56120,32 62947,6 fürnew_value.
Der Zählerstand vor der Nullung, alsoold_value, war ebenfalls 62947,6.
Also hätte imho doch{% if new_value <= old_value %}{{ old_value }}greifen müssen, und das wäre eben weiterhin 62947,6 gewesen 🤷♂️
Warum funktioniert das nicht? Warum nullt es mir den Zählerstand? 🤷♂️
#Hausautomation #Homeserver -
Periodic reminder for people interested in #HomeAssistant
There is a @[email protected] bot that replaces the old gup.pe home assistant bot.
Mention it in your homeassisitant posts and it will boost them. Follow it to see all the #homeasistant posts it boosts that may not normally get federated to your instance.
There’s also @[email protected] - follow that and it will automatically boost everything you post with #homeassistant without you having to remember to mention the bot.
For those who don’t know, these bots exist because when you look for a a hashtag, your server only checks the posts that have been federated to it.
In order for a message to be federated to your server, the author (or one of the people boosting it) have to be followed by someone on your server. If no one touching the message is being followed, it’ll never get federated to your server and you won’t see it.
Hashtags are great for finding messages, but only messages that were federated to your server. They don’t help message propagation, but these bots will.
-
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 -
@derphilipp die iOS App von #homeasistant kann das nativ. #android wahrscheinlich auch. Chatten geht nicht.
-
@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)
-
Mal schauen ob die Bedingung funktioniert...
-
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
-
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!
-
Does anybody has any experience with this indoor air quality monitor and Home assistant? I'm thinking in getting one.
#homeasistant #airquality #openhardwareIndoor Air Quality Monitor
https://www.airgradient.com/indoor/ -
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 -wIt 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/system2. create a definition file for the service
sudo nano glances_w.service3. 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=25Change 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.service5. Check the status of the service
systemctl status glances_w.serviceIt 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 tomiThe 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/
-
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 glancesAnd 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:
- 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.
- Install Glances
<path to venv>/bin/pip3 install glances
- Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
<path to venv>/bin/glances -w
- 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.
- Install Fastapi (web framework)
<path to venv>/bin/pip3 install fastapi
- Run Glances again to find out more of stuff is missing (uvicorn)
- Install Uvicorn (web server)
<path to venv>/bin/pip3 install uvicorn
- Run Glances again to find out more of stuff is missing (jinja2)
- 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/
- Create virtual environment in Python just for Glances (venv something something)
-
Are you perhaps a lucky owner of Rockchip RK3588 powered #friendlyelec Nanopi M6? Welcome to try optimised Armbian Linux experience https://armbian.com/nanopi-m6/ with #platinum support.
#aarch64 #arm #server #armbian #debian #ubuntu #kalilinux #homeasistant #TechInnovation
-
Vnitřní půdní senzor MiFlora není nejlevnější, ale ze tří zkoumaných tohle opravdu dobře funguje a měří. A nejenom vlhkost a teplotu. Navíc k tomu je i slušná databáze květin s vhodnými hodnotami pro vše měření. Do #homeasistant to jde připojit skvěle.
-
Anyone familiar with #homeasistant know how to make HA store the state of something so that you can have an automation manipulate the object and then have it return to its original state?
-
Who else has a Tidbyt?
We just got one and we are going to program some plugins for it.
#tidbyt #iot
#homeAutomation #homeasistant
#thread #matter #wifi #smartdevices
#smartdisplay
#raspberrypi #arduino -
if you run #homeasistant and don't name it "homeass" why do you hate fun
-
The amount of installed #solar panels in this area is to high for the network to transport all the energy generated. So during a day like this the #solarpanels will shut down at ~251 volt.. so even while using over 17kW of power (of which 6.1kW is generated by my own panel) the voltage is creeping up to the limit :( #green #energy #power #homeasistant
-
Made a quick and dirty 3d printer monitor dash in homeassistant
-
@[email protected] @[email protected] @[email protected] io ne ho 5 uno è installato fisso #kodi uno #homeasistant e un altro con un magic mirror ( solo che lo devo costruire ancora ma la parte software è pronta)😇
-
@ceedee666 @homeassistant also like the extensibility of #homeasistant
-
Thought I'd repost my #introduction
I'm a technologist for #localgov during the day. A transformation enthusiast.
#Bipolar, recently married and dad of 3, watching #movies, #scifi and love #goodfood and #coffee. 2 #dogs and a #cat complete the home
#smarthome, #lego, #modelrailways, steam train geek.
Constantly learning, technology (#3Dprinting, #drones, #selfhosting, #homeasistant, #photography, #drones, #infosec) and socially, to be a better ally to those who aren't as fortunate as me.
-
Would be great if we can get #Tasmota support and do it all #opensource.
If I were to get a speaker system like #Sonos, it has to be able to connect to #homeasistant and other #opensource services!
-
If you're clever at #ReverseEngineering or decompiling #Android apps - I have a #HomeAsistant challenge for you!
https://community.home-assistant.io/t/x-sense-security-is-it-possible-to-create-an-integreation/534119 -
I have a plan to use smart TVRs a nest thermostat and home assistant to build my own smart heating system. Mosley because I want to heat only my home office when I'm working but not the rest of the house and I'm too lazy to go and turn all the radiators off by hand.