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 August 31Aug 31 by MJsan
added versions

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 August 31Aug 31 by MJsan
adding tag

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.

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 September 1Sep 1 by larryllix

On 8/31/2025 at 8:00 AM, bpwwer said:

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.

Like I said in the 2nd post, @bpwwer is usually the smartest guy in the room. That was it Bob... delete the scene and recreate it. Since I had a few corrupted records for 2 KPLs, not surprising. I just wish there were a way to "check" all of the files on EISY to ensure that they are all OK.  

I've removed and replaced the corrupted KPLs which solved one issue... but am running into the weirdest issue now.

I have a scene "master bedroom" that includes several Insteon plugs and one MH device ("Headboard"). There is a scene "Bedroom all" that has all of the Insteon devices + MH headboard. I have one button of the KPL set to control the scene.

If I turn on the scene from the UD mobile app ... it works. If I try to turn on or off the scene from the assigned KPL button ... nothing.

What's weird is that if I active the scene - the light for the KPL button responds, but the MH device doesn't.

Even weirder ... I have a remote link with the same scene programmed to one button ... and it works.

I have a scene defined with just the MH device in it + the KPL and remote link buttons as controllers. The remote link works, activating from UD mobile or the console works... but the KPL doesn't (again, the keypad light responds, but the MH device doesn't.

I've deleted both of the scenes, redid them (several times)... no change.
Any ideas of how to troubleshoot this further, or is this a UD bug I should have them dig into?

bla

I have a scene "master bedroom" that includes several Insteon plugs and one MH device ("Headboard"). There is a scene "Bedroom all" that has all of the Insteon devices + MH headboard. I have one button of the KPL set to control the scene.

If I turn on the scene from the UD mobile app ... it works. If I try to turn on or off the scene from the assigned KPL button ... nothing.

What's weird is that if I active the scene - the light for the KPL button responds, but the MH device doesn't.

I think it has something to do with the way IOX creates and handles scenes. An Insteon only scene programs the responders to respond to an Insteon broadcast message sent by the controller.

In a mixed scene (Insteon + plug-in based device). That won't work because the plug-in based device (MH) doesn't use the Insteon protocol and can't respond to the broadcast message.

IOX should know that the scene is a mixed device scene, but I don't think you can program a keypadlinc button to send anything but broadcast message. The keypadlinc will only send direct on/off commands for the main buttons. So that probably explains the behavior.

When IOX tries to control the scene, it sends the proper command (may a broadcast) to control the Insteon devices and sends an ON command to control the MH device. So it all works as expected. But the keypadlinc only sends to broadcast command which controls the Insteon device but not MH device.

The only workaround I can think of would be to supplement the scene with a program. If keypadlink button X is on, send on to MH device.

This would probably be something you should submit to UDI as a ticket. They can then investigate if there's some way for IOX to handle this internally.

@bpwwer thanks MUCH Bob... that makes sense... BUT ... this all used to work flawlessly. Exactly as set-up and described - I had a KPL button trigger an MH only scene. I also had "bedroom all" that triggered the mixed scene. In fact, I have a few others also working right now - "accent lights" is a scene that triggers 13 MH only devices.

It stopped working a few months ago, maybe around the time 5.9.1 was rolled out?

I don't know then, if it used to work, nothing has changed on the MH plug-in.

Maybe try viewing what's happening when you press the keypad button using the diagnostics -> event view on admin console. That should show the incoming message from the keypad button and what the IOX sends out in response. If your system is busy doing a lot of stuff, it may be hard to pick those out of the view as it will also be showing all the other on-going activity.