I have an issue that I've been able to narrow down to the latest firmware, but I'm not sure if it's the HubMesh or something else...
My garage doors wired up to the zooz multirelay, using the zooz garage door app, and then the dashboard im pressing the button on is on another HE communicating over Hubmesh. Rolling back 2 versions everything works great, 100%. But on the latest update, it seems like 1 out of every few garage commands is lost.
In this log you can see the bottom where the time is 4:07PM, I am on the older ....3.123 firmware and the doors are working as they should. Then starting at 5:01PM I am on the latest ....3.130. The blue X shows the hub acknowledging the door is in the incorrect state.
Going into the zooz device page seems to control the doors just fine by pressing the ON switch. This seems to be an issue communicating with the App or Hubmesh, or, I'm really not sure. But I have rolled back twice and this issue is not on the older firmware.
I can also add, this behavior does not seem to be present in 3.128. This is 3.130 only. I've swapped the versions several times this evening and each time everything works perfectly on versions before 3.130.
I have had the same experience with my Zooz garage app. Other apps didn't work consistently as well. I cycled an app where one (z-wave) switch controlled another and it would bomb out at 3 cycles, sometimes on the first. It was repeatable. I will stay at 3.128 until the next version comes out and see if that works any better.
I don't think it's HubMesh. My GDO use wired to a Zen16 with no mesh involved and I've noticed the same behavior the last couple of days. I didn't dig into the logs, but noticed my dashboard tile working unreliably since the update a couple of days ago
I just wanted to add myself to the group experiencing inconsistent operation issue with a Zooz GDO relay in the latest FW. I've been looking through logs also and verified my app tells the GDO to open/close but it is completely ignored by the Zooz device (nothing shows in the log). I just moved my single open/close calls into repeat/while's to catch the event and still operate the door. So far, each time if the first call is 'ignored' the second call works. I'm just glad it's not only me Hopefully something is found.
Edit, thanks for the ack, BobbyD
Also, update just had my first double failure. It took the 3rd try in my repeat/while to get the door to open. Nothing in the logs, it's just like the Zooz portion simply ignores the open/close call.
Glad to see some traction here and other users noticing the same behavior. It's a strange one, but I'm confident in the team at HE, they haven't let me down yet.
I may have an educated guess about this... there was a change to check if a scheduled job is in the past, and if app/driver uses a call to run something in 0 seconds, it may be in the past by the time the call is actually scheduled. 2.3.3.132 (just released) has some better logic handling this. Can you try updating to 2.3.3.132?
Well, how about this? I go back to the reversion screen and I find that 128, the version I just updated to 132, and then reverted to 130, is no longer an option! 2.3.2.141 is the last choice. So I can't even go back now to a version that I know is rock solid. I'm assuming this was because 128 is a beta version and I apparently got kicked off the beta program yesterday. Isn't that special. Here's hoping 132 is stable, for me of course.
The light switch that I'm controlling from another light switch is actually a GE/Jasco motion switch using @JasonJoel 's driver that separates the motion detector and light switch components. Wouldn't that be a parent/child thing as well? Anyway, that's working for me now on 132. I guess I could break out my spare Zooz multi-relay and see how that works on 132.
Hopefully something is found.
