Is there an "id_v1" value in "state" (not "Current States"; might need to enable developer mode to see this) for the problematic device? And what real-world action/command corresponds to the entry?
EDIT: OK, I have an idea of how this could have happened. As a workaround in the meantime, commands that don't need the V1 API at the moment (anything besides Set Color?) should work...
Thanks again for looking
It's actually solved now. Turning each one on/off with Hubitat in a browser (sure there's a name for logging into it via IP) pulled them back in. Now the motion app is firing as intended. I think it just needed to re-establish a connection. Assuming on/off in the actual phone app may have also fixed it but wanting to be clear I did it directly through a browser window.
From your logs, the problem would be related to the issue I discovered that will be fixed in a future platform build (and likely come back from time to time in the meantime, particularly if you have bulbs that go online and offline on Hue for whatever reason or chose non-default polling configuration -- two possible causes of this data getting "corrupted" that I see). But a turn on/off would be a quick way to likely get the data it's looking for back to what it should be -- and is necessary for some commands, the ones I referred to above.
A test of this should have revealed that "Set Color" failed, while "On" or "Off" was fine (unless, per the above, done in a different order or before the problem came up again). This is the kind of information I was trying to gather that would be helpful in troubleshooting. Hopefully it helps next time!
I don't see any evidence of issues related to motion areas, though if something is going on with events from those, logs would again help clarify.
Hey Bertabcd1234. You're totally right. I did miss what information you were trying to gather. I was sharing the forest, "this app no longer is running correctly", rather than the tree, "what specifically isn't working." I apologize. On my end, and not conveyed, I could see the motion activity was working as designed but it was the lights themselves not changing state. I wish I thought to look at the light events. Alas, I had totally forgotten that the lights are only used in the one mode. The things that were correctly running within the same motion app, but under the other modes, are not in the mode that wasn't running as desired. Essentially one side of the coin was correct and the other wasn't but they were two separate coins and I thought they were the same one.
Download the Hubitat app
