Next time it happens check if the Association Group 01 has device 01 in it. I’ve seen this get removed a few times and I think it was after an update. Adding it back got everything working again.
1 Like
I’m having the same issue. Did you ever figure it out?
I eventually got them all to work by persistence. Someone else posted the size field was wrong and manually changed it. I’ll try to find it.
Thanks! I ended up excluding the dimmer and PC controller from ST and connecting dimmer directly to Z Stick to push the update and that did the trick for me.
Big shoutout to the Inovelli team for fixing smart bulb mode in 1.53. It now operates just as I assumed it would when I bought the switches, and by lowering the ramp rates and dimmer delays, control of Zigbee bulbs is pretty seamless so far.
2 Likes
I started getting the same thing this morning. Very weird…and no, there is nobody locked in the shed trying to get out 
dev:3452021-03-11 07:25:15.278 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:24:33.078 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:24:19.815 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:23:37.328 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:23:24.230 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:22:41.512 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:22:28.811 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:21:45.601 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:21:33.426 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:20:49.736 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:20:37.985 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:19:56.416 am infoShed Light: Button 8 was held
dev:3432021-03-11 07:19:55.627 am infoShed Light: Button 8 was held
dev:3432021-03-11 07:19:53.957 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:19:42.471 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:18:58.210 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:18:47.402 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:18:04.748 am infoShed Light: Button 8 was held
dev:3432021-03-11 07:18:02.488 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:17:51.395 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:17:08.682 am infoShed Light: Button 8 was held
dev:3432021-03-11 07:17:06.402 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:16:55.889 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:16:10.598 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:16:00.370 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:15:14.814 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:15:04.902 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:14:19.029 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:14:09.464 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:13:23.211 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:13:13.964 am infoShed Flood Lights: Button 8 was held
dev:3432021-03-11 07:12:27.330 am infoShed Light: Button 8 was held
dev:3452021-03-11 07:12:18.496 am infoShed Flood Lights: Button 8 was held
2 Likes
I did some more testing and figured out how to easily reproduce it. @EricM_Inovelli this info may help your engineer fix this bug.
I found out that using the “hold config button for 5 seconds then release” (to see the z-wave signal strength) will start these messages repeating. Power-cycle the switch via air-gap will clear it. Holding config button for 5 seconds then release again will start the messages again. I can reproduce this every time
Side note: I updated the device handler to the new version released yesterday (2021-03-10) and the event is now logged as Button 7 held instead of Button 8 held. But otherwise everything else is the same.
2 Likes
I also learned that an air gap reboot can cure it too. I’ve made that a standard practice now when adding/removing any of these from my meshes.
Thank you, this is very useful. I’ll relay it to the engineers.
@LA_MATT.T I’m having this same issue. No scene commands or updates to current states using the 1.52 firmware and the latest 3/10 driver update on a Hubitat C7. I’m currently downgrading to see if the issue somehow persists. Did you ever find a resolution?
1 Like
Did you use the Hubitat device firmware updater app to update to 1.52? That’s how I initially did, but I reflashed using a z-stick and I haven’t had the problem since.
Interesting. I’ll try that next… So you overwrote your 1.52 firmware again directly using your z-stick? Reverting to 1.48 via the DFU seemed to fix the issue as well.
Edit: I tried a Z-Wave repair after installing via the DFU again, and the device turned up Pending, so I replaced the node and it’s now reporting everything as normal. It’s definitely not the firmware update, but updating the switch via the DFU while being S2 authenticated creating some communication problems. Messages are received and processed by the switch, but not by the hub.