Initial testing of Beta Plug-in

[dbwarner5]

ok!  getting much closer!! 

-During loading, it seemed to have errors on all the "bulbs". The rest of the nodes came in quickly and w/o errors.

-Many of the lights came in with a value when they are all OFF. see screenshot.

-still have the repeating of 2 nodes, same 2 as before : O FrontMain 1 and O FrontMain 2

-played with one switch. Kitchen Lights. 

-It started by saying it was at 100%, but the light was off. I clicked off and then on and the light came on but the value didnt change. When I did it a second time, the light and the value changed correctly. 

-If I changed the level from 100 to 45% and clicked on set level, the light does not change, but the value in the AC changes. If I hit off and then on, it goes to zero and then to 45 and the light follows suit.  However, when I change the light level it causes the switch to go offline. The switch comes back on line when I hit off or on. 

-Lastly if I change the level in the app, the AC changes correctly as does the light. But if I change the set level in the AC, and turn the light on and off, it does not go to that level, it goes to the last level chosen. And sometimes it doesn't go off, or on. very glitchy. 

Let me know how I can help you better.  Do you want access to my PGX? and the meross app so you can see what is happening? 

Meross_4-23-2025_43316_PM.zip

[bpwwer]

I see the issue with the bulbs, they should still be responding to changes made in the app and to the controls on the AC.  But the error is what's causing them to so the brightness level instead of off when they are initialized.

You probably need to remove the duplicate nodes from the AC (right click / delete) and the plug-in will recreate any if necessary when it's restarted.

Looking over the log, it looks like the plug-in is doing what you ask it to. However I turned off a bunch of the debugging log messages accidentally so the log isn't showing what the Meross server is sending so I can't see everything that's happening.  I'm going go through things a bit more and I'll release a new version with the debugging enabled.  Or if you have a chance, you can enable debugging log from the PG3 detail page log setting.  Just set the level to debug and then run through some of the same steps you did above and send me that log. 

[dbwarner5]

-Nodeserver is stopped (from yesterday)

-turned all meross switches off via Smartthings

-opened AC

-switched plug in log to Debug

-started plug in @11:20am

-blue messages of “Configuring XX type YY” for each device

-seemed to get stuck on “configuring MB Accent type mss560x” @11:29am

-waited until it loaded all devices into nodes.Seems to have stopped at around 11;32am

-noticed I now have 36 nodes, correct count should be 34 devices The two extras are repeats of o FrontMain_1 and O FrontMain2. Both have only Node Name, with no Name section below it like the others.

-Back to AC, 6 devices are showing some state of on, but they are all off.

-Tried a Query on Doug's Rdng: nothing changed in AC. 11:39

-hit ON for same light at 11:40 in AC. Nothing happened. 

-Hit Off for same light at 11:41 in AC. Nothing happened.

-Turned same light on in the meross app. It is on at 20%

-hit off in AC. nothing changed. 11:42

-Changed brightness to 100% in Meross app, no change in AC.

-Turned light off in meross app, still no change in AC, still showing it at 20%.

-Switching to a different light Cabana. Hit on in Ac 11:44.. Nothing happened to light nor AC. Same with Set lelel, and off and query. 

-turned cabana light. on to 6% in meross app at 11:46.. no change in AC

-tried turning off via AC. Nothing. 

Will stop here for now as clearly something isnt working. Log attached. 

Thanks!

Meross_4-26-2025_114746_AM.zip

[bpwwer]

6 hours ago, dbwarner5 said:

-seemed to get stuck on “configuring MB Accent type mss560x” @11:29am

-waited until it loaded all devices into nodes.Seems to have stopped at around 11;32am

It looks like the plug-in lost it's connection to PG3 at that time.  The log doesn't show why.  There are a couple of errors right before that but I don't think they're related.  That's why it paused there, it was attempting to re-connect, which it did.

6 hours ago, dbwarner5 said:

