DennisC

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.

Don't know if this helps, but the only time I have seen out of range is when the battery has died and the time exceeds the reporting window.

If you check the Configuration page on IoP, the "Portal" tab is probably missing. You can also go to Help - Manage Modules to see if it says all up to date. I had the same issue when I did my two units, this is a known bug. Completely finish setting up your IoP, then send an email to UD with your UUID # and tell them you restored a back up from ISY994 to IoP, lost your previously approved IoP license and the "Portal" tab is missing from IoP Configuration page. Also, let them know if you want your ISY 994 Portal license transferred to IoP, or just to restore your previous IoP Portal license. They respond very quickly during working hours. After they do what you need to do, you will need to go to Help Manage Modules and it will ask if you want to install. Or, it might pop up to install after logging in. Give it a few minutes, then approve and shortly afterward, your portal will show on line again.

Whenever you add a Zwave device, it is best to exclude then include all on the device you want to add the Zwave devidc to. The way I proceeded was to leave ISY994 alone and exclude using IoP, then include on IoP. After all devices were included on IoP, you can disable or delete in ISY994. The Zwave device in ISY994 will no longer work because a Zwave device can only be synced on one Zwave controller, hence why the exclude is done as first step on new controller. Any Zwave device connected to IoP will be deleted if you restore a backup from ISY994 to IoP. Since the backup doesn't handle Zwave, Zwave is disabled automatically when you complete the restore steps. You need to enable Zwave and then save and reboot. It's not hard, just follow the script originally posted by UD.

I wanted to add - Once you have included your Zwave devices in IoP, you can either disable or delete them in ISY994. Also, once done, I ran Zwave - Update Neighbors.

I questioned Michel about upgrading firmware of Zooz stick and he replied that UD has not tested the updated firmware with IoP and suggested not upgrading. I followed the suggestion and stayed with the firmware the stick came with. No, go to IoP and exclude then include. It is all done from IoP. Good luck.

It looks IoP omitted the formatting we use to have.

In the past week I moved both my sites over to IoP and both sites had some Zwave, although not a lot. One site has 4 Zwave devices, inuding 1 Schlage lock and the other has 3 Zwave devices. All in all it was fairy easy. Plug in the Zooz Zwave stick, select Zwave on the configuration page and reboot. Next place IoP in exclude mode, and exclude a Zwave device. Followed by include Zwave device. Each site took less than 10 minutes.

Glad you got it working.