bigDvette

@bpwwerhave you seen anyone else with this problem. Trying to decide if I need to report it somewhere else.

Not sure if this just started with 3.1.21 or if it is even a node server issue but suspect it is. my occupancy node server just disappears. I have to go to portal and go to occupancy Node Server configuration and click configure Node Server/. Then I have to restart pg3x on eisy and then it works for a while. its cold here and it keeps setting my thermostats back based on occupancy and pissing off my wife

yes, that is what I was trying to say. Since I had trial licenses installed (when I did it unless they changed it), it complained I had trial licenses when I did that and didn't transfer them.

yes

after seems to be teh correct procedure. If you install trial licenses it complains and doesn't move the license. Personal experience here. However, given all the Node Server issues until 3.1.17, I wanted to make sure node servers were working so I ended up having Michael move my licenses.

Mine works fine. My only issue was 2 aerotec repeaters. It would pair them but not create any nodes.

I have the same experience. No nodes created. Something about "not a multifunction device".

That point was actually in the migration wiki. I have found you have to do this basically any time you restore a backup.

yeah, something is definitely off with caching credentials. I have had this happen multiple times. Many times just unsing another browser will work. An I can't auto find isy anymore, have to add it manually in launcher.

I know it may sound dumb, but click logout in upper right and log back in. Also, if it doesn't prompt you to lockin to portal when you do that, then reboot your computer. I've gotten stuck in that loop. I've also sometime only been able to fix that by doing an SSH reboot of the eisy. what does it look like under teh menu when you click on iox configuration?

2 - Well this is what I did. At the time all the node servers would not come up until 3.1.17. So I set them up as test licenses. Now you can do a backup and restore which didn't work when I was working on this. I also wanted to keep my Polisy up until I knew everything would work. 5 - When you restore the Polisy backup, the node servers get installed in ISY AC. The IP address on them was the IP address of the Polisy. I also has the UUID in there, so I had to manually change them. I don't think purchasing doesn't anything different, but 3.1.17 gave an backup restore option and it uses the internal IP. I did, Michael moved them for me. I tried to migrate them from portal but it said I already had licenses in the slot.

I backed up my polisy (normal backup, there is no zwave backup). I restored on the eisy and then was able to plug in the zooz dongle and use zwave no problem. I have a procedure I followed and wrote up here,

Insteon was seamless. After 3.1.17 of PG3 nodserver was released, that became stable. While I did not backup and restore as the instructions there indicated if you had multiple ISYs in the polisy you were managing node servers for, there was not a way to select which one was being restored, it was pretty straightforward, I have have another post where I listed the order of my steps. As for zwave, to use my zooz stick I just plugged it in after the restore of the ISY backup to the Eisy. My last piece of puzzle is to migrated the zwave nodes to zmatter and it hasn't been obvious to me which combinations are supported on which platforms.

Sorry I am confused and this is why I am asking. That instructions is from Dec 29th. On Monday you replied to someone else's post where you indicated it was correct that you can't migrate from the zooz dongle., I'm willing to roll the dice a lot, but was just looking to make sure I am not spinning my wheels. Correct. This has been covered a few times on here and from Michel. Its still being worked on.

Does it say that? first sentence says. "in this build we focused primarily on migration either from a Z-Wave network using our original implementation on Polisy/Eisy, or from an ISY-994 backup (containing a 500 Series Z-Wave backup)." Would like to hear from someone that has tried OR someone that is building the migration that can say Yes/No or Not-Yet/Never.

I migrated everything form the polisy to the eisy (node servers, insteon, homeasisstant (what a PITA) / homekit integration) and plugged in my zooz stick an everything is working. Can't seem to find a clear answer. is there a migration at all from zooz 700 to zmatter? If yes above, can that be done on the eisy running 5.5.2? Thanks,

3.1.17 update fixed the issue

After an update today of the PG3 to version 3.1.17, I was able to get all my node servers configured and running. What I did was as follows. 1) I started clean with Eisy. I never got WIFI setup to work, but didn't need it. 2) I then got all my node servers setup in the same slots as the the Polisy I was migrating from. I made sure all the nodes were in the admin console and validated they had the same node_ids. The only one I couldn't get the match on was the occupancy sensor UUID to use with locative, but the ISY node was the same ID. Make note of the User ID, base URL and Host Name fields in the node server configuration in AC. They follow a format, just a bunch of pasting in step 5. This included setting up occupancy sensor in ISY portal on the slot I used it in previously. 3) After all that was working I ensured that I did not have my PLM attached (I migrated my polisy to a USB PLM before I started any of this, but I also got my serial PLM working with the adapter cables). I then unchecked the Insteon and zWave options in the AC Config tab. 4) I backed up my polisy at this point and restored it to EIsy. 5) After it came back up, I went in to each node server from menu at top and changed the User ID, Base URL and Hostname to the ones saved from step 2. 6). I rebooted IOX and made sure node servers were populating. 7). Shutdown eisy and installed existing zooz stick and started Eisy. 8 ). After it came back, I enabled zWave in AC config tab. Then did a restart IoX. 9). Validated the zwave devices were controllable. 10). Shutdown eisy and attached the PLM and started Eisy. 11). After it came back up I enabled Insteon in AC config tab. Then did a restart IoX. 12). Let it run and do its thing until devices had been updated. I have a large Insteon network but it didn't take nearly as long as the Polisy takes. 13). Did some tests, then went over to the portal. Went to my ISY I was migrating from in portal and Did the maintenance -> migrate to option and migrated all the options to my Eisy. Now I just need to have the purchased node server licenses moved and I should be good.

