yes, it is marked for the beta, but that hasn’t arrived just yet, so this is still release 2021.7.4
just tried on on another iPhone, to make sure it was my device or not, and that too won’t connect. Making this a more generic certificate/iOS issue ?
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 
I meant the iOS beta version via testflight
o, no, I don’t use that.
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…
Try the beta would be my suggestion. There have been some changes in auth in the app recently.
yes, but I am not even using the app on this instance, only regular browser windows. I use the app for my production system.
next to that have always had 3 dedicated browser windows saved on desktop for my instances. 1 of those now won’t connect anymore
if no one is seeing this after updating to 2021.7.4 I’ll take it elsewhere…
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.
Upgrade to what version? “Latest” or “new” are not versions.
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.
Sorry, 2021.7.4
O M G !!! Finally Allow pymodbus to reconnect in running system (not startup) by janiversen · Pull Request #53020 · home-assistant/core · GitHub this happened! Now single modbus sensor unavailability does not affect requests to other sensors!
Great!
1 Like
Not with the recommended zwavejs integration.
Which integration are you using? The original zwave integration and the zwave2mqtt integration have been deprecated for many months.
That’s not an integration. it’s a way to run a zwavejs server that you can then connect to with the zwavejs integration.
and it’s not deprecated. it’s one of the two (OK three…) methods of running a zwavejs server for the HA integration to use.
3 Likes
Thanks.
I mistyped. I meant zwave2mqtt
Corrected.
1 Like
But…that’s not an integration either, tho. 
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.
that’s not entirely correct…
but I’m mostly just bustin’ your chops now.
But we also need to make sure our language is as precise as possible to minimize the confusion for newer users.
there is always confusion over what the differences are between integrations, add-ons and custom integrations.
no reason to add more to the fray.
1 Like
Thanks, I am still trying to get re-acclimated back to HA after 2 years away elsewhere.
1 Like
Did you ever get this figured out? I seem to be suffering from the same issue.
No I still have it every 5 minutes. I started removing integrations/addons to see if it would clear but didn’t get very far. That’s the only way I could think of troubleshooting it. Searches in the forum have only resulted in unanswered threads unfortunately.