I had a scene working that turned on/off two FIBARO RGBW controllers and set the color desired for each. It no longer works, and I see the following in the logs;
dev:7402025-08-05 08:43:21.547 AM
error
java.lang.IllegalArgumentException: null on line 59 (method on)
dev:7402025-08-05 08:43:21.532 AM
info
boxes was turned on
dev:7402025-08-05 08:43:18.925 AM
error
java.lang.IllegalArgumentException: null on line 74 (method off)
dev:7402025-08-05 08:43:18.915 AM
info
boxes was turned off
Kudos for sticking true to the Groups and Scenes App. If only for my own interest, are you running a recent platform version or an older one? i.e. what version are you running?
A screenshot of your setup may (or may not) help those who know more than me about what could be happening...
It's a C8
A screenshot of your setup may (or may not) help those who know more than me about what could be happening...
Sorry, I don't know what you mean by "your setup". Can you please be more specific?
I would try recapturing the scene, but I had to spend several minutes with wife to get exactly the right color of "warm white" and to get the two devices colors to match (no, the same R,G,B,W doesn't result in the same apparent color between the devices. Different LED strips, different ambient colors)
Is there a way to see the RGBW captured for each device in the scene? If so, I'd just set those, then recapture.
Just screenshot everything.... 
Nah, good point, I did leave it a little open. Was thinking about screenshots within the automation app you have setup.
I just did a scene capture. I don't think there's really anything interesting about the "scene activator" page. I was hoping I could see the RGBW set for each device in the scene there, but no...
What about the app?
Is dev:74 the scene activator?
Can you go to the device detail page for this device if so, navigate to the "Device Info" tab, and provide the data in the "Parent app" row under "Device Details"?
The scene activator is 740 (not 74--probably a typo?)
There is no parent device???
What about the app?
I'm new to "scenes". In fact, this was the first one I did. That was about six weeks ago and I've been out of town since then.
I thought there should have been something under the apps, similar to what I've seen for groups. But I don't see one for the boxes scene activaotr and I recognize everything else under "Groups and Scenes":
I don't think I deleted anything in Groups and Scenes, but I can't be 100% sure. Does it fit the symptom if somehow the corresponding entry in Groups and Scenes got deleted? Is that where the RGBW for the devices in the scene were stored?
Yep! Normally deleting the "parent" app (the Scene app for this scene) will delete the "child" device (the activator), though this app might behave differently (not sure). However, either that or maybe you accidentally (or not) creating a "Scene Activator" device manually as a virtual device would pretty much be the only way this could have happened. What is the "Device Network ID" for this device, which should also be on the page you took your screenshot from? That would also offer clues.
Scene_538
I think I did create the scene activator manually.
Vaguely recalling, I think I had the scene "working" in the sense that I could apply it to change the colors. But I couldn't actually turn them on/off.
I think I created the scene activator device trying to get an on/off function, but later (I think) I found a setting in the scene definition (sorry I don't know the correct terminology) that made it work.
When I left (early July) it was working using Alexa to "turn on boxes" and "turn off boxes"--this much I'm sure of. And, not working when I got home this weekend
OK yeah, that is a plausible DNI for a child device created by a scene app. If you created it yourself, you must have very carefully edited this DNI -- not impossible, but not the default. I don't suppose you still have an app:538 on your hub (http://<hubIP>/installedapp/configure/538 would bring it up if so, or you can find it in the list with some work), but if you do, that should be or have been the parent app for this device.
At this point, two ideas:
If you did manually create this device, you'll have to either find another way to do your automation or create it as a Scene through the Groups and Scenes app instead. If you aren't using the device in many (or any?) places yet, removing it and doing this would also be an alternative to the above regardless of how it may have gotten here.
Wow, thanks for such detailed replies.
I'm sure I didn't edit a DNI.
Where did you get 538? Here's what I see for http://192.168.0.48/installedapp/configure/538
The hub was rebooted just yesterday (for some reason it went offline), so that won't "fix" it.
I'll have to check if the automatic back-up was actually working. I've had problems with that, now is the time to get it fixed. (I'm actually paying for it, but I think the hub mesh is confusing things and I haven't bothered to sort it out)
"538" was in the DNI for your Activator device; it takes that from the ID of the parent app by default (easy way to avoid DNI collisions, as all must be unique on the hub). So, that app isn't there anymore, based on your screenshot.
Note that I did not suggest a reboot but rather a reboot with database restore. This is not the default and must be done with the option I specified (or manually as a separate step if you prefer for whatever reason).
Local backups are free and automatic, and that is all you need for the above suggestion. You would need a cloud backup for radio restores, and one of those could certainly work here too (but no need to restore anything besides the hub database if you do); depending on your frequency settings, one may also go back farther, so you might want to check both -- assuming you have some idea of when the problem started.
So, does this mean I should have a local back up file for every day?
When I go to choose, I see what looks like a File Explorer window with a .lzf filter. I see only one file, hubitat_new_2025-06023....
That's probably worth trying, but shouldn't I see many .lzf files?
I found the local backups page.
Interestingly there are many (daily), but none between 6/26 and 7/26.
I did pay for a cloud backup at some point, but I think I did it for another hub on the mesh. I'll chase that down later. First I'll go with the 6/26 backup
I was typing a reply when your response came through and I didn't read it carefully.
I'll try a reboot with database restore as you indicated before restoring a backup.
Thanks!
Reboot with the database rebuild didn't seem to change anything.
It looks like 6/27 is when I created the scene activator, and that's the last local backup until 7/27. But, the 6/27 was on an older platform --- 2.4.1.169 versus 2.4.2.16.
Is it ok to restore a backup from an older platform?
Reading about Hubitat Diagnostic tool...
Download the Hubitat app