-Tried a Query on Doug's Rdng: nothing changed in AC. 11:39

-hit ON for same light at 11:40 in AC. Nothing happened. 

The query looks like it worked, it simply sent the current values for the bulb to the AC and that looked successful.

The ON command made it to the plug-in and the plug-in supposedly sent the command on to the Meross server.  I don't have any logging happening to verify that.  But somewhere in there, it appears to have hung.  There's no response and and even though it should timeout and continue, it that never happened.

From this point on, I see in the log that you sent commands, but none of them get handled by the plug-in at all because the plug-in appears to be stuck processing the ON command above.

So there's nothing more you can do at this point.  I get another release published soon.

The details you provided are really helpful so thanks for that.

[bpwwer]

@dbwarner5  I just pushed version 1.0.5 to the beta store.

I made some pretty significant changes in this version to try and get everything working and to make it easier to fix any issues that are still present.

After install/re-installing this version, remember to check the log level setting, it should be 'debug' by default now, but if not, please set it to that before doing any testing.

[dbwarner5]

Deleted old version. Loaded new version. Found all devices in 8 minutes. Log set to Debug. Nothing showed up during node loading.

Outlet nodes seem to be lacking details: 

AC load and initial values: Values are all showing correctly as off.

Testing: 

Lanai Cans: on / off worked as expected. Set level is a bit quirky. I changed value to 100%, hit set level. The light was off, but then shows in the AC as 100%, but light is not on. Hit on, nothing happened. Hit off, and it goes to zero in the AC, then when I hit on again, it then turns the light on to 100%. Same behavior when I did set level to 80%. Lastly, when I hit On in the Meross app, it shows on to 32% but AC shows 80% . Actual is 32%. Just changed it back to 100% in the AC, now AC is not able to control the light at all. The PI seemed to have lost the connection, and then reconnected but is now unresponsive on that light. 

Tried a different light. PI is still unresponsive. Will restart it. Upon restart it is going thru the whole reconfiguration again. 

Restarted. Config finished. Same result on Outside plugs.

Lanai Cans: On / off in AC works as expected from both the AC and the Meross app.

Set level to 30% in AC. Again shows 30% in the AC, but light is off. Hit on, nothing happens. Hit off and AC went to Zero. Hit On and AC shows 32%. Meross app went to 100%. Actual lights went to 100%. Turned them off in AC. And back on. this time they went to 30% everywhere. Changed value to 100% in Meross app. Lights went to 100%, but AC did not change. Hit Query. No effect. Hit off in AC, lights went off. Hit On, lights went to 30% in AC but 100% in Meross app. Now AC is locked up again. Doing nothing. Meross app still is able to control the light. 

Attached is the log. Thanks! 

Let me know if there is anything else I can do to help. I am no longer at that house, but with a camera I can see what some of the lights are physically doing.

Cheers.

 

 

 

 

 

 

 

 

Meross_5-2-2025_111435_AM.zip

[bpwwer]

I found the problem with the outlets so that will be fixed.

The plug-in is becoming unresponsive when it is waiting for a response from the Meross server and it doesn't get one.  It is supposed to time out after 15 seconds (maybe that's too long?) but that doesn't seem to be working. I'm not really sure what to do about that yet.

The behavior you're seeing with brightness level vs. on/off is how the plug-in is currently designed.  The brightness level control and on/off control in the Meross API are separate controls.  So right now, setting the brightness is supposed to do only that.  If the device is off, changing the level doesn't turn it on.  

I'm guessing from your description that the App behaves differently and setting the brightness level does turn the device on (if it's currently off).   I can change the plug-in to do this which probably make more sense.

I don't have any devices that have brightness so I can't really test it.  But I did order a couple of the RGB bulbs so at some point I will be able to test.

I'm adding a custom parameter to force the use of the remote communication method.  Setting this will bypass the auto-detection code and should speed up the initialization a little more.  But it's still going to take time.