-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exceptions since HA 2023.9.0 #158
Comments
yes, you are right. When the yaml is loaded, some modbus values are still not present. The template sensors should check this before. |
The same here, I have no sensors. Is it the same bug, as to update 2023.8.3 ? |
well its more broken in my code :) But I don't know yet, why it is triggering now |
an "availability" option in the templates could solve it, I can add those if you want. Of course only if you aren't working on the code a lot, so I don't trigger too many conflicts merging. |
Already coded it..will check in tonight after some testing ;) |
Above I forgot to say, that I make a downgrade to core-2023.8.4 and now it works for now. |
Can you double check, if it is fixed? I am on 2023.09 and there are no more log entries after "full" restart and none after "yaml reload" |
The error does not come up again. 2023.09 and 2023.09.01 |
Hello Same here no Sensors again since 2323.09.01. The Solution seems to be this... https://github.com/home-assistant/core/pull/99988/files I have loaded the newest yaml , but the sensors are still unavailable |
Anything new about the Modbus Problem since 23.09.0 I can not use my surplus charging :) |
The modbus_sungrow.yaml last update: 2023-09-08 (2) doesn't work here. I made for testing and logging a snapshot from my working ha-vm with ha core-2023-08.4. Than I updated the modbus_sungrow.yaml and after that I updated the ha core. After Update to ha core-2023-09.1 the sensors works for maybe 20 minutes, then sensores are not available. HA works completely a bit slower (not testing, only feeling by clicking ;)) Here is my abstracted Log with ha core-2023-09.1 and Sungrow Hybrid Inverter SH10RT: auszug-log-nach-core-update-2023-09.1-home-assistant_2023-09-10T18-06-19.729Z.log After the HA-VM-Rollback to ha core-2023-08.4 all works fine !!! |
The update 2023-09-08 (2) works well with the SH10RT. The previous version worked as well until something broke. So thank you very much for the quick fix! |
Hello , same here since 2323.09.01. Update 2023.11.09 - since last reload of yaml - took time (don't know how long - over night :) ), to reload all sensors, but runs stable now |
I reverted to Home Assistant version 2023.8.4. The more recent HA release doesn't work |
i tried two times to resore 2023.08.4 but it doesn t work. What am i doing wrong. |
Who of you is using a modbus proxy? I am using one and not experiencing all these issues. Could you maybe try https://github.com/Akulatraxas/ha-modbusproxy/ ? |
I don't. At least I did not configure one. |
I changed to using a proxy. Now the connection seems stable. Even though I don't like the idea of another layer between, it is a working temporary fix, until the core integration is fixed. |
FYI seems to be fixed in HA 2023.9.2 and fixed by this PR home-assistant/core#99988 |
with HA 2023.9.2 everything is working fine since this morning. |
sorry, I cannot derive anything from the plots. What is shown there? (Axis description is missing) |
works fine with the latest HA release. Thank you very much! 👍 |
Since HA 2023.9.0 I get exceptions:
Afterwards I have to reload the yaml to bring the sensor values back. Perhaps this is caused by an unstable lan connection. Would be a solution to check every value for the string "unavailable" before using it as sensor value?
The text was updated successfully, but these errors were encountered: