So I have my lights grouped using Groups and Scenes. For example my Driveway Lights group comprises some landscape lighting, the porch light and kitchen door light, all z-wave. I control the group with a Simple Lighting rule to turn them on at sunset - 15min and off at 11pm. I view the state of all my lights on a dashboard. I have tiles for the group master and all the members below it. Obviously the members should follow the state of the master right after a change.
The Group is turned on and off at the correct time just fine by SL. And, for the most part, the member devices obey the state of the group master, ie they mostly all physically turn on and off at the right time. However I am seeing in the dashboard that the state of about 50% of the devices is wrong after a SL event on or off. Its just the state, the light should be on, and it is on, but it shows as being off (or vice versa). If I go around these wrong devices and hit refresh in the driver, it instantly updates to the correct state in the driver and on the dashboard.
I have a pretty solid z-wave plus mesh. As I said, hitting refresh instantly updates the state, so the connectivity is there, and its fast. Just not seemingly right after a group state change has occurred. It feels like the mesh or the z-wave stack is not handling the burst of commands and responses properly and messages are getting lost. I have a different group of zigbee bulbs that uses group messaging, and all its member devices seem to report correct state after a change.
I guess I could create some RM creature to periodically refresh all my zw+ devices, but that feels like polling, which id like to avoid, and shouldnt be necessary.
Anyone seeing something similar? Any tips for elegant solutions?
