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

@toptierweb After following @Techman's advice, I usually like to past this into a browser: http://<eisyip address>:8080/admin.jnlp, substituting the eisy IP address into the string. This will put an admin.jnlp file on your desktop. Clicking this shortcut will then be a direct local link right into your Eisy, skipping the whole launcher process. Only works for local connections though. Enter your local username and password. cheers.

take a look at this post and see if this helps.

@hart2hart the easiest way to avoid the water hammer that @IndyMike mentions is to “overlap” each section of your programming ie: turn on the next valve before shutting the previous one if you look at my programs (I chose to break each one out separately vs one long program) you can see the overlap concept good luck!

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

ok will load it and see how it works. thanks! Oops,, not showing in the store yet.

Two questions for you on your program: 1) Looks like you are setting the counter to the same variable (minutes for that zone) each time. This means each zone will run the same amount of time? Dont you want a separate variable for the minute setting for each zone? $Minute_Counter_I = $Irrigation_Run_Minutes_I 2) when each zone ends, what happens to your pump? will it momentarily shut off until the next program starts again? If that is the case, you will cause unusual wear on your pump and a higher electric bill. But if using municipal water, then no problem.

@hart2hart I have a set of programs to run my sprinkler system. The overall concept is that I can trigger "groups" as on or off, I can set minutes per zone, and I can set a % multiplier to adjust for rain / dry conditions. For example, if I want the garden to run every other day, I can set a flag for that frequency and assign minutes for that zone. Then I have an overall multiplier that is 100% for normal operations. I can easily change the 100%, the minutes or the frequency per week. This concept applies to four groups: garden, lawn, pine trees and bushes drip line. For the lawn, each zone has its own program with a waterfall effect where when zone 1 is completed, it calls the zone 2 program, etc until the last zone is done and it stops the sprinkler system. The other "groups" only have one zone each so they are much simpler. Also for the lawn, I have two sets of sprinkler times so that if I need a second run on a certain zone ie: I've laid some grass seed that needs more frequent watering etc. Each group has its own folder which allows a high level of"on/off" test. Here are the groups. The groups are also under an umbrella folder that disables the whole system ( for in the winter etc) An example of the sprinkler 1 folder test: 1 is enabled, 0 is disabled. Sprinkler 1 530am - [ID 02BD][Parent 0162] Folder Conditions for 'Sprinkler 1 530am' If $Sprinkler_1 is 1 Then Allow the programs in this folder to run. These are the zone controllers for sprinkler 1. The last three programs determine when they run: daily, odd days or 3 days per week. Here is the program for 3 days a week. the variable days is 3 which is the deciding trigger. In the 7 days a week, that variable is set to 7 and for odd days it is set to 2 which triggers the other programs. Sprinkler 1 3 Days - [ID 02D6][Parent 02BD] If On Mon, Wed, Fri Time is 2:30:00AM And 'Elk Non Alarm / Rain Sensor' Logical Status is Normal And $Sprinkler_1 is 1 And $I_Sp1_Days is 3 Then Run Program 'SP1 1Start / Stop' (Then Path) This then starts the "waterfall effect by running the following program: SP1 1Start / Stop - [ID 0338][Parent 02BD] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'SP1 Lake 1' (If) Else Run Program 'SP1 xStop' (Then Path) So then zone one (sp1 lake 1) runs. $I_Sp1_Lake is the minutes I have set for that zone. If it's zero, the Else runs and immediately goes to the next program in line. I initiate the second zone before stopping the first so the pump stays running. There is a separate program that monitors if any of the zones are on, the pump turns on. SP1 Lake 1 - [ID 02C4][Parent 02BD] If $I_Sp1_Lake_1 > 0 Then Set 'Elk Controller and Outputs / Sprkl Lake 1' On $I_Sp_Counter = $I_Sp1_Lake_1 $I_Sp_Counter *= $I_Sp1_Percent $I_Sp_Counter /= 100 Repeat While $I_Sp_Counter > 0 Wait 1 minute $I_Sp_Counter -= 1 Repeat 1 times Run Program 'SP1 Lake 2' (If) Wait 4 seconds Repeat 2 times Wait 2 seconds Set 'Elk Controller and Outputs / Sprkl Lake 1' Off Else Run Program 'SP1 Lake 2' (If) In this program the variables are as follows: -Counter... gets used to match the minutes for that zone. Is used in each program -$I_SP1_Lake_1 is equal to the minutes I have set for that zone -$I_Sp1_Percent is equal to the "adjustment %) I want for that group, ie 100%, 75% etc. This program counts down and then calls the program for zone 2 which is SP1 Lake 2 This continues down the list from the screen shot above until it hits the last zone in that group. SP1 Wild Flowers - [ID 02F1][Parent 02BD] If $I_Sp1_Wild_Flowers > 0 Then Set 'Elk Controller and Outputs / Sprkl Wild Flowe' On $I_Sp_Counter = $I_Sp1_Wild_Flowers $I_Sp_Counter *= $I_Sp1_Percent $I_Sp_Counter /= 100 Repeat While $I_Sp_Counter >= 1 Wait 1 minute $I_Sp_Counter -= 1 Repeat 1 times Set 'Elk Controller and Outputs / Sprkl Wild Flowe' Off Wait 4 seconds Repeat 2 times Wait 2 seconds Run Program 'SP1 xStop' (Then Path) Else Run Program 'SP1 xStop' (Then Path) This runs the following program which is set up as a safety to ensure all zones are actually off. SP1 xStop - [ID 02D3][Parent 02BD] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Elk Controller and Outputs / Sprinkler Pump' Off Wait 2 seconds Set 'Elk Controller and Outputs / Sprinkler Pump' Off Wait 1 second Set 'Elk Controller and Outputs / Sprkl Deck Spray' Off Stop program 'SP1 LDeck Sprays' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Lake 1' Off Stop program 'SP1 Lake 1' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Lake 2' Off Stop program 'SP1 Lake 2' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Lake 3' Off Stop program 'SP1 Lake 3' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Lake North' Off Stop program 'SP1 Lake North' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Lake South' Off Stop program 'SP1 Lake South' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Road 1' Off Stop program 'SP1 Road 1' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Road 2' Off Stop program 'SP1 Road 2' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Road North' Off Stop program 'SP1 Road North' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Road South' Off Stop program 'SP1 Road South' Wait 1 second Set 'Elk Controller and Outputs / Sprkl Wild Flowe' Off Stop program 'SP1 Wild Flowers' I have set up favorite screens in UDMobile to then easily control everything . On this screen I can enable / disable the whole group, choose the frequency per week, choose the % multiplier, and lastly adjust each zones minutes. For the other "groups", they all only have one zone each so I skip the whole multiplier concept because it's just as easy to adjust the time. Here is a screenshot of UDM for the Garden. In summary, using variables and wait times, what you want to do is easily accomplished. I hope this helps! Feel free to reach out if you need further help in setting this up!

