Since this update my HomematicIp local integration stopped working.
Error: HomematicIP local interface not reachable.
it worked like a charm before
EDIT:
After several hours of waiting the devices seem to be picked up again. Not sure why and what happened before but the problem seems to have solved itself…hope it stays like this.
That’s really cool! Can’t wait to get the Yellow PoE, hopefully the new board design passes all tests…
Hello, I’m running RPi4b. After the update, I’m having problem booting the Home Assistant without HDMI. When I plugged the HDMI cable connected to the TV, it boots. I’m trying to restore my last backup now if the problem still persist. I will post again after restore.
Update:
Restoring from backup didn’t work. But fixed by uncommenting the “hdmi_force_hotplug=1” from the config file.
Thanks Bro
Hey guys!
I updated to the latest iteration yesterday and see that my HA will not allow a restart or access to the integrations page. I did a force reboot by unplugging my pi but the problem is persisting. I see that I also can’t get into the backups section to try revert to 2022.9.3. Not sure what to do now.
Update - I see that I cannot access any of my installed integrations (Hacs, Node Red etc.). When selecting one of them, I just get a blank screen.
Home Assistant 2022.9.4
Supervisor 2022.08.6
Operating System 9.0
Well if you want to revert to 2022.9.3 execute in your ssh session
ha core update --version 2022.9.3
A simple way is to plug a keyboard and monitor into the RPi.
Since this release and SHellyForHass 1.0.2 i have a lot of connection timeouts to shelly devices. Devices have the latest firmware (1.12).
Logger: pyShelly
Source: /usr/local/lib/python3.10/site-packages/pyShelly/utils.py:94
First occurred: September 14, 2022 at 9:27:11 PM (697 occurrences)
Last logged: 11:15:06 AM
Timeout connecting to http://192.168.2.79/status
...
After OS 9 update, my raspberry pi wont bootup anymore.
Even ping the IP is not successful. What can i do? Is my system now destroyed?
Nothing has been changed in 1.0.2 that can give this error.
What happens if you load the URL in a browser?
That seems to work fine. device responds with the status json.
I was triggered last night by one of the devices that did not turn on the light trough HA. It only switched on after using the physical wall switch. After using the physical switch the device also responded again trough HA. After checking the logs i noticed the amount of connection timeouts.
[edit]
Correction: after some monitoring 192.168.2.85 just caused a log error and is not responding on the status call. within a minute or so it responded again on the status call.
I get the same thing. Can’t access any integrations (HACS, Log viewer, File Editor, ESPHome, etc).
I am also keen to use the scheduler, however I find that the UI doesn’t work properly on Chromium browsers. For example I am unable to create a time slot from say 7:30 to 22:30. Any times not visible do not get scrolled correctly. It needs an option for a pop-up entry box for start and end time.
Pushover YAML migration failed. In this release Pushover is available as integration. The settings are merged from the Yaml file. But Something went wrong I guess. Pushover no longer works and is not shown as integration. If I try to add it as new integration is fails.
I have configured a lot of messages. For now I will migrate them to NodeRed.
Please fix it in HA!
It looks like a problem within the shelly device after examining the shelly debug log. the device is reporting a 201 error. wifi issue. So it looks like there is no issue in ha or shelly4hass!
Just created PR to update docs
Turns out the disabled label shows up if the automation is disabled, so disregard previous post
Yet I don’t think you filed a issue on github. How do you expect it to get fixed?
I give all my automations unique IDs and that is just not true. Maybe if you edit in automations.yaml but I put mine in packages alongside the things which are automated or the context the automation runs in (e.g. a package for everything related to media playing)