did I miss anything in the 2021.7.4 release note that could block iOS connection to the instance? Im having issues with 2 of my instances, which on 1 I could solve by hard booting the Pi3. another just wont come back on the iPhone either Safari or Chrome browser (while it is perfectly fine on desktop now,) and I have SSH and SMB connection alright.
posted the only errors on the log in discord Discord
Already deleted the tokens, restarted the iPhone twice, deleted website history, and every time I get a new auth screen, after which Unable to connect to Home Assistant. RETRY is displayed…
ip is not banned.
please have a look if you can help me out get my instance back on iPhone?
Since updating to 2021.7.4, for the fritz box device_tracker my not_home/home status is switching from time to time although I am at home all the time. Haven’t had this issue with 2021.7.3
thing is I have 3 instances, 2 of which can connect on my iPhone, it’s only the 1 instance. I’ve tried it all now network only, mobile only, IP address duckdns address. And it has been flawless for over 2 years…
even downgraded just now, but that didnt help, so I am back on 2021.7.4
what else can I try?
dont suppose it is the aeotec zwave stick attached to the RPi…? how could that only cause issues on iDevices…
Anyone else having Zwave issues when upgrading to the 2021.7.4? Every time I upgrade to this version (I’ve done it three times now) . I lose Zwave and have to restore to a snapshot with version 2021.7.1.
I have the ZWave plus Razberry2 plug on module board. When I lose the Zwave, none of my Zwave devices will respond to calls (the green light on the board just flashes). When I restore back to the earlier version everything works fine.
core-2021.7.3 bricked my system, presumably due to max/min changes.
I got stuck on the dreaded “Loading Data” screen after logging in and before lovelace loads. After hours of troubleshooting, I commented out all of my max/min entries in configuration.yaml and everything magically worked. I was methodical and only changed one thing at a time before testing in multiple browsers, and then restoring to previous state before trying something else, so I can definitively say this was the cause.
I’ll submit an issue with relevant logs in github when I regain my desire to play around with it.
I did not say it was but they may be using that addon. We cannot assume what they are using since they did not tell us explicitly. I have had no issues with zwavejs2mqtt and the zwavejs integration.
