GTench

Just wanted to say thanks for the above. I appreciate the clarification. I just migrated from Polisy/Zmatter to eisy/Zmater doing as you suggested above and also by following the instructions in the wiki. I don't believe the wiki mentioned your last step of restoring the Z-Wave network (maybe I missed it) but I did need to do that. Everything is working well on eisy. My system has a large number of Insteon devices, a dozen Z-wave devices and a few node servers. I did not do the Zooz to Zmatter migration on Polisy. I just removed and readded them when I installed Zmatter on the Polisy. I have a serial PLM; so, I used the original cable that came with the PLM and attached it to a serial to USB adapter that I purchased from Amazon - worked fine

Perfect! Thank You very much. I did notice that before in the portal just forgot about it.

I just had the same problem but power cycling the eisy solved it for me

I just moved from Polisy/Zmatter to eisy/Zmatter and migrated my node servers there. I am running the latest 5.5.3 and 3.1.18. Node servers say they are connected but if I look at purchased node servers I see 0 purchased. If I do a restart, I get a license error but they do show up as connected. Just wondering how to fix this? Gary

Just another vote for yolink. I have 9 yolink devices all working very well on Polisy. They were very easy to set up (much less trouble for me than adding my Zwave devices). My primary use is using the yolink speakers scattered throughout the house to announce when someone is on the front porch delivering packages. The speakers are triggered by IoP blue iris nodes connected to cameras pointing at the front porch. I set this up because I found that delivery personnel rarely if ever ring the doorbell when they leave packages. Gary

I had a similar experience adding a multisensor 7. The event log showed it as being added but no nodes showed up. I tried sync with interview but it crashed IOP with java errors and automatically restarted but still no nodes. i then shut down IOP and reopened it from the finder. It started but showed busy with the progress bar. When that finished, the nodes showed up Gary

Thank you. Worked for me too

I am on 3.0.25 and I keep seeing a message to upgrade to 3.0.26. I have tried restarting the server, stopping the server and restarting and rebooting polisy but I am still on 3.0.25. Not sure what is happening Gary

OK thanks, I see it under 5.5.2 but did not see it under 5.5.0. The syc problem was under 5.5.0; so, the UV was not there when I did the move to 5.5.2. I did try to Synchronize New with interview under 5.5.2 but the UV did not show up

Just upgraded from 5.5.0 to 5.5.2. All went well I have polisy with Zmatter board installed. I manually added my 12 Zwave devices to Zmatter when using 5.5.0; so, I did not do a migration. Under 5.5.2 I still do not see nodes for my 2 Zwave repeaters Humidity is not shown for the mulisensor 6 but I see this has been identified as a bug. Also I noticed that after doing a Zwave Synchronize New with interview that the UV item for the multisensor 6 vanished leaving just 3 items (temp, lum, bat) Gary

Thanks, I went ahead and reset Zmatter and factory reset each of my 10 Zwave devices then included each of them. All but 2 of the devices repaired quite quickly with Zmatter - quite a bit faster than with the Zooz stick. I struggled with 2 of them - an Aeon Labs MultiSensor 6 and EVC200 Z-Wave Automatic Valve which took multiple resets and inclusions to pair them - a major pain. I had the same issues pairing them previously with the Zooz stick. The Aeon Labs MultiSensor 6, although paired, is not showing humidity in Iox but it did previously with the Zooz stick. I will likely try to exclude and repair to see if that clears the issue. I now see all zwave devices as nodes except the 2 repeaters but the event log shows that the repeaters were paired successfully. I also have a large number of insteon devices and a few Yolink devices which transferred over to 5.5.0 with no issues at all. Just glad I only had a few Zwave devices to manually include.

Yes, I noticed the same thing with the Zooz stick when I added a few Zwave devices a few years ago. Once there is a fix, can I reset the counter with a factory reset to the Zmatter? I only have a half dozen or so Zwave devices but I would like to have their counters match what they were under the Zooz dongle if possible

OK thanks very much for the quick response. I see by the event log that I should have 6 Zwave entries as a result of my retrying to add the repeater but I don't see any of them in the node tree. I will wait for a fix