I can't discover any nodes. When I click discover nodes it looks like it is trying to use the wifi adapter which is not configured on my eisy as I am using wired. My basic debugging seems to indicate this. It also looks like MQTT is trying to use the 172 address space. I don't see where to turn off wifi and regardless shouldn't It default to wired when both configured? Cheers, let me know if you want to remote debug on the eisy. 2023-01-03 16:04:21,560 Thread-9 udi_interface INFO Controller:_discover: harmony_discover: starting... 2023-01-03 16:04:21,561 Thread-9 udi_interface DEBUG discovery:get_network_interface: gateway: default=('172.26.18.1', 'wifibox0') 2023-01-03 16:04:21,561 Thread-9 udi_interface DEBUG discovery:get_network_interface: gateway->ifad: wifibox0=[{'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'}] 2023-01-03 16:04:21,561 Thread-9 udi_interface INFO discovery:get_network_bcast: get_network_bcast: Returning 172.26.18.255 2023-01-03 16:04:21,561 Thread-9 udi_interface DEBUG discovery:discover: Pinging network 172.26.18.255 port 61991 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:21,598 MQTT udi_interface.interface INFO interface:_message: Successfully set harmonyctrl :: GV7 to 2 UOM 25 2023-01-03 16:04:22,624 Thread-9 udi_interface DEBUG discovery:discover: Pinging network 172.26.18.255 port 61991 2023-01-03 16:04:22,624 Thread-9 udi_interface DEBUG discovery:discover: Pinging network 172.26.18.255 port 61991 2023-01-03 16:04:22,624 Thread-9 udi_interface DEBUG discovery:discover: Pinging network 172.26.18.255 port 61991 2023-01-03 16:04:22,624 Thread-9 udi_interface DEBUG discovery:discover: Pinging network 172.26.18.255 port 61991 HarmonyHub_1-3-2023_40724-PM.zip

Cool. Hoping to get all the Node Server stuff working while in the 30 day trail before migrating my licenses and moving Insteon. I only have like 6 z wave dimmers I use for fans and 2 repeaters so will just do those over.

Yeah, can’t ever get them started. @bpwweris this something you are working on and potentially fixed in next release. I saw your update earlier on items in next release but haven’t seen an update to try against.

No, not trying to move. I've decided I would get all the node servers working and installed and then do my restore and re-do my zwave devices. So for now I'm using trial license to do this. I'm hoping to get this all working in the 30 day window, then move the licenses. So far I can't get Harmony or MyQ to work.

what are the pins for the rj45 to db9 adapter? I have the original cable that came with serial PLM, but it didn't work. I have a bunch of db9 to rj45 kits to make adapters. IS this correct? RJ45 PIN1 --> RS232 TXRJ45 PIN8 --> RS232 RXRJ45 PIN7 --> GND

I have been able to convolutedly get all the free node servers I use installed. However, none of the licensed node servers will install. As an example, I am attempting to install the harmony node server. All the paid node servers fail with the same message of error: createNS: ReferenceError: status is not defined at checkLicense. I know you've said several times you can only test with your unlicensed node servers @bpwwer. Has anyone else been able to install paid node servers? 12/30/2022, 19:47:27 [pg3] info: checkLicense:: Updaing HarmonyHub subscription expiration to 2023-01-30T02:50:43.000Z 12/30/2022, 19:47:27 [pg3] error: createNS: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:433:5) 12/30/2022, 19:47:30 [pg3] info: [00:21:b9:02:60:43_3] Retrieved customparams 12/30/2022, 19:47:30 [pg3] info: [00:21:b9:02:60:43_3] Retrieved oauth 12/30/2022, 19:47:37 [pg3] info: [00:21:b9:02:60:43_3] Retrieved customparams 12/30/2022, 19:47:37 [pg3] info: [00:21:b9:02:60:43_3] Retrieved oauth 12/30/2022, 19:47:37 [pg3] info: [00:21:b9:02:60:43_3] Retrieved customparams 12/30/2022, 19:47:47 [pg3] info: Starting log stream for pg3frontend_ks9ZQ :: /var/polyglot/pg3/logs/pg3-current.log

I can't get my first 2 node servers to start. When I install one that has a license, I get what is in the picture below about undefined. When I install one that is free, i get an installed successfully message. I can't either of them to actually connect. I have this in the log for the MyQ (which is paid and throws the error in the picture). 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] :: Creating Node Server 'MyQ' 12/30/2022, 09:40:18 [pg3] info: Adding customparams entries to custom database 12/30/2022, 09:40:18 [pg3] info: Adding nsdata, oauth entries to custom database 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] Set nsdata 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] Set oauth 12/30/2022, 09:40:18 [pg3] info: checkLicense:: Updaing MyQ subscription expiration to 2023-01-30T02:49:51.000Z 12/30/2022, 09:40:18 [pg3] error: createNS: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:433:5) 12/30/2022, 09:40:35 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customparams 12/30/2022, 09:40:35 [pg3] info: [00:21:b9:02:60:43_2] Retrieved oauth 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Set customparams 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Set customtypeddata 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customparams 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customtypeddata 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved oauth 12/30/2022, 09:41:01 [pg3] info: [MyQ(2)]: Restarting Node Server 12/30/2022, 09:41:01 [pg3] warn: [MyQ(2)]: Was not running. Starting... 12/30/2022, 09:41:03 [pg3] info: Starting log stream for pg3frontend_9baEU :: /var/polyglot/pg3/logs/pg3-current.log 12/30/2022, 09:41:03 [pg3] info: Starting log stream for pg3frontend_9baEU :: /var/polyglot/pg3/logs/pg3-current.log 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20) 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20) 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20)