gzahar

I just excluded and re-included again to test. Ended up in same situation,works but doesn't complete interview (and reports temp in C). I did have a strange situation the first time I tried re-including. Device showed that it need to write updates to device in admin console (but it appeared to be working as before). It would fail every time I selected write changes and I could not exclude the device (even after factory resetting). I had to remove failed node and then included again with no problems. Are you getting to the point where it asks for the security pin? Or not even that far? Edit: I was surprised that the device kept reporting motion to my Polisy after I went through the factory reset. Not sure I believe it is doing a reset, but I really don't know the specifics of how Zwave networks operate.

Included on Polisy/Zmatter. But doesn’t complete interview. Works ok as far as I can tell.

So the probes are hard wired to sensor (no plug)? I guess that would make sense if they were made for unprotected areas. Also, can they graph collected data like the Tags do? How much data is retained to view? Anywhere close to a year?

Did you try unchecking Zwave support and rebooting? Then add back Zwave. Probably would require another reboot once other controller is added. Just a thought. I have no idea…

Obviously cloud based for the app, not sure about the node server. Probably the same. I haven't used the Tag node server (and may not use the YoLink node server), is it local? There is some local communications based on the following: What is YoLink Control or Control-D2D? Control D2D (device-to-device) pairing allows for one or more sensors to be paired with one or more other sensors, in a way that they will respond and operate automatically, even with the loss of WiFi, internet and AC power. For example, leak sensors can be paired to a valve controller, so that the water is shut off automatically when a leak is detected. This is a unique feature not found in other smart water leak systems. If your smart system absolutely must perform, no matter what - power outage, loss of internet - you can depend on YoLink Control-D2D!

I could possibly use my existing Tag hub, but I can get a complete YoLink setup including hub, sensors, and node server for less than just the Tag sensors. I also like the additional devices YoLink has. Looks like I'll give that a try. Thanks

Not sure what eisy gets you over Polisy. I moved to Polisy looking for improved Zwave operation using Zmatter. You might consider first going to Polisy/Zmatter and then later eisy/Zmatter. Regarding the occupancy node server issues, it may have been a similar situation where IoX already had the node server pointed to the old portal instance (not sure what migration options were available or you attempted here). Next time, I would go back to IoX Node Server configuration menu for Occupancy and delete it, before attempting to install it to eisy. (Doing it this way, you will end up with new URLs that you need to enter into your devices.)

Trying to monitor temperature on a hot water pipe. First thought is to connect a K-type thermocouple (they are readily available and economical) to something that can be monitored by ISY (z-wave, node server, rest i/f, etc.). Preferably not battery operated, but I can live with that. Could also be self-contained system that reports over network to app if that is cheaper or better solution. Z-wave would be last choice (sensors would be no where near my current network build out). I see Wireless Tags has a device that will accept a thermocouple and I already have a tag manager, but not sure if sensors will reach the distance I need. A 2nd tag manager and their sensors would do, but would like to see if there are better solutions that some have found. Thanks.

Are you using the Portal node server with Locative? What seems to be the issue?

I’m not suggesting you edit the IP address in IoX. Just saying you can confirm it still thinks Polisy is managing the node server. Not sure if changing the IP address there would work or not? As Bob says, it is probably better to restore or re-install each node server. When I went from PG2 to PG3 most of the nodes kept the same name, so program edits were minor. From PG3 to 3x I doubt you would have any.

Did you delete the node servers from Polisy or power down? If they are still running there and pointing to the same IoX as eisy this would happen. Go into IoX node server menu, and select 'configure' then any node server and see where it is pointing (IP address).

