MH devices not working in scene any longer

[MJsan]

Not sure if this is due to a recent update or not, but I had some corrupted KPL files in my EISY that I had to remove/replace the KPLs (fixed it). However, I have one LED strip that works in the MH app, works in Google Assistant, and seems to work in the UD app on my phone and on the console when I tell it to go ON or OFF (I'm watching it physically go on and off). 

The weirdness now is that it doesn't show on the UH console whether it's on or off... but does on the UDI app (see attached image). Not a major issue, but I'm trying to suss out why that's not updating but the UDI app does?

More problematic: I have this light in a scene so that it can be controlled with a KPL button (and a few other "all off" scenarios), and it's not responding. It used to work relatively flawlessly - I'd have to restart the PG3 once in a while (especially after a power outage) but for 1+ year it's been good. Now the only way to turn it on or off is via the UDI app, MH app, or voice via Google Assistant (so we KNOW it's connected, working, but just not being part of the scene).

Any thoughts, ideas, or suggestions? 

In a related issue... I have about a dozen accent lights tied to a scene. Executing the scene from EISY I usually have 2-4 that don't respond... but when executing a similar scene from Google Assistant, 100% come on (albeing VERY slowly, one by one). 

PG3x ver 3.3.18, IoX 5.9.1

 

Edited yesterday at 01:22 AM by MJsan
added versions

[MJsan]

Interesting... when executing "ON" from UDI, the messages show it happening. 

When executing the scene "ON" ... I get this link not found error. 

Now I'm really perplexed. 

Tagging @bpwwer because he's the smartest guy in the room in a lot of cases

Edited yesterday at 01:31 AM by MJsan
adding tag

[bpwwer]

I'm not sure how the app works, but when you click On or Off in the console, IoX sends the command to the plug-in and plug-in process and sends the command to the device.  If the device changes state, the plug-in will see that change in state and pass that state change back to the console.

Since the console isn't reflecting the state change, either the device is not sending the updated state to the plug-in or the console is not seeing the state change when the plug-in sends it.

A couple of things you can check.  In PG3, if you look at the nodes tab, it will show what the plug-in thinks the state of each node value is.  if the ST value is getting set correctly, then the device is sending the update and the plug-in is seeing it.   The PG3 log should show lines for all the messages going back and forth to the IoX.  So again, when you change the state on or off, you should see a line where PG3 makes a request to IoX with the new state.  If that's failing, you also see those failures in the PG3 log.

For the scene, it sounds like you may need to re-create the scene, link not found seems to imply a corrupt scene.  I do have a MH bulb in a scene and it continues to work as expected.

[larryllix]

I have found different code techniques are required for so many different versions of the MagicHome/LEDenet bulb versions. Some of the newer bulb versions have simulated candlelight flickering built into the bulbs. White temperature adjustable LED lamps and some bulbs require a different technique where the white blends use a brilliance parameter and  white temperature balance parameter instead of discreet CW/WW values.

The PG3 NS may not support some of these versions.

I have had to make many adjustments to my code many times when purchasing a new batch of bulbs. Mine vary from v1 to v10.

Have you added new bulbs recently?

Edited 7 hours ago by larryllix