JTsao

I did get it fixed - I tried a few different things, but I believe this was the key: SSH in and try: sudo service udx restart

I heard via an open ticket, that there was an update a couple of days ago that might fix the node server problem in PG3x, but I can't find anything verifying this - I updated the eISY via the update button but the revisions of IoX (5.5.5) and PG3x (3.1.22) are still the same - logging in to eISY, I see via pkg info -a that the versions are udx 3.3.6, pg3x 3.1.22_3 and isy 5.5.5_2 - can someone explain how to figure out if there was a minor update and where the release notes are?

This morning I tried to upgrade and my eISY has been indicating in IoX that it is upgrading for hours - how do I stop this and re-run the update?

Are you suggesting that it should not have been possible to migrate to ZMatter and then just switch back to the Zooz controller? That's what I did and all my Z-Wave equipment works - I was thinking that this could be a problem as well... I do have the Silicon Labs software and have updated Zooz ZST10 firmware before and performed backups but I will need to re-read the forums to learn exactly how associations work Does this indicate that the "LR Lts ZW034" device is controlled by "LR2 Lts ZW035"?

This past weekend I performed a migration from Polisy/Zooz to eISY/ZMatter but ended up going back mainly due problems with Node servers not working - I have some Zooz Zen71 and Zen77 switches in one area of the house and had 3 switches grouped together in a scene - I think that ZMatter does some Z-Wave scene setup because now, after going back, I have one switch still controlling 3 lights and I have since redefined the scenes - Is there any way with the Zooz ZST10 dongle to manually erase the scene setup or adjust it?

That's what I thought too, but from my experience this past weekend and from correspondence with Michel via the ticket that I submitted on this issue, I believe that: 1-Node server licenses can go back and forth, but 2-The ISY Portal license is a one-way/one-time transfer I would prefer that UDI allow all licenses to be more fluid in the case where software issues render the eISY unusable (like in my case) due to user requirements

One question about re-trying this sometime in the future - do I need to factory reset both the eISY and ZMatter (not sure how to do this) before trying again? If not, what is the recommended procedure for cleanup prior to trying migration in the future?

Not sure if this is directly related but I noticed something about the Zooz ZSE40 - I recently took my Insteon MDs out of service and have 5 ZSE40's controlling lights in various locations using the scheme where the MDs do not directly control a scene, they just report motion On and Off to IoX: If 'Motion Detectors / LR ZW037-MD' is switched Off And 'Motion Detectors / LR ZW037-MD' is not switched On Then Wait 5 minutes Set 'LR-Coffee Room / LR Ctr Lts' Off The above program works fine to turn off the lights as discussed - the lights stay on as long as someone triggers motion within the MD timeout + 5 minutes If 'Motion Detectors / MBath ZW050-MD' is switched Off Or 'Motion Detectors / MBath ZW050-MD' Status is Off Then Wait 25 minutes Set 'Master Bath / Master Bath Lt' Off But the above also works - I noticed that the above program becomes false when the MD is switched ON and also refreshes the MD timeout - note no AND clause for not switched On Is this normal behavior or unique for the ZSE40?

