mbking

I tried for the first time to update a node server from UD Mobile and I received the following error message: The node server disconnected and did not update. Using the PG3 web interface, I restarted the node server and it restarted with the old version. A re-install was successful. I have version 3.2.1 of PG3, so there may be something new there that caused the problem.

Installed the upgrade last night, but eisy became unresponsive to a reboot. I've seen this before from time to time. I was also not able to log into PG3. I tried to shutdown eisy with 6 presses of the power button, but it would not shutdown. I removed power and restarted it. It booted normally and I was then able to get into PG3. I have 6 node servers. The re-install step worked fine on the first 4 (Notification, ELK, Ambient Weather, and HueEmulator), but it stopped on the RainMachine node server with it in a Disconnected state. Also, the version shown for RainMachine was the upgraded PG3 version, 3.2.1. I had to do a manual re-install on it and the last node server, VenstarCT. After that, everything seems to be working fine. So, the upgrade was a little bumpy, but it's complete and working.

@Dr. Q, Apologies on the link. I believe you got the same one. The corrected link is: https://www.amazon.com/AV-Access-Extender-Extension-Operating/dp/B0C5R4DVRF/ref=sr_1_4?crid=285K6WROJD9WO&keywords=av%2Baccess%2Busb%2Bextender%2Bover%2Bcat5e%2F6%2F6a%2F7%2B196ft%2F60m&qid=1691285946&sprefix=%2Caps%2C215&sr=8-4&th=1 The reason I like this particular one is because the power supply plugs into the transmitter and then supplies power over the ethernet cable to the receiver with the antenna and PLM USB connections. Since that transmitter will be located in the equipment room with eisy, it will remain powered along with eisy. Again, looks like you got the same one. I verified this link and it takes me to the one I bought. Let me know how it goes.

@mapeter, so far so good. i haven't experienced any issues with the extenders.

I updated from 2.0.8 to 2.0.11 with no issues. However, I expected to see new nodes and there are non in the AC. The old nodes are there and updating with the new version of the software. The log looks normal. @bpwwer, should I be seeing new nodes? I only have two sensors; an outdoor sensor and an indoor sensor with multiple attributes in both. The node addresses didn't change.

Updated per the instructions above and everything updated as expected. The UDX restart rebooted eisy and PG3 is now at 3.1.37.

Update completed as advertised. Update Packages, reboot in AC, re-installed all NS's, and then restarted NS's. Note: NS configuration is retained as part of the re-installation. Thanks for the smooth update.

