dbwarner5

If you open up PGX adn the Plug in for the elk and go to the NODES tab... for each device, the system code you need will be on the right. There is "copy" icon. If you click on that icon, it will copy the correct format you need for the plugin's zones and status. You will need to update each line in your custom notification to display the correct "address" to the new nodes. The zones/devices you are using above are part of the old / discontinued module, vs the new Plug-in nodes.

Its still a good idea to regularly to the backups that were suggested, so that if your unit someday dies, you have them all ready to go.

@srjacob Be sure to to open up the ELK desktop program and get all your "connection" information copied, such as ip address, passwords, and settings in the Elk MEXP module. This will be needed to populate the config files in the Elk Plug in. By the way , the elk plug in works really well. Have not had any issues with it, but it does require rewriting most of your elk programs. Some of them you can do a find / replace in. Key as mentioned above is to right click on the top of your program hierarchy and click copy folder to clipboard and then past it into a text application. This way you can easily see what the original program was meant to be. If you use Resources, it's good to also export a copy of that as well.

@teverk am not sure why you are looking for a 3 way switch. Any normal Insteon switch can be wired and configured to work as a 3 way. Insteon has dimmer and on/off switches available. https://www.insteon.com/wall-switches

UPDATE: @Panda88 So this time, I Stopped the PI... did the update and got this: But then when I hit START... it reverted back to 1.2.5:

Having hte same issue.. Everything appears to go thru the update process: asks for slot, asks to update. Plugin restarts, etc, but version stays on 1.2.5. thanks. attached is log set to info YoLink_11-18-2024_111432_AM.zip

Found it. Was able to "install" right over top of the old one so did not have to recreate names or configuration. Working. thanks!

FYI.. Just tried to update vis UDM / settings / plugins and getting ERROR, invalid node server. Hit the update button directly on PGX.. goes to a blank screen. Went to purchases.. not showing up Went to non production store, not showing up Went to production store, not showing up. thanks.

Would th number of lines also have an impact? All the programs should have the same number of lines, even if that means adding another $test_X = 0 at the top. This would be to test if both programs start at the same time in your test 1, but program one has an extra line to process and hence turns the test_2 to 0.

@Jimbo.Automates Worked!!! Shows and operates as expected again! Thanks!

I dont think it is that important. Just something I had to figure out.

Ok.. that makes more sense then now.. Your motion sensor could be turning off, which would also stop the program, and then back on, restarting the program. How do you have that set up?

@smorgasbord Try making your if statement Bathroom Motion-Sensor' is switched On And $RecirRanRecently is 0 And then eliminate the first line in your THEN. As you have it written, when it hits the first WAIT, the IF is re-evaluated. Since you just changed the variable to a 1, it fails the IF and turns False, stopping the program.

If your goal is to have Program 2 run "in the middle" of program 1, you can put a wait in program one, right after the "call" for a length of time you need for program 2 to complete. Just be aware that program 2 can NOT change the If state of program one in any way, or program one will either start over or run false etc, as it will be re-evaluated at the WAIT.

Solved it! thanks!

Yes. thanks.

Two other options: 1). A long IF with ALL the lights you have in that scene separated by ORs, that if switched off (during the time period you want ), then maybe wait 30 seconds and then turn the scene back on. example: IF From 9pm until 6am next day AND ( Light A is switched off or Light B is switched off of light c is switched off ) THEN wait 30 seconds,. turn scene "nighttime" on Or 2) Just turn that scene on every 10 minutes during the duration you want it on, so it will "self correct" w/o any monitoring needed. example: IF From 9pm until 6am THEN repeat every 10 minutes Turn "nighttime" scene on. The advantage of this technique is that you can have in your scene all the other lights that you want off to turn off as well, again w/o monitoring I have use both techniques above for different scenarios. For my Bedtime scene. I probably have 30 lights included in it so I use the "every 10 minutes" technique but I think I use 20 minutes so that if someone goes out to the kitchen and turns a light on to see they have in theory anywhere from 0-20 minutes that the light will stay on, and then it goes off. Not always ideal, but it works w.o monitoring all 30 lights as to which are turned on, which are turned off etc.

Have this program below. Running THEN does not change the Elk armed status as expected. When this program runs, the Armed Status is " Armed Away. Then Set 'Elk Main House' Set Armed Status Armed Stay However, if I add a disarm, it runs correctly. See next: Then Set 'Elk Main House' Set Armed Status Disarmed Wait 2 seconds Set 'Elk Main House' Set Armed Status Armed Stay Is this a function of the ELK or the Elk plugin? thanks.

See answers in CAPS Do all of your temp data jive with the admin console or the webcontrol console? YES Is the heartbeat switching between -1 and 1 every shortPoll? YES Does the time/date update also every shortPoll? YES, buts it one hour off. (DST?), Eisy was correct I quess it would be easier to have asked, is the plugin working fine in UDM, just with the errors? YES appears that way.

could have it have anything to do with the Json line? mine is blank.

@TJF1960 FYI.. when I go to UDM and do a Sync.. the plugin throws an error for each node. So with 2 plug ins running, I get 72 errors.. See below for example of first page.

Updated to latest version and restarted. Port held.

Whew.. glad I wasn't losing my mind!! THANKS!!

Try doing a restart and see if it stays at 84

Under Tools / Diagnostics / Show PLM Link table.... then hit start. I am not as knowledgable as others on this forum about this, but I am pretty sure if you have programs running or adjustments happening to your system at the same time, it will throw the count off. So you need to stop your programs and let it run. Just ran mine.. 886.... big shortcoming of the PLM