sjenkins

Thanks, now I know that is needed for zooz (and maybe others). I did that with a few of my z-waves and it helped with a few. Good to know its not a UD/isy issue.

At first all my servers showed green with nodes. I had to stop each of them and start or restart. Did it with the log tab selected for each node & you can be sure it started. That got all my servers going again. They only came up with this manual intervention and not a eisy or pg3x reboot.

Haven’t done the 5.5.4 update but last night did the *.20 update for pg3x and even though my servers showed green with nodes I had to stop each of them and start or restart. Do it with the log tab selected for each node & you can be sure it started. That got all my servers going again. They only came up with this manual intervention and not a eisy reboot.

I am getting these same nodes (I have about 7 of these sensors). Having the same where the Leak Detected Alarm does not turn off. I am using the main node which does come on/off for my programs right now.

I have been finding the battery devices have needed a few interviews to complete. It's as if the device goes back asleep. I have found by either hitting buttons on the device or activating it (moisture, motion) that sometimes keeps the interview going. mostly through just another interview seems to eventually get it all done. also in one case I went onto something else and the data/nodes showed up later. just with battery. dong this I have got all of my z-wave working with all nodes. Now I am really looking forward to being able to do OTA updates for my z-wave. I am in an OSX / Linux house so need this to get my devices up to date.

You will need to do a sync, replace with interview on those nodes. they will then show up (out of whatever folder they were in) as ZY devices. I have had good luck with the GE stuff doing that. after that you will need to goto any programs and scenes which they were in and touch them up.

same here ; just did a packages update & pg3x restart. still on 3.1.18 with 3.1.20 update available.

So I am now complete with my transition from Poly / zooz stick to Eisy / matter. Although I am mostly Insteon I do have about 20 YoLink and 20 Z-wave. The transition to Eisy was flawless and the transition to matter board was a solid OK for me. As @Chris Jahn mentions above the z-waves fell into a few buckets. 1. A very few units moved from ZW to ZY automagically I think two. 2. Most powered units with one sync replace with interview came with the correct nodes 3. battery units have required multiple sync replace with interviews to get all the nodes. usually requiring button pushes on the unit to wake up (multiple pushes). finding they will goto sleep during the interview sometimes 4. my GE switch / motion sensor works with the switch but no motion updates through the motion nodes. Finally all my node servers (about 12) all came over with minimal work except for a couple which required some updates by their author. currently only the Sonos node server (the free one) is running but not coming up with nodes. Hope this helps others!

my logs are simpler..... 2023-01-17 21:47:15,574 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2023-01-17 21:47:15,574 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2023-01-17 21:47:15,745 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-01-17 21:47:15,745 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-01-17 21:47:20,747 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-01-17 21:47:20,748 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

Works like a charm for my needs. Mostly the 30min open reminder and a delayed turning on of garage lights to supplement the garage opener lights.

Sorry for delay was travelling for mlk weekend. No not using wi-fi. All my old polisy setup is working on eisy minus a couple z-wave holdouts. All other ns’ are good except this one.

@johnmsch I am sorry I didn't see the want to keep the 994 going. I also have an "old faithful" 994 which is not doing anything but being kept up to date for that friend or smaller use. I now also have an "extra" Polisy too which I will use as a development device I think. I did have to move on to move up as they say. Anyway, integration of the YoLink devices is through the very excellent node server written by @Panda88. Set-up is simple & it has been rock solid. The yo-link and app are still used ; the app for device maintenance and I use the history functions a lot for my temp/hum devices. The YoLink hub is critical as all communications goes through it. The negative is the dependance on devices which are dependant to external servers. There is debate on how much now and some hope (promises?) from yo-link that the api will not require calls to momma to operate at some point (thoughts on local api to hub I think). I am normally a tinfoil hat guy and want everything local but have strayed a bit with these devices because of the rock solid nature of their chosen protocol. The LoRa protocol gives such good distances it works well for sensors inside fridges or leak sensors on floors. I even home-made a few LoRa devices but the YoLink were so easy to use I haven't completed the project. I have about 20 or so YoLink devices temp, leak, and water-valve are all really nice. Used two switches to make a three-way at a friends vacation home who had the leak, water-valve already (no UD there). The switches are not as high quality as Insteon so do not recommend, but I used the direct linking feature and wanted to try them out. That is the other thing the direct linking feature I do use to switch my water valve with really critical leak sensors which gets by my tin-foil hat issue. So bottom line you NEED a Polisy/eisy to use this node server. I will argue you will enjoy the other features of the new hardware and node server eco system. I also do understand looking at your 994 and feeling like you are betraying a loyal friend. (I keep mine powered on and updated; it makes me feel better.). I do also wanted to integrate all into your Insteon system, I have tried the Z-wave sensors and am not a fan so far (the matter board is a real improvement & my two z-wave switches which I bought in the dark times are working much better now.) Anyway, I have experimented a bunch and still think Insteon makes the best switch. I am though very happy with the YoLink integration with specific devices. I also use the node servers for a Sonos, MyQ (garage door), OpenSprinkler, Plex, weather, virtual, ping, timedata, location....

