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.

[dbwarner5]

On 5/2/2025 at 2:44 PM, bpwwer said:

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

Are you waiting for me or am I waiting for you? No worries or hurry, just didnt want to leave you hanging if you were waiting for me. thanks.

[bpwwer]

You're waiting for me.

I bought a couple of the RGB Led bulbs and I think I have those working correctly.  I need to apply some of the changes for the dimmers (and switch, I think).

Other projects have interfered so I haven't had time to finish up and release it. 

[dbwarner5]

@bpwwer  Good morning.. I upgraded to the latest version. 

I am not at the home where the Meross lights are but can see one set via a Ring Camera. 

When I turn it on (long delay), it comes on as expected. If I change the light level in the A/C and then click on Set Level, the light GOES OFF first, and then comes back on, then adjusts to the new setting..

See video attached. This is changing from 40% to 100%. 

Thanks! I will be at this house next month and can continue to do more testing. 

[bpwwer]

I don't see anywhere in the plug-in code where it would send an off command before sending the level command.  When you execute the command to set the level, it just sends the command to set that level to the device.

I haven't tried doing any level changes from the plug-in, but I do have a bulb that is now part of a scene in one room of my house, which is why I made a few changes lately so I could get that working correctly.

[dbwarner5]

@bpwwer Also forgot to mention that the Meross NS has quit and restarted 4 times in the last 3 days. 

Attach is log.

Dont know what to say, but you can see in the video that it turns the light off. Then after a pause, back on, then brightens it. does it everytime I adjust the level. 

Thanks

 

Meross_9-25-2025_120052_PM.zip

[bpwwer]

I see the disconnects in the log.  The error is:

Unexpected MQTT disconnect. Reason code: Unspecified error. 

So no real information about why.  The MQTT connection is managed by a common interface library that is used by all the plug-ins so it's probably not something the plug-in is doing that's causing it.

I also see quite a few "meross:send_to_broker: Timeout waiting for respsonse from device", which means the Meross broker isn't responding, at least not within 15 seconds.  I could increase that, but 15 seconds seems like more than enough time for the broker to respond.  I have not found that the connection to the Meross broker to be all that reliable.

Does that log include you changing the level of the light?  If so, do you know approximately what time you were doing that. The log is fairly long so searching through the whole thing looking for a level change is a bit more than I want to do right now.

[dbwarner5]

I will repeat the light switch and note the time and resend the log. 

I am working with Michel and gang on the MQTT connection error as it causes most of my NS to fail / restart. Strange that only the Meross one is doing it currently. They are going to increase the time before error so that if, as in my case,  I seem to have an unstable internet connection, it wont kick these out. 

6:02.

Light was on, so turned it off, then to 40 % then to 100% then off.

 

Same behavior. 

Meross_9-25-2025_60235_PM.zip

[bpwwer]

This device is a dimmer switch, right?  I have a note about dimmer switch behavior:

Quote

dimmers work by controlling both on/off and brightness.

The devices brightness value (luminance) controls how bright to set the device, the onoff value tells us if the device is on or off. When the device is off, the luminance value is not automatically set to 0, instead it is the value that we should set when the device is turned on.

So when setting a level on a dimmer, I first send the command to set the level then I send the command to turn the device on (in case it is off).

It doesn't seem like that should be causing it to turn the device off unless the set level command does that automatically.

Can you try the bright and dim commands?  They should bump the luminance 1% up or down.  This command will only send the command to set the level so I'm curious if this will cause the dimmer to turn off or simply set the level.

It's possible that the various models of dimmers behave differently.  I don't have any real documentation from Meros on how any of this works so all my info is coming from other projects on github.

I did find the log entries where you send a OFF, ON, Level 40%, Level 100% but the log doesn't show anything that would indicate that the dimmer was set to 0% or off other than when the original OFF command was sent.

[dbwarner5]

Yes its a dimmer. 

at 12:24 on the 27th, Light was ON.. I turned it Off, and then could not get it to respond again.

Rebooted. 

Took 15 minutes to rediscover everything. 

At 12:38 I turned the light on 100%. Hit Dim, the light turned off then back on to 99%. Then became completely unresponsive again. 

Two logs attached. One up until reboot. Second one after reboot. May be duplicative, but wanted to make sure you had everything. 

cheers. 

 

Meross_9-27-2025_122602_PM.zip Meross_9-27-2025_124239_PM.zip

[bpwwer]

At 12:24 after you turn the light off, the last message from the plug-in is "waiting for response from device".  There aren't any error messages and it doesn't show that the response timed out so I really don't know what happened, it seems like the plug-in got stuck at that point but there's no information as to why.

At 12:38, when you dim the device, it does dim, but the fact that it turned off first seems to be device behavior.  All the plug-in sends in this case is a set level 99% command.  It looks like setting the level of a dimmer (or at least that model of dimmer) causes the dimmer to turn off and then ramp up to the set level.  I don't believe the bulbs have this behavior.  Maybe check if there's a firmware update for the dimmers.

After that it hit a bug in the plug-in and the plug-in crashed.  I've fixed the bug.

As I mentioned before, there are a lot of time outs waiting for a response from the device (or rather a response from the Meros broker service). That's going to cause some issues although most of the time, the plug-in doesn't really care and assumes the device was set based on any commands sent.  It could effect polling so if the device is controlled via the app, the plug-in may not see those changes right away.

I'm a bit hesitant to increase the timeout value, because when it's waiting for the response, the plug-in is basically pausing until it either gets the response or it times out.