Yes, same here. More than 20 minutes to restart. Not experienced in 0.112.4 (2 minutes to restart)
Iāve got a denkovi maxi I/O
The reason I went for this is that it has 8 relay channels and 4 analog temperature inputs and wired network connection. I use it to control my heating and ventilation system and wanted it to be all hard wired. Iām a sparky so didnāt mind having to pull a few wires around the place.
I never intended it to be able to take a switch input but that was just an added bonus!
I only have one switch being polled on it.
This being said Iāve got a wi fi dimmer on the way so it will probably become redundant soon!
Installation of 0.113.2 failed badly on my pi 3.
This is output after I updated from 0.112.2 to 0.113.2:
>sudo systemctl status home-assistant@homeassistant
Jul 29 21:19:33 hassbian hass[743]: 2020-07-29T21:19:33+0200 Info: Connected to 192.168.0.201
Jul 29 21:19:37 hassbian hass[743]: 2020-07-29T21:19:37+0200 Warning: No dispatcher found for notification
and later I get these:
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: InvokeId mismatch: waiting for 0x16 received 0x11
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: No response pending
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: InvokeId mismatch: waiting for 0x16 received 0x12
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: No response pending
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: InvokeId mismatch: waiting for 0x16 received 0x13
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: No response pending
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: InvokeId mismatch: waiting for 0x16 received 0x14
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: No response pending
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: InvokeId mismatch: waiting for 0x16 received 0x15
Jul 29 21:21:03 hassbian hass[743]: 2020-07-29T21:21:03+0200 Warning: No response pending
HA is not loading in the browser anymore. Reboot of my pi does not help. I reverted to 0.112.4
Anything I could try?
Same hereā¦ I was going crazy thinking to what was causing thisā¦
Yes, I have spotcast on its latest version (3.3.5) both configured and running in my Home Assistant, but never experienced a slowdown issue with it until 0.113.
On 0.113 while running the top command on the host I noticed that python3 kept going through the roof, eating over 150% CPU and Time+ going over 300:xx.0 sending the 15 minute load average around 15.x, when on 0.112.x CPU usually remained below 15%.
I read on the opened issues you mention that spotcast has been spotted as a possible related factor. Hopefully it will get fixed with 35943 or a spotcast update.
Thank you!
Did you manage to keep your device names as they were before migration?
Yes but not easy:
- take care you prepare your configuration.yaml before upgrading, remove name field and add a # with the orignal name.
- upgrade
- go to entities and search on the rfx idās in your configuration.yaml, you will find them and then you can rename them to the original names so all your automations etc will work again without modifying.
Still is present/not fixed in 0.113.3 0.113.2
Very annoying because I use(d) this function a lot
Where is 0.113.3?
Good question So still a chance to get it fixed actuallyā¦
trying to work out the already reported issues with google tts notifications, I now notice all my notify.notify services stopped working after updating to 113.2.
this is in the log if I issue a service manually from the developer-tools/service
2020-07-30 17:56:28 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:29 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:30 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
2020-07-30 17:56:30 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Requested entity was not found.
which is silly because notify.notify has nothing to do with my registered mobile apps, and I am not issuing that command in the first placeā¦
so, checking that in the services page, I now am scattered to see none of these mobile_app services work eitherā¦?
hope I am not aloneā¦
is this a(nother) bug?
ha core update --version 0.113.1
restores the earlier mentioned tts %20 issue, but I still have issues with the services page using notify.notify and other notification groups. Pushbullet still works fine, the others give the posted error still
Thereās an issue with mobile push at the moment:
o Iāve missed that, sorry. Thanks for the link, this is a major bummerā¦
coming to think of it, Ive also updated the iOS app yesterday. Hope this isnt a chain of issues ;-(
update
found my older iPhone and iPad and they did receive the notificationsā¦is it the new app then after all?
I was able to update last night but for some reason I canāt log in when using my normal Firefox session. If I open it in Firefoxās Incognito Mode, I can log in fine. If I use Chrome, it also works fine.
When I log in through the regular session I get 400 errors for the /token endpoint and thereās errors in the JS console.
Uncaught (in promise) TypeError: u.addEventListener is not a function
e core.a99cac39.js:1
o core.a99cac39.js:1
o core.a99cac39.js:1
o core.a99cac39.js:1
hassConnection core.a99cac39.js:1
promise callback*196 core.a99cac39.js:1
I cleared the entire cache and also tried by using Firefox in safe mode and it still doesnāt work. Not sure why Incognito would work fine though.
Update to this issue: I forced Firefox to start in Safe Mode, and was able to get back in with my regular browser session. The Firefox extension I had installed (WebSocketSniffer) was messing up the websocket connection.
anyone else seeing this weird behavior from 0.113?
I thought my logs were broken but it really is empty after +24h!
Nice work guys!!!
Iām having the ārequested entity not foundā issue too.
Just commenting to say, you guys are awesome! I just got around to checking out the 113 notes and the automation & scripts updates are much, much appreciated. As someone whoās innermost thoughts are comprised of about 50% functional programming code, having the ability to do loops and if/else syntax makes writing up new automations SO MUCH EASIER. Iāve only been messing with HA for about 4 months now and the progress Iāve seen just in that time is unreal, and well worth my support (through HA Cloud subscription).
Keep up the fantastic work!
so are most people on the new iPhone Appā¦ check this for development of the issue and hopefully quick fix
for now, resetting your push_id in the app settings makes the notifications work again (though no promises are made for how long)
Maybe you should check your IP-Bans?