@johnmsch, curious what you think you will gain with the insteon over the yolink? I have both plus some z-wave sensors ; all of them work but I actually am liking yolink (don't bother with their switches, but their water valve & temp/humidity are all good). They have excellent range and give better feedback than the z-link & much like the insteon. I integrate them with my Polisy & now Eisy quite well ; same programs for all three really. just interested in your thoughts / concerns.

have been using this ns from the beginning. recently moved from Polisy to eisy mine does not seem to be finding my Sonos on the eisy. the Sonos is uptodate and used regularly. just interesting if anyone has it working or not so I can point to the ns or me. I have restarted ; deleted ; re-installed ; rebooted. all the 'regular' stuff.

I have been using the sync replace with interview a lot to get my migration to work. Thanks @vbphilfor passing on the motion fix coming. I have a GE switch/sensor with that issue.

Zen31 rgbw just needed the sync replace & interview ZSE44 temp humidity sensor required a removal from the network and reinstall. Bit of a hassle to redo programs. so far the powered units are working better than the battery units. next is the moisture sensors which I have a weird mix of Insteon, YoLink, and zwave zooz and zwave smart things. more to come.

@garybixler can't tell if you tried this, but with my zen77 I did a sync with replace & interview. That helped quite a bit but ymmv.

@joembzJosef, Certainly understand the frustration and the rant ; we all need to vent sometimes. I guess I look at the diy home automation a bit different. We are using a beta product with the matter board (it's in the name) and therefore we are taking on a contract to help develop it beyond beta. Part of us getting a product early is that we are taking on some responsibility to work it out. I was "easily impressed" as I got my system back with my 30 or so z-waves in a state I could work with. btw: : I have about 60 Insteons, 30-zwave, & 20 YoLink, as well as home-made esp8266/32s going. I KNOW this will not work out of the box; part of the fun is the ride IF your partner is working with you. UD is a really good partner. I have taken this ride with others (Eufy I'm looking at you) and have not had fun. So, I know I look at this different but I do think UD is a good partner and deserves encouragement, and good data from us as we take this product from Beta to full production. Stephen

Looks like it. I think as long as people have a list of things to try we can get everyone through this. No doubt by deleting I reset something ; maybe didn't need to change slots. Thanks again for your updates. Today I have been into my z-wave migration so it was good to have a base system which was working as before.

Just spent the morning with my Zen77 switches. I only have two which I bought during the Insteon scare & have hated them. Post migration I am able to use them in scenes and use their scene or fast-up/down features just like Insteon. They are not as fast as I am using them as responders or controllers in programs but they are now useable. The range on the eisy is a tonne better than the old zooz usb. Now moving onto my other z-wave devices - mostly moisture & temperature. I have one motion sensor in a box. Already documented my one issue with the GE switch/motion device which it looks like others have the same issue.

Great job @Chris Jahn and @Michel Kohanim ! The migration went flawlessly! (had moved from my Polisy to Eisy a while ago, now moved from the zooz to the usb "matter" device. I am now "cleaning up" my 30 or so devices. At first blush they mostly showed up in one of two categories. Either "normal" or "disabled". My first one I started to play with because its in the same room as my eisy and its a wall switch which is in high use. Its a GE ZW 500 series with switch and motion sensor. I needed to enable it and then did a z-wave replace. A few of the garbage nodes went away and it replaced with good switch, motion, scene responder, switch all, basic assoc. My only issue is the motion node does not update even after the replace. .....more info to come, but thanks to the whole team!! btw: : LOVED the hint to tail the log file & have been enjoying the x-ray feature. Those are real informative.

@Javi so I deleted the node server &. installed it in another slot. All 34 nodes came back. Solved. Thanks again!

@Javi I did do that the first time (had to do it with all my ns coming over). I just did it again. Also have done both a restart of pg3x and then a restart of whole eisy. Same error with the issue. I don't have much in the way of programming for this ns so I am ok to delete and install in a different spot or anything else to "play" with it. Let me know ; I'll leave it stopped for now.

updated to new version and restarted pg3x, similar error (might be different line number) OpenSprinkler_1-9-2023_34256-PM.zip

Most of my node servers came across from my POLISY to the EISY except for two ; one of them being OpenSprinkler. In the logs it seems to be having a sslv3 alert handshake failure. Logs attached. Also the restore from backup did not bring back the configuration on this node server and two others. Most did. OpenSprinkler_1-9-2023_104107-AM.zip