There is now. I’ve never used the custom component but I have my switches calling automations now. Yay!
yesterday i had a problem (0.108.1) that i could no longer reach the webpage, i saw a big HACS logo.
eventually went back to 0.107.7 and then everything worked again.
Are there more who had these problems?
And incidentally, the modbus also no longer worked unfortunately, no more measurements came in.
disappointed to see the modbus rtu component problem sill persists even in 0.108.3 
A little problem I have since a few versions (including 0.107.x). I just remove ‘/lovelace/default_view’ from the url and everything appears again.
I see this all the time in the iOS app as well but just pull down to refresh and it comes good.
Well, in my side it’s just a Rapsberry Pi 3B+, maybe you have a more powerfull one.
No, I think one off pi3b is much the same as another pi3b. (not turboed, not over clocked, no wide bore exhausts or even a go faster stripe)
My pi4-4 has gone from 0 to 1 % too
First I did https://dnsname.duckdns.org:8123, there I got the HACS logo full screen,
if I put / lovelace behind it I get a message that the page cannot be found.
This was also the case if I entered the IP address instead of the duckdns.
Since modbus also does not work, I stay on 107.7
Thanks it helped me, removed unused integrations from custom_components, hacs stayed there, restarted HA and worked (restarted many times before this, that didnt help)
It is ok to be disappointed, especially if you helped solve the problem!
I think most people in here understand that we developers are volunteers, and as such a limited resource.
To be honest your comment makes me think why do I bother solve it (I do not need serial). but then I think about all the other positive comments and offers to help.
The problem is in a combination of HA and pymodbus, because I have a standalone program that works. It will take time to solve this.
A big thanks to all the offers for help and positive comments.
7 Likes
Something is fishy with WLED, I have Wemos D1 too and it goes ON and unavailable pretty fast. Reverted back to 107 and no issues…
@janiversen Please take all the time you need I would say. It seems everyone who needs modbus has rolled back to whatever version they were on so it matters little. If possible could it be announced here that whatever version released may work (ie: needs testing) or not please? That way it will save (people who need modbus working) updating only to find out nothing has changed…cheers!
anone else got the issue in Homekit, that all lights indicated to be on, even they’re off? went back to 0.107.7 which is running flawlessly.
Thanks. Version 0.107.7 works. The best way is to pick directory components/modbus in version 0.107.7 and dump it in whatever version of 0.108.x you are using (that is how I do regression testing).
Follow issue:
https://github.com/home-assistant/core/issues/33872
for progress on the serial issue. Until that is closed serial will not work
Follow issue:
https://github.com/home-assistant/core/issues/33947
for progress on the rtuovertcp issue.
I will announce on the issues when a patch is ready for testing.
1 Like
Next time, refresh page and clear cache.
also in the app and two webbrowsers?
Since updating to 108, my mini graph cards act strange. For most of them the lines don’t load unless I switch to other page (for example Configuration) and back. If I refresh the UI from the browser they are gone again until switching the page and back. Weirdly 2 of the cards load fine without this page switching. They are not configured differently than the others.
I have seen this before and had to clear the cache on all. It is related to something in HACS. I never needed to down grade for this.
D-Link ZWAVE motion and door sensors all not working showing status unavailable after update to 108
Model d’link DCH‑Z120 and DCH‑Z110
Update: even after restore to a previous version the sensors do not work!! Help!