My hub is a C5 with the latest build where I have about a 20 zwave switches, plugs, and sensors. I also have the same number of zigbee devices.
I started noticing the problem when I started using Groups and Scenes to handle my Zooz dimmers and Hue bulbs where interactions into the Groups and Scenes was not always caught. This could be from the physical dimmer, Webcore, or Rule Machine. Commands are never missed from the virtual device or dashboard.
After learning about direct zigbee pairing with the Inovelli switches for Hue, I started putting them in. As a result, my physical interactions are flawless. I still have the problem where the virtual device not always reflect status of the dimmer switch status. This comes apparent when my RM or Webcore read the virtual device status before taking action such as toggle actions from a remote, etc.
I'm not exactly clear on what either of the described problems is. Can you be more specific? I can't tell if you're expecting a specific state change on the group or scene activator device based on some real-world change on the "member" devices (and, if so, what); or if the problem is sort of the opposite direction where commanding this activator doesn't result in the desired changes on the member devices. Similarly, in your new setup, it sounds like you're expecting a state change on some activator device somewhere, but exactly which state(s) are or are not updating isn't clear and would be good to know. It also sounds like you might have an automation set up somewhere that isn't behaving as expected, but it would be good to know how that is set up and what the desired outcome is.
One guess without knowing more: there are various options in the Group app for how the activator should show its state in response to member devices. Maybe those options just aren't set as you want? Note that some member device states will simply never make their way to the group device, for example, color changes. Those will only be reflected if commanded from the activator (undoubtedly due in part to to the complexity of figuring out what the group state should be in that case -- an average?). The on/off state should be pretty clear-cut if the options are correct, however.
I do see you mentioned Hue bulbs. This is also not clear from your description, but if these are Hue Bridge bulbs integrated via the built-in Hue Bridge integration, note that changes made outside Hubitat may take up to your polling interval (as specified in the integration app; default is 1 minute) to appear on the hub. If you used Zigbee binding (I assume that is what you mean with "pairing"), this would not be the case, since the bulbs must be directly paired with Hubitat for that.
you have 3 or more device/apps that you need to track:
Bulbs
Dimmer
Group
Apps that interact with the above
Make sure logging is enabled for all of them. Open a log page in a new browser tab. Do something that you know works. Do something that doesn't work. Filter the logs to those devices/apps. Take a screen shot of each scenario. Post it back here explaining your sequence of actions.
This is the best I got. At some point in the early morning, both of my Groups for master Bedroom stopped working, both the lights and lamps. Since the hue bulbs are paired directly with the switch, I didn't notice until later in the day when Webcore could not assign the correct color temp to both Groups.
Once I cycle the group off/on from the device page, as not even dashboards could interact with the Group, it starts working normally and tracking the physical switch. These pictures were taken when the lights were on.
Master Bedroom Lamps - Lamps with hue bulbs were on. My Inovelli switch said it was on. Group said it was off.
On the logs the best way to look at them is to look at both devices and apps in line. You can filter on multiple devices/apps. Your logs above just show devices. Of course, you need to make sure logging is turned on for your groups.
I don't use the Inovelli dimmers. Is your firmware up to date? Go to the dimmer device page and choose update firmware. Look at the logs to check the status.
I finally have isolated the issue down. My Groups would not match the physical state switch because sometimes one of the bulbs wouldn't report as being on. I had to change it to reflect if any members were ON, not off.