@Michel Kohanim, I updated using the commands above. Once the systems had restarted, I was not able to get into PG3x via the Admin Console or UD Mobile. I restarted PG3x using the following command: sudo service pg3 onerestart (sudo service pg3 restart didn't work, onerestart was recommended) Now I can login to PG3 and all node servers appear to be running normally and the UI indicates 3.1.35 is running. At this point, I have no issues to report other than the additional command to restart pg3. I will continue to exercise the system and post any issues I find. Thanks

@PapaBear, I was a loyal user of MobiLinc for a long time. I used MobiLinc Pro and then switched to MobiLinc X when it was released. MobiLinc X was a nice interface, but lacked some of the features of the MobiLinc Pro. I assumed those would be added over time, but that didn't happen. Unless it's been added recently, MobiLinc X lacked support for node servers and that's an important feature for me. UD Mobile is highly customizable and new features are being added on a regular basis. Support is superb. UD Mobile also automatically negotiates between a local WiFI connection and the Portal (small fee for this) for remote use. The switchover is quick and smooth. There are just features in UD Mobile that I can't get with MobiLInc X. Had to switch.

@MMotion, I have another option you might want to consider. I'm currently testing the following product which allows me to mount my eisy in my equipment room and remote mount my ZMatter assembly and PLM in a location best suited for the best RF connections. That location is more than the allowed 16 ft for USB 2.0 and already has an available ethernet port: https://www.amazon.com/dp/B0BRPQQ77T?psc=1&ref=ppx_yo2ov_dt_b_product_details So far, the testing has been successful, but I need to do more testing to convince myself there is no degradation in performance with this setup. This unit uses a single ethernet cable to extend 4 USB connections up to a claimed distance of 196 ft from the source computer. This particular unit is unique in that it supplies power through the ethernet cable from the transmitter to the receiver to power those end devices. Most of these units inject power at the receiver. I wanted something that would remained powered with eisy via my equipment room UPS. With this setup, the ZMatter dongle and PLM are plugged into a single receiver being feed by a single USB connection on the eisy side via the ethernet cable. Let me know if you'd like more details.

Update on this Project To recap, I want to eventually mount eisy in my cabinet room where an existing UPS can provide uninterrupted power and it will be easier to power cycle when necessary. I want to keep the PLM and ZMatter antennas in their current location because they are on top of the kitchen cabinets with a good RF connection there. I have ethernet between the 2 locations. So, I purchased the following USB Over Ethernet equipment: https://www.amazon.com/dp/B0BRPQQ77T?psc=1&ref=ppx_yo2ov_dt_b_product_details One of the USB ports on eisy plugs into the transmitter, the transmitter connects to the receiver via ethernet cable, and the ZMatter dongle and the PLM plug into the receiver via their USB cables. I chose this unit because unlike other brands, the transmitter, which will be located with eisy, provides power to the system including devices attached to the receiver. Since the transmitter will be on UPS power, I'll be able to maintain power to ZMatter during a power outage. Only the PLM will need to restart after power is restored. Since eisy will continue to run with power off, I'll need to write some recovery programs to insure all equipment is in-sync with easy's current state. I plan to use ELK's AC status attribute to determine when AC is lost and restored. This is in a test setup right now with all equipment above the kitchen cabinets since I need to finish installation of my Unifi system before the needed ethernet connection is available, but I plan to run it like this to watch for any unusual behavior and test some power lost scenarios. So far so good.

@PeteEaston, no cause was determined for the connect notifications and for the last 2 days, I haven’t seen any of the notifications. So it’s still a mystery. Fortunately, it wasn’t causing any operational issues. If I see them again, I’ll post and I’ll review the logs.

@Goose66, this is a great explanation. The default poll intervals, for the most part, work fine. Sometimes, though, I use UD Mobile to change the cool/heat set point and a more immediate feedback would be nice. Rather than shorten the short poll for this one use case, is it possible to request a one time status update after changing a thermostat setting via the node server?

@PeteEaston, I think we may have the same issue. I'm working with the PG3x developer in the following thread: I have PG3 notices turned on in UD Mobile and 3 times a day (at 7:01am, 3:01pm, and 11:01pm) I get a notice for each node server that they are connected. The events are exactly 8 hrs apart. Don't have an answer yet, but if you're having the same issue as I am, please come join our discussion. It will help for Bob to know that I'm not the only one having the issue. As a note, I have the same software versions, only I'm running on eisy.

I've gone through the systems I have online and can't find anything that might disrupt the network, but I do have a UDM-Pro connected to my existing network at the moment to prepare it to be my main router and it monitors its connection to the network. I'm not showing any loss of network connection during the time of the MQTT issues. @bpwwer, I'm updating this response. I did find something that happens every 8 hours; PG3 looks for changes in the node servers. The reconnect notices come right after that checking for updates. Yesterday I had reconnect notices at 7:01, 15:01, and 23:01. In two of those events, the following error occured in that checking for changes event: 5/29/2023, 23:00:56 [pg3] info: Query store database https://pg3betastore.isy.io/v1/list 5/29/2023, 23:00:56 [pg3] error: MQTTC: Error: write ECONNRESET 5/29/2023, 23:00:56 [pg3] error: MQTT received error: Error: write ECONNRESET Interesting note: I received the connect notifications at 7:01, but not at 15:01 as I expected, so it doesn't happen every time. I'm going to PM you the log package from yesterday so you see the full picture.

@bpwwer, This is an excerpt from the PG3 log file at the time the notifications came through this morning: 5/29/2023, 07:00:59 [pg3] info: Verifying node servers are installed on IoX correctly 5/29/2023, 07:00:59 [pg3] info: IoX entry for ELK::2 OK 5/29/2023, 07:00:59 [pg3] info: IoX entry for AmbientWeather::3 OK 5/29/2023, 07:00:59 [pg3] info: IoX entry for HueEmulator::4 OK 5/29/2023, 07:00:59 [pg3] info: IoX entry for RainMachine::5 OK 5/29/2023, 07:00:59 [pg3] info: IoX entry for VenstarCT::6 OK 5/29/2023, 07:01:01 [pg3] info: MQTT attempting reconnection to broker... 5/29/2023, 07:01:01 [pg3] info: Pushing notification {"title":"AmbientWeather (3): Connected","body":"from PG3"} to UD Mobile 5/29/2023, 07:01:02 [pg3] info: Pushing notification {"title":"VenstarCT (6): Connected","body":"from PG3"} to UD Mobile 5/29/2023, 07:01:02 [pg3] info: Pushing notification {"title":"RainMachine (5): Connected","body":"from PG3"} to UD Mobile 5/29/2023, 07:01:02 [pg3] info: Pushing notification {"title":"ELK (2): Connected","body":"from PG3"} to UD Mobile 5/29/2023, 07:01:02 [pg3] info: Pushing notification {"title":"HueEmulator (4): Connected","body":"from PG3"} to UD Mobile At 3:01pm this afternoon, exactly 8 hours later, I got all 5 notifications again. I'll be watching tonight at 11:01pm to see if it happens at an 8 hour interval again . I definitely want to keep the notifications on. This one isn't a show stopper, but it would be nice to get it resolved. I can PM you the whole log package if you like. Let me know. Update: At 11:01pm, I got the same 5 notifications and the log messages are the as above. The difference was the location of the MQTT reconnection message which at 11:01pm, came before Verifying node servers message. There does appear to be a pattern. Mark

@Geddy, currently, I'm only running eisy. This morning, I received connect notifications from all 5 node servers. They came in all at once and all have the same time stamp. I looked at the log for 2 of the node servers and found nothing abnormal around the time of the notifications. This same thing happened yesterday at exactly the same time, 7:01 am. This makes me think this is a bug in the notification logic and not an issue with the node servers. But I'm no expert on the details, so I was going to send @bpwwer the log packages for 2 of the node servers to see if they shed any light on this issue. Should I send these packages to Bob directly or submit a ticket with the packages attached? Not sure of the best process here.

Since moving to PG3x both in Polisy and eisy, I get random reconnect notices from all my node servers at the same time. I looked at one of the node server logs and there were no indications that anything happened at that time to cause the reconnect notice. Happens maybe once a day. Interval seems random. Since there is nothing in the log, maybe this is a bug in the logic that triggers the notices?

Thanks @bpwwer, that’s what I finally did and all went well except I had to remember some of the special settings needed for some. Strain on the brain, but I remembered correctly. My biggest concern was having to redo some of my favorites in UD Mobile if any node server references changed on the re-install. Fortunately, that didn’t happen. I was just thinking about what someone would do if they were replacing a failed eisy and trying to restore from their PG3x backup. With the current process, I think they’ll have to do what I did. Since moving to PG3x, I have seen some random connect notices in UD Mobile for all my node servers at once. I’ll post the details in a separate topic. Thanks for getting back with me.

PG3 on my Polisy Pro had already been migrated to PG3x, so there was nothing to migrate. I don’t think my scenario is covered by the instructions. I’m hoping Bob can shed some light on that.

@bpwwer, I enabled PG3x on Polisy before creating a backup to use with my new eisy, so I did not create a migration backup, I created a standard backup file. I've moved licenses and restored the PG3x backup from Polisy to eisy. I've rebooted PG3x on eisy and node servers are displayed, but unmanaged at the moment. What should my next steps be to get the node servers working again? I checked the node server configurations in eisy IoX and they are still configured for Polisy IoX. Should I change the IP and UUID to match eisy? Never done that, so I'd like to hear what you think before proceeding. Update: I ultimately re-installed the node servers and everything is normal now. But I'm curious why a PG3x backup from Polisy didn't completely restore on a new Eisy with PG3x. Thanks.

I’m already using ZMatter via the ZMatter board for Polisy. As I went through the Eisy instructions, I kept overthinking the term “migration”. For me, everything is already migrated. So with that in mind, I can follow the instructions and ignore the migration path. Before I jumped in, I just wanted to make sure I had a clear and proper path for making this move from Polisy to Eisy. You guys helped clarify some of the details. I’ll give it a try a little later in the day. Thanks again.

@DennisC and @Javi, Thanks for the replies. It always helps to have another perspective. To clarify some of your questions, I'm not moving the Zmatter board from the Polisy Pro. I'm starting with a new one on eisy. I plan to use the Polisy Pro as a development machine; maybe try a node server or two. One last question; once I restore my IoX backup, do I need to go to the Z-Wave menu and restore the Z-Wave backup or does that automatically happen when I restore the IoX backup? Again, thanks to both of you for your input.

I'm making the move from a Polisy Pro to eisy and I've looked through the applicable wiki documents, but I want to make sure I have the steps correct before making the move. I have a Polisy Pro with a USB PLM and the ZMatter internal board and I have enabled PG3x and migrated my node servers to PG3x. My Z-Wave network is using the ZMatter board. I'm moving to eisy with the Zmatter dongle using the PLM from the Polisy Pro. Software is up-to-date and Polisy and eisy have a Portal license. Pulling together all the information from several wiki docs, my upgrade process is: Backup Polisy Z-Wave (I assume but can't confirm that this becomes part of the IoX backup, true?) Backup Polisy IoX Backup Polisy PG3x Deselect Insteon and Z-Wave support Power down Polisy and unplug PLM Plug PLM into eisy Restore Polisy IoX to eisy IoX Restore Polisy Z-Wave backup to eisy ZMatter (not sure if this is already done when I restore the Iox backup??) Restore Polisy PG3x to eisy PG3x Migrate node server licenses to eisy PG3x Select Insteon and Z-Wave support Reboot eisy Restart node servers Migrate Favorites in UD Mobile from Polisy to eisy @Chris Jahn, @bpwwer, @Javi, does this process look solid for my upgrade scenario? Missing anything?

Thanks, @Michel Kohanim. I'm afraid I left out a few of the details. If I do this, I'm waiting until I move to eisy. I have a USB PLM, so I'd be connecting that to eisy as well as the USB Zmatter board. With eisy mounted in my equipment room, I was planning to use something like the OREI USB-EX165-K USB over Ethernet to connect the remote mounted PLM and USB ZMatter board to eisy over an existing ethernet cable. The OREI comes with 2 modules that are connected via Cat 5 or Cat 6 cable. One module connects to the host(eisy) via USB and the other device module has 2 USB ports that I can connect to the PLM and ZMatter assembly. The device module has a power supply that can power the devices. This system is not supposed to require any drivers and is compatible with all OS's (yet to be seen if that's true). Before I move to eisy, I could try this out with my existing Polisy system to see if the USB PLM will work. My current Polisy location is above the kitchen cabinets which is great for RF coverage, but if I have to power cycle Polisy, I have to grab a ladder to get on top of the counter to reach it. The older I get, the less popular that sounds :). That's why I'm looking at this to see if it's possible. It's not a big deal if it doesn't work. I can run a cable with a switch through the cabinets to power cycle Polisy or eisy if need be.