Looking through the nodes that got created I noticed a few that did not have a "name" section below them. They are all outlet related devices. Also two nodes got repeated in the node server: O Mainfront1 and Omainfront2. See screen shots.

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

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

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

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.

@someguy The easiest way to get the variable you want from a node server into an email is to go to the PGX plugin and hit the copy symbol next to the variable you want and then past it into the program. For example if I want the barometric pressure of my weather flow plug in, I would click on the copy symbol and it will copy the correct string to paste into an email. I get notifications throughout the day when traveling.. I use pushover vs email. but here is an example of the program and the pushover message that gets sent. House Status when away - [ID 00E2][Parent 0203][Run At Startup] If $Away is 1 And ( Time is 8:30:00AM Or Time is 12:00:00PM Or Time is 5:00:00PM Or Time is 9:00:00PM ) Then Set 'Notification Controller / Service Pushover Other' Send Sys Custom With Params Priority=Normal Content 24 Notification ID (ID=24) Else - No Actions - (To add one, press 'Action') Notification in custom notifications looks like this: Security: ${sys.node.n014_area_1.ST}, ${sys.node.n014_area_1.GV0} Doors: -Front: ${sys.node.ZY010_1.ST} and ${sys.node.n014_zone_1.ST}. -Mud Room: ${sys.node.ZY011_1.ST} and ${sys.node.n014_zone_15.ST}. -Back Grg: ${sys.node.ZY012_1.ST} and ${sys.node.n014_zone_12.ST}. -Mstr Bedrm: ${sys.node.n014_zone_10.ST}. -Slider: ${sys.node.n014_zone_33.ST}. -Screen Porch Entry: ${sys.node.n014_zone_5.ST}. -Screen Porch North: ${sys.node.n014_zone_9.ST}. -Screen Porch South: ${sys.node.n014_zone_4.ST}. -S. Garage: ${sys.node.n014_zone_7.ST}. -M. Garage: ${sys.node.n014_zone_3.ST}. -N. Garage: ${sys.node.n014_zone_8.ST}. Main Thermostat: -Set: ${sys.node.ZY004_1.CLISPH} -Temp: ${sys.node.ZY004_1.ST} -Mode: ${sys.node.ZY004_1.CLIMD} -Status: ${sys.node.ZY004_1.CLIHCS}. Upstairs Thermostat: -Set: ${sys.node.ZY005_1.CLISPH} -Temp: ${sys.node.ZY005_1.ST} -Mode: ${sys.node.ZY005_1.CLIMD} -Status: ${sys.node.ZY005_1.CLIHCS}. Main Level: ${var.1.92} Minutes Upstairs: ${var.1.94} Minutes Day 1: ${var.1.98} Day 2: ${var.1.99} Day 3: ${var.1.100} Day 4: ${var.1.101} Day 5: ${var.1.102} Master Fireplace is: ${sys.node.1D 5A C0 1.ST} Water Pump is: ${sys.node.ZY013_1.ST} Temperatures: -Outside: ${var.1.28}ºF -Garage: ${sys.node.n019_ts5.ST} -Hot Tub: ${sys.node.n016_8b4c01000a1c2e.CLITEMP} -Mstr Bedrm: ${sys.node.n019_ts4.ST} -Family Room: ${sys.node.n019_ts1.ST} -Great Room: ${sys.node.n019_ts3.ST} -Office: ${sys.node.n019_ts2.ST} -Lake: ${sys.node.n016_8b4c0100079d9f.CLITEMP} -House Refrig: ${sys.node.n016_8b4c01000ba53e.CLITEMP} -House Freezer: ${sys.node.n016_8b4c01000ba56d.CLITEMP} -Garage Refrig: ${sys.node.n016_8b4c01000ba218.CLITEMP} -Garage Freezer: ${sys.node.n016_8b4c01000ba4d1.CLITEMP} Weather: Temp: ${var.1.28}ºF, High: ${var.1.38}ºF, Wind: ${var.1.11}mph, Gusts: ${var.1.31}, Wind Direction: ${sys.node.n001_285149.WINDDIR} Rain: ${var.1.34}%, Clouds: ${var.1.35}% ${alert.time} Output looks like this Hope seeing a real life example helps!

An alternative way to using the virtual switch concept above is to simply replicate part or all of the scene in your If statement: For example if in your scene you have switch 1 @50%, switch 2 @100% and switch 3 @100%, Then put in your If statement the matching values of the scene. Sometimes in a scene I may have just one switch turn on to a very unique value like 98%. Then I only check to see if that one switch is at 98%, which lets me know that scene is on. The drawback to this approach is that you have to make sure you keep the two items "in sync" --> ie 98% in the scene and 98% in the IF statement. Other than that, it's a pretty straightforward and easy way to accomplish the same as a virtual switch.

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

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

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

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

try first "quitting" the Alexa app on the phone by swiping up and killing hte app. If that doesn't change the linking ability, try to restart your phone and try it again.

Cant update.. getting the following message. thanks.

Yes. All of my devices are remote not local. thanks! let me know when you want me to try again

@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 just updated the plug in.. will start to test it. THANKS!!

Oops.. typo.. meant to say that program 2 is set to run at startup. And program 1 runs at multiple times of the day to ensure prog 2 is actually running.