My bet is it comes over from IoX. 1 is main entity you control on/off 2.3.6 are on most Insteon devices in AC (even devices that don't use them; like backlight) 5 probably mirrors whether you have the device enabled or disabled in AC. (and your ability to change that in HA) 4 ??? I'm sure you could build something around those in HA just as you could in IoX or hide/disable them in HA if you want.

You can just plug that USB module into Polisy. You don't have to mount the board internally.

Is it checked under configuration?

Since installing the HACS ISY integration, I have been installing HA updates as available. Most recently 2023.2.1 Is this overwriting the HACS install? Should I avoid HA updates for now or reinstall the HACS component afterwards?

There’s now a communications speed setting in the Zwave menu.

Update w/interview didn't make a difference. I'm tired of updating my programs every time the ZY address changes, so I'll hold off on remove/include for now (until I hear it will fix something). The X-ray always shows Interview as not done, but here is output from event viewer. Thu 02/02/2023 04:38:55 PM : [ZW-INTERVIEW-37 ] Add interview request for 46 Thu 02/02/2023 04:38:55 PM : [ZW-INTERVIEW-37 ] Interview started for 46 Thu 02/02/2023 04:38:57 PM : [Device 46] Waiting on interview complete (timeout in 392) Thu 02/02/2023 04:38:59 PM : [Device 46] Waiting on interview complete (timeout in 397) Thu 02/02/2023 04:40:29 PM : [Device 46] Waiting on interview complete (timeout in 26) Thu 02/02/2023 04:40:31 PM : [Device 46] Waiting on interview complete (timeout in 0) Thu 02/02/2023 04:40:31 PM : [ZW-INTERVIEW-37 ] Device 46 : Interview Done with some non-conforming features : total=22 successful=20 attempted=22 Thu 02/02/2023 04:40:32 PM : ZWAVE-WORKQ-34 Queue sync device 46 (initialize) Thu 02/02/2023 04:40:32 PM : ZWAVE-WORKQ-34 Start sync device 46 Thu 02/02/2023 04:40:32 PM : [ZWAVE-SYNC 46] Attempting to reuse ISY files/objects for Z-Wave device Thu 02/02/2023 04:40:32 PM : [SYNC-DEVICE 46.0] Set commands are accepted by the controller Thu 02/02/2023 04:40:32 PM : [ZWAVE-SYNC 46] Not multichannel Thu 02/02/2023 04:40:34 PM : [SYNC-DEVICE 46] Initializing associations to ISY Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-35 Queue write device updates for node 46, full=false Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-34 Finished sync device 46 Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-35 Start write device updates for node 46, full=false Thu 02/02/2023 04:40:35 PM : [ZWAVE 46.0] Association Set in group 1 : Controller 46.0, Responder 1 Thu 02/02/2023 04:40:36 PM : ZWAVE-WORKQ-35 Finished write device updates for node 46, full=false

It doesn't seem to have fixed the update issue. Disclaimer: I didn't catch the beeps and pull the power. IoX did reboot and the AC came up showing the new firmware/UI version (w/o needing to clear Java cache either). Possibly some other updates may happen when/after rebooting the whole system or clearing Java.

Is there going to be a separate thread for 5.5.5 or continue using 5.5.4? Also, in the installation notes (not new to 5.5.5) it says: Launch the Admin Console, go to the Configuration tab, click on Update Packages. Warning, this might take a while depending on how current your OS is Once completed (4 beeps + 1), unplug Polisy I thought in the past it was recommended to not just pull power on Polisy (/eisy by extension) but use a shutdown command first. Has this changed?

Copy Folder to Clipboard.

On the configuration page, make sure Insteon support is still selected (did you hit save before rebooting). Restore Modem (PLM) is under the File menu. Try Tools, Diagnostics, PLM Info/Status. Edit: Did you reboot the eisy or just the IoX? Probably need to reboot eisy.

You would have a Zwave menu in the admin console and could check the version/firmware under Zwave>Advanced>Version (I think). Or to physically check, see the assembly instructions: https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions

Do you not have an menu item for setting/deleting users in the admin console? Other than mobile access, not sure what keymaster buys you. Maybe feature will be added to UD Mobile in the future.

Will do. Pressed a lot of keys today trying to get it to happen again, but no luck. I've written a program to notify me if any key is not in idle for more than 10 secs. So if it happens again, I should be able to find it in the logs.

I have two that are at S0 from migration and one at S2 that I (re)included after migration. I don't use the ones that are at S0 that much (so I didn't notice), but just tested and they do seem to report manual changes correctly (small test sample). The one at S2 needs a query to pick up the manual change in status. Not sure if it is S0/2 related or pre/post migration inclusion. I thought there were some security options when I included the one lock. I may take another look at that.