This is what I see in the event log Tue 12/27/2022 03:31:00 PM : ---- Start Adding Devices - S2 Standard --- Tue 12/27/2022 03:31:00 PM : [ZWAVE-INCL-S2STD] Start Include S2 Standard highpower=true Tue 12/27/2022 03:31:00 PM : [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0x802beb468 Tue 12/27/2022 03:31:00 PM : Z-Wave Listening for Z-Wave devices to add to the network Tue 12/27/2022 03:31:05 PM : Z-Wave Z-Wave device detected, start adding to network Tue 12/27/2022 03:31:06 PM : Z-Wave Z-Wave device detected, retrieving info Tue 12/27/2022 03:31:06 PM : Z-Wave Z-Wave device added Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x20 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x26 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x33 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x59 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x5A Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x5E Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x70 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x72 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x73 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x7A Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x85 Tue 12/27/2022 03:31:06 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=0x86 Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:06 PM : Z-Wave Idle Tue 12/27/2022 03:31:08 PM : [Device 5] Waiting on interview complete (400 ticks remaining) Tue 12/27/2022 03:31:12 PM : [Device 5] All interviews are done Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Queue sync device 5 Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Start sync device 5 Tue 12/27/2022 03:31:12 PM : [ZWAVE-SYNC 5] Device mismatch, Removing all existing ISY files/objects for Z-Wave device Tue 12/27/2022 03:31:12 PM : [SYNC-DEVICE 5.0] Set commands will now be accepted by the controller Tue 12/27/2022 03:31:12 PM : [ZWAVE-SYNC 5] Not multichannel Tue 12/27/2022 03:31:12 PM : ZWAVE-WORKQ-34 Finished sync device 5

I upgraded to 5.5.0 and have the ZMATTER board in my Polisy. I pushed the zwave to matter button, restarted Iox and as expected my Zwave nodes were gone. I then tried to add an anotec zwave repeater. Iox dialogue box says it is interviewing then disappears. The repeater blinks green which should I believe indicate that it is paired but I do not see its node in Iox. I have tried resetting the repeater and retrying pairing without success. Any suggestions? thanks, Gary

yes... I ordered and received the ZMATTER board from them a week or 2 ago. I installed it into my Polisy a few days ago Gary

Thanks... I used TOP. HTOP was not installed. Looks like I also see the high cpu usage. I am only using 3 message annoucement yolink devices currently

Does HTOP need to be installed? If so just wondering how. I would like to check my usage as well. thanks, Gary

thanks... I submitted a ticket. I am still getting a large number of entries in the error log file

OK thanks. I am using IOP with latest firmware

I seem to get a large number of entries like this in the error log file. Just wondered what they are and if I should be concerned thanks, Gary Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(6323)->36895 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(59241)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:41:57 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(20890)->3689 Sun 2022/11/20 01:41:57 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(40095)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(36825)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:48 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(16020)->3689 Sun 2022/11/20 01:42:48 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c61:3fdf:ff7f:0:(10036)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log Sun 2022/11/20 01:42:56 PM 0 -170001 [Auth:-10103] ::1c51:1fdf:ff7f:0:(42489)->3689 Sun 2022/11/20 01:42:56 PM 0 -10108 Check log

Thanks for info the guys. My fix, although not pretty, works for now at least until replacements become available.

I had reason the other day to make use of a remote link2 that had not been used for 4 or so years. I plugged it in to recharge but the red LED would not go off so it was not taking a charge. I found this strange because it had just been sitting there unused. I then went to a spare remote link2 that was in its original box (also at least 4 or more years old) and discovered that it too would not take a charge. I looked online for a replacement battery but could not find one with the same dimensions as required to fit in the remote link2 enclosure so I just MacGyvered something together using a similar capacity battery that I could find as I do not believe new remote links are available yet. I released the 4 tabs on the remote link2, cut the battery leads close to the battery and pushed them through a small hole that I drilled in the back of the case. I stuck a new 300 mahr 3.7V battery to the back of the case since it would not fit inside the enclosure and soldered its leads to the ones poking through the case hole and now it works fine. Just wondering if it is common for these batteries to fail if they are unused for a lengthy time. I have other remote link2s that are at least as old as the failed ones and they are working fine but they are in regular use and are recharged periodically. Gary

oh I did change the ethernet adapter on the computer that I use to access IOP but network/internet works fine through it

OK, I got it going by adding it in the finder by entering http://192.168.2.117:8080. Not sure why the finder could not find it by itself though?