Room lighting gives currentSwitch error

I changed nothing and all of a sudden my Room Lights app is giving me this error, which prevents it from turning on the lights:

Anyone seen this? Fix?

Actually - this is happening on all my Room Lighting apps. So frustrating.

I did a search to see if anyone else had this issue and found two other posts over a year old - both with no responses. I made a new Room Lighting app and it worked, but all my existing ones are toast.

Tagging @bravenel

Thanks both... I'm rewriting the handfull of essential ones I need to work today, but hope to find a fix for the slew of others I have that would take quite awhile to rewrite. All the rewritten ones look exactly the same and they work, and the old one's don't. So weird.

This is indicative of a missing device, one that was removed somehow. Can you show a screenshot of the Room Lights instance that throws this error.

1 Like

Sure... Here is the error:

Here is the rule:

And here is the device - Bottom Stairway Light:

All three appear to be there. A rewritten rule using the exact same device works fine.

1 Like

And here is the "gear" info for the Room Lighting sub-app:

Ah, good. So perhaps this was some corruption of your database.

yea, I think that's the case. I ended up rewriting them all and now all is well. It was easier to rewrite them than to do more fussing with finding a root cause. In case it helps you with the platform, this all happened after I migrated my other hub from a C5 to a C8 Pro which went fine. The next day this happened to this hub which is a C7 and had nothing to do with the migration, other than the Hub Mesh got switched of course. The mode following and variable sharing via Hub Mesh may have messed stuff up. I had to do a bunch of virtual devices swaps because my Alexa integration is only through my other hub. That's the only thing I can think of that could have messed it up.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.