Having trouble with presence sensing since the latest beta firmware on Thursday. Both my phone (Google Pixel) and my wife’s (iPhone 8) have significant delays, sometimes >10 minutes before the hub detects are presence and adjust SHM and my automations accordingly. This was working flawlessly prior to the update. The fact that both of our phones are doing this leaves me to believe it’s on the hub’s side. I’ve tried reboots and adjusting presence zones, etc.

Also have a motion sensor that reads as constantly active. I’ve removed it and readded, it works for about 5 minutes then goes back to constantly active. I’ve completely removed it now until it’s resolved.

Having issue with both Iris and Centralite keypads since this update and perhaps the update to Groovy.

When entering a pin there is a timeout where the network light shuts for about a half second, then turns back on. However, it appears the device has “timed out” and will not react to the status command, causing all the status lights to start blinking. The status requrest is properly processed by ST SHM.

Since they released 24.5 last Thursday, I have one z-wave lock that is constantly showing as unavailable. If I manually unlock it, it shows as available again and I can control it through the app. But within an hour, it goes back to unavailable. Not a battery or distance issue. I haven’t posted this issue on centercode yet but will.

Do direct association commands ever get routed by repeaters or do the commands always go directly between the 2 devices?

With this beta, direct association seems to be delayed and no longer reliable.

I realize that this is probably coincidence and NOT related to the beta at all.

Maybe the devices in question are failing but it affects 3 different devices bought at different times.

The other possible explanation is that prior to this beta, direct association commands were being helped along with some repeaters I have, that I have removed from my mesh. I do NOT think this explanation is likely, but I am including it as a possibility.

What happened the day that I got this new beta. I was having system zwave problems. After rebooting and doing zwave repairs I started to remove devices that I no longer needed, one at a time, with the plan of simplifying the zwave mesh and hopefully get to the point that zwave repair, repairs cleanly, as it used to do. Again I am not sure that it is not coincidence or is the beta, but prior to the beta as far as I can remember my zwave repairs had no errors.

As part of the group of zwave devices I removed were the zwave plus radios in some iris plug in sockets.

Anybody on the hub beta using smartsense open/close devices and the new app? All of mine are showing 40*F in the new app but correct in the classic app. Not sure if it’s an app or hub firmware issue. iOS app.