Initial testing of Beta Plug-in

[dbwarner5]

@bpwwer Loaded the new plug in. 

Again took quite a while for discovery ~ 15-20 minutes.

Lots of errors.

Everything is pointing to "offline" in AC

No node for the Controller in AC

No grouping of nodes.. they ended up as their names alphabetically --> for testing purposes would be easier if they were grouped under the controller. 

One item did not come in with its name.. came in as Smart Bulb. 

Attached are the logs after I hit Discovery. 

Cheers!!

 

Meross_4-10-2025_121759_PM.zip

[bpwwer]

That's good data, thanks!

I see a couple of bugs that need to be fixed.  One, it's not making sure the device names are legal for the eisy nodes. There are a couple of the names that are too long and I see at least one with a character that's not supported in node names.  That's a pretty easy fix.

It also looks like there's a bug in the switch nodes.  I thought I had tested those but something slipped through. Shouldn't be a big deal to fix.

A lot of the errors are just the plug-in trying to connect locally to the device and failing.  I thought I had the logic right to make one attempt to connect locally and then mark the device as a remote device and not attempt local connections anymore, but that doesn't seem to be working given how much it's attempting local connections.  This is probably the biggest issue.

I've designed the plug-in so that it tries to mimic how the eisy handles Insteon and Z-Wave devices.  Thus, there isn't a "controller" node, just device nodes.  There's both pros and cons to doing it this way with the biggest con being that it does make it more difficult to find the nodes for testing.  The eisy only allows for a single parent/child relationship between nodes.  I'm currently using that for devices like the indoor/outdoor 2 outlet device and hub/sensor devices.  If I grouped them under a controller, I'd no longer be able to have the multi-outlet or hub/sensor groupings.  Trade-offs.

I think a lot of the time it's taking to discover is because of the check to see if the device is local. It looks like that takes about 30 seconds.

[dbwarner5]

Yes. All of my devices are remote not local. 
 

thanks! 
 

let me know when you want me to try again 

[bpwwer]

Published version 1.0.2.  I think I fixed the bugs and discover should be a little faster now.

[dbwarner5]

Cant update.. getting the following message. 

 

thanks.

[bpwwer]

Sorry about that.  I'm trying to use the trial licenses for limited time beta releases.   

The second release was supposed to have 30 days but it sounds like it's still trying to use the license from the first release. 

Try deleting your current version and see if it lets you "purchase" the new trial.   If that works, great.  If not let me know and I'll add a perpetual license. 

[dbwarner5]

Sorry, no that did not work. I had already tried that too, forgot to mention. thanks

[bpwwer]

Ok, I added a new purchase option so this will give you a permanent license for the betas and the final production release.

[dbwarner5]

installed 1.02

Still lots of errors. discovery still very slow as a result. 

Only found 9 devices.

Attached is the log package. 

thanks!

Meross_4-18-2025_14845_PM.zip

[dbwarner5]

Also the nodes that came in, did not have the correct names. 

 

Edited Friday at 05:59 PM by dbwarner5

[bpwwer]

Wow, I really screwed up with that version.

I think I fixed the bugs now and just published version 1.0.3.  You should be able to just re-install this version but you may have to delete the nodes from the admin console so it can re-create them with the correct names. I'm not sure if PG3 will update the names.

[dbwarner5]

Getting closer... 

-Discovery went much faster ~5 minutes

-names are still messed up

-Most of the devices will not respond in AC

-Values of on/ off are incorrect

Still lots of errors. 

Error logs attached. 

Currently the whole house is off, so all should be at zero below.. (node 20)

 

Meross_4-19-2025_114716_AM.zip

[bpwwer]

I don't have the plug-in configured to rename the nodes so it simply didn't rename any of the nodes that already existed.  I'll change that so that it does rename them to whatever is set in the app.

Looking at the "Chairs" dimmer that says it's at 20% I see it sending:

{'togglex': [{'channel': 0, 'onoff': 0, 'lmTime': 1745019070}], 'triggerx': [], 'timerx': [], 'light': {'capacity': 4, 'channel': 0, 'luminance': 20}}

It's sending a luminance value of 20 so what the plug-in is reporting is what the device is sending.  However, the device is also sending onoff as 0 (off).   The plug-in currently is assuming that the luminance value is what represents the current state of the device, but that appears to be not true.

This may also explain why you can't control them.  If the plug-in is only changing the luminance and not the onoff state, you won't see any change in the device.

I'm not seeing any place in the log where it tried to send a command to a device.

[dbwarner5]

yes. I think I downloaded the log before I started to play with on off etc. 

I can redo some on /offs and send you another log. 

 

[bpwwer]

You can wait and do that with the next release.   I'll try to get something ready in the next day or two.

[dbwarner5]

I had deleted the app so I reinstalled it to test the on offs.

Never could get past 17 nodes after 20 some minutes. 

Deleted and reinstalled it again. This time, couldn't get past three nodes.

Logs attached. 

thanks!

Meross_4-19-2025_24842_PM.zip Meross_4-19-2025_25956_PM.zip

[bpwwer]

The only ones I see failing in the log are the outlets, but I can't tell why they are failing.  For everything else, the plug-in is sending the commands to eisy to create the nodes and it's not getting any failures back.

I do see something that might cause some issues.  eisy has a limit of 14 characters for node names. Looking at the outlets I see a device "Outside Front " and another "Outside Front Main"  When "Outside Front Main" gets truncated to 14 characters, it's now the same as "Outside Front ".  I don't think the eisy cares that they're the same, but it could be a bit confusing for you.  Also, since these outlets have multiple plugs, the plugin will suffix each plug with an "_1" and "_2" to try and create unique names, further limiting the names to 12 characters.

[dbwarner5]

The Meross names get picked up currently by my Smartthings hub which then reports the names to Alexa 

 

so changing Family Room Cans to FR cans will make voice commands with Alexa difficult. 
 

let me play with it and see if I can “break” the chain and have different names at the Meross level vs Smartthings 

[bpwwer]

The name limitations are in the eisy but I don't think it really cares what the names are.  It mostly uses the node address to interact with nodes and the name is just there for you.

The plug-in will make sure the names it assigns to the node are valid (well it should now).  

To make the longer ones unique, maybe switch around the parts.  So instead of Family Room Main, use Main Family Room.   That may be hard to remember though for trying to control via Alexa.

Before you make changes that screw up your setup, let me send off a note to UDI to see if updating the eisy node name restrictions is something they'd be willing to do.

[bpwwer]

Actually, I decided to test setting the name to a longer value and it seems that they did increase the limit at some point.  Looks like it's now 28 characters.  I've updated the plug-in so you shouldn't have to change any names at this point.

[dbwarner5]

I missed your note, so already changed up the names in the Meross app.. Seems like smarthings naming is separate so I think I am ok on that.

Re-installed 1.03 and

-got stuck on loading GR table 

-Did not discover all of the devices, so after it stopped, I hit discover again at this time below:

-Plug in found several more devices but did not list the outlet Main, only the daughters.

-status in AC was wrong again. All devices are off.

 

- If I hit on or off in AC, there is a 15-20 second delay until the ac reflects the on or off. Light does respond quicker.

-A dimmer switch reports back as 100% when I turned it on via the smarthings app to 50%. 

Attached are logs.

Version on store is still 1.03 which is what I am running. 

thanks.

Meross_4-20-2025_15024_PM.zip