FWIW I ended up going back to the Polisy for now - overall I would say that this attempt (#2 for me) came really close for a final eISY migration, but a couple of issues are breaking a lot of functionality that I have come to use on a daily basis- so I will shelve the eISY for now and try again later... EDIT: so DennisC is right that you CAN go back to the Polisy/Zooz dongle after attempting the migration - one thing - ISY Portal is a bit unclear to me about this but it appears that I was able to migrate the node server licenses back from the eISY to the Polisy, but not the ISY portal license

I get the same error when I tried to add geofencing back into the eISY

I'm getting HTTP error 400 or 401 when trying to add devices/locations

After migrating to eISY, I tried to migrate back to Polisy, but ISY Portal said I can't send the licenses back - but now, I am showing 0 purchases on eISY, and this, in combination with the "already started" issue is making most of the node servers non-runnable - do I need to open up a ticket? EDIT: I found out that even though the ISY Portal indicated some kind of error message about migration, the node server licenses did migrate back from the eISY to the Polisy, but the ISY Portal license did not

Well, I have migrated to eISY but there are some issues: 1-Several node servers report as disconnected and are experiencing the "already started" issue, where they can't be re-started - these are all configured correctly and some were actually working prior to a reboot, PG3x restart, or power cycle 2-Zooz ZSE40 motion sensors don't work and won't complete an interview 3-I cannot seem to set up the Occupancy node server that was working fine with the Polisy 4-A couple of z-wave devices won't complete an interview, but others of the same type can... 5-Sometimes, I cannot log into the PG3x web page for the eISY - a power cycle is required to get back in if this happens At this point I would recommend staying put to anyone considering moving from Polisy/Zooz to eISY/ZMatter - I am considering the possibility of moving back - does anyone know if it is possible to transfer Node Server licenses back from the eISY to the Polisy?

I am at the point where all node servers should be working, but I am seeing the node server "already started" issue appearing in slots 1 and 2 consistently and other slots randomly with each reboot - I am starting to regret attempting this today...

This is happening to me - I (unfortunately) am trying to migrate from my Polisy to eISY and appear to have random node servers displaying the "already starting" issue, with the node server in slot 1 = DSC Envisalink, always exhibiting this problem (and slot 2 as well)...

OK - to be honest, I didn't completely understand what you meant, but I am trying to digest - "To migrate the node servers, you need to (1) backup PG3 on the Polisy and then (2) use PG3x's migrate from PG3 backup button to migrate the PG3 backup and (3) convert it to PG3x format and (4) change the node server configs to point to PG3x." I'm pretty sure that I did (1) and (2) but can you elaborate on (3) and (4)? EDIT: OK I found what gzahar mentioned and had to change all IP references to the eISY's new IP address in IoX admin panel node servers->Configure - so that's obviously been a problem - should I re-do the migration again to more quickly get everything working?

All - thanks for the replies - I migrated the licenses, I did the "migrate from PG3", and I powered down the Polisy before I started the migration process - so far it appears that I have to re-install node servers in the same slots one at a time, and then re-configure them... I have got Rachio and Weatherbit working now - I was hoping that this would not be necessary, but it isn't terrible - not sure if I'll have to re-edit all of the programs using the node servers, though...

I followed the Wiki instructions very carefully but cannot get any node servers to work - they appear to be in the original slots, but all report as unmanaged with "no details available" - tried multiple reboots and re-starts of PG3x - any suggestions?

I've been kind of dreading performing the migration - Initially I was considering just doing Polisy/2448A7/Zooz to eISY/2448A7/Zooz migration with the hope that I could revert back to the Polisy if there were any issues - but after reading the Wiki, it seems that it may be best to migrate directly to eISY/ZMatter - would anyone agree with this? Is this is one way process such that the ZMatter becomes the new z-wave controller and I would not be able to revert to the Polisy/Zooz?

I deleted an experimental node server that I hadn't started using yet (for the flirc IR) and then the version seemed to correct itself

I re-started PG3 2X and rebooted the Polisy - it still indicates "ISY 5.5.3" using two different browsers, but the IoX on both the Polisy and eISY is clearly 5.5.5... Thinking about this some more, I had been running 5.5.4 for quite some time, so 5.5.3 wasn't even the version that I was previously running - I guess I didn't pay attention to this until now

I updated both Polisy and eISY (not in service yet) and restarted PG3 and PG3x - everything seems OK so far - one thing - the PG3 Node servers page (Polisy) reports ISY version 5.5.3, not 5.5.5

In the program example that I provided, for example, "Watch a Movie" is an activity, not the hub. Your examples above indicated what you can do with the hub itself, which is limited. Hubs have the arrow pointing right. Activities have an arrow pointing left. You need to make sure you can see your activities in IoX, then you can trigger on when they start or end. The hub below is called "Family Room" - devices and activities are child nodes, activities have the arrow pointing left. Devices, and the hub itself point right.

Thanks but that didn't work either - is there a recovery process where I plug my HDMI monitor and USB keyboard/mouse directly into the eISY? Otherwise, I may have to send it back to UDI to get fixed...

NEVER MIND - eISY is now a brick - I tried a factory reset (10 presses) then 5 presses to reboot - had to revert to wired ethernet - it gets an IP address, but refuses ssh connections and does not show up in IoX finder I've tried a couple of factory resets and reboots - what now?