DennisC

In the Main tab the Elk Outputs are not listed under "Area x", but under "Elk Controller". Therefore, in a Program you need to go to: Status - Elk Controller / Output x. Then new selections popup and you can select Status or Default on Seconds. From there you can select operands (<,>,=, ect) or variables.

Elk keypad presses not being recognized can be worked around by creating Elk Rules in ElkRP2 to turn on an output when pressed. That's how I got around it. Just be sure to turn it back off, either by only turning it on for a few seconds in the Elk rule or having the Elk Nodeserver turn it off.

Think it depends on the type of message. If you are triggering the message from a program, you can set it there. If from a NR, you have to include it in the string at the top. There's an example on the Configuration page of PG3 of the Nodeserver.

After updating, I had no issue with the indicatoright blinking. However, I did have to go in and re-save programs. I found some of them were not working.

Use the DHCP reservation in your router to make an IP address permanent. See the instructions here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Network_Settings

Actually, I do both and set 2 different variables on my ISY, just in case. I am detecting the change in connection to my specific wifi network. I also am using Tasker for this. I have a 2 minute waiting period upon leaving my wifi area to prevent bouncing in and out. I have not experienced any issues when the screen goes off.

I have been using geofencing via Tasker on Android to tell my ISY when we are home for several years. A couple of years ago it stopped working but for the last two years it has been solid on 2 Samsung Galaxy S20+ phones.

Have you tried right clicking on each device and running Restore device? There might be a problem with the links.

I won't be able to try this until the end of next week since I will be traveling until then.

For PG3 Nodeserver upgrades, just stop and restart the Nodeserver. The newer version will install itself with no impact to programs. For that matter, if you delete and then reinstall the same Nodeserver in the same spot your programs are also not impacted.

After clicking on manually upgrade and get to the part that the file finder window opens, select the zip file you downloaded and process to upgrade. You shouldn't be changing any file name. You should be using the zip just has it is without modification or unzipping.

Try changing power for PLM to a different circuit. Something near by may be interfering. Have you tried power cying Polisy? Or, your PLM's are bad.

If you have Insteon support checked, saved, rebooted and PLM still shows not connected, then either the PLM is no good or you have some kind of filter on the power line interfering with Insteon signal. Make sure you are not on UPS power with the PLM. You can also try a factory reboot of the PLM. However, if it was from a working system it will require running Restore PLM afterwards.

If this is on IoP, UD is aware of it. I reported it last week and was told they would look at it.

@macjeff, One thing about Insteon before you perform a reset, check the PLM Links. Go to Tools - Diagnostics - Show PLM Links Table. Make sure you have links shown. If not, check Tools - Diagnostics - PLM Info/Status and see if PLM is connected. If not, try a Restore Modem (PLM).

@Michel Kohanim, Since the log error log in IoP is messed up, making it hard to read, I might have cleared the log since last I tried making a change. Do you want me to clear the error log and run the test again before sending to you?

No, clicking on N/S name for WirelessTags in PG3 rests in a 404 error.

Any chance you can get a look at the error log? The formatting is not good but might give you an idea. Sounds like you might need to do the restore over.

I have two properties set up and decided to use new USB PLM's for both of them. My original thought was I might need to run both IoP and 994 for awhile. As it turns out, except for one 994 running WOL, I am completely on IoP now.

As I said, not working right doesn't give us anything to go on. You need to describe exacy what is happening if you want help. Another suggestion for Zwave is to turn it off, save, remove done and reboot. After it starts up, reconnect dongle, enable Zwave, save and reboot. So, it takes a few minutes after reboot for Zwave to show available.

Just updated to this version. Not sure if you had a chance to fix the link from the Nodeserver store. If you haven't that's ok, if you have it's still not working.

Can't offer a suggest about your isses with IoP without more information. As for Zwave, make sure Zwave is enabled on the configuration page, then save and reboot. If that doesn't work try power cying your Polisy.

I installed v 3.0.13 this morning. I will check it out tomorrow.

I can confirm this works. I am doing this for one nodeserver at two locations that I am running IoP.

I can confirm seconds since update going to 3600 after a query. Saw it happen today.