GTench

I tried both the update button on the Yolink node server page and the install button on the node sever store page. Neither results in an update to 0.8.97. This is the first time I tried to do an update under PGx 3.1.27. I did do an update under previous PGx 3.1.25 or possibly 3.1.26 that worked o.k.

I am on PGx 3.1.27 and IOX 5.6.0 and yolink 0.8.90. Tried updating to 0.8.97 using the update button in yolink node server but system stays an 0.8.90. Doing a yolink restart still results in staying on 0.8.90. I think this process worked under the previous PGx version

Yes, it looks to me like the phone app is the main source (and that makes sense to me too) but the name change is just not being picked up by the nodes unless adding a new (or missing) node. Now that I realize how this is working, I don't mind deleting the node and restarting the node server to have the new name picked up; so, don't worry about changing anything for me. Changing names is something that is quite easy to do this way and is something that would only happen very infrequently for me. If I want to use a node name different than in the app, I could just change it in the AC (overriding the PG3) and I have done this with other node servers. In this case though, I want the app name and the AC name to be the same for consistency and since the AC gets its names from the nodes, I wanted the app and node names to match Yolink is working great for me. I really appreciate all the work that you have put into it Gary

Did some more testing. Basically, if the device name is first changed in the cell phone app, the changed name shows up in the configuration parameter list but not in the nodes list after a restart of the node server. However, if I delete the node in the nodes list first and then do a restart of the node server, the changed name shows up in the nodes list when the deleted node is automatically readded. Looks to me like the "nodes" do not see the name change as a "change" but it does seem to recognize a missing node as a change then readds it with the correct name. Not sure if there is a bug here or that's just the way it works but if so it seems inconsistent

Just an update. I changed the name of one of my speaker hubs in the cell phone app as a test. I restarted the Yolink node server and I see that my updated speaker hub name shows up in the configuration parameters list but the old speaker hub name is still in the nodes list. I have not tried a delete and reinstall as that is a bit of work. Just wondering if you think that would work or is there a fix at your end

Just added a number of leak sensors. I gave them unique names which show up correctly in the PG3x configuration listing but their node name in the PG3x node listing just shows them as "Leak sensor". They then each just show up as "Leak Sensor" in the AC; so, I assume the name comes from the PG3x nodes. My other devices such as speaker hubs have the same name in the PG3x configuration and node listings and also match what is in the app on the cell phone. Is there something unique about leak sensors?

Just curious but when I go to the node server store it shows the current version as 0.8.88 but my installation sys the I have 0.8.89 installed

Strange... Just got a notification that there is a new version available 0.8.88. When I look at the version that is currently installed it says that it is 0.8.89. Node server seems to be working fine though.

I thought maybe PG3x 3.1.24 corrected the node server reinstall problem but I guess not. A delete and reinstall did work

I am running the latest versions of PGx and IoX on an easy with a Zmatter USB plugin I have a Dome water leak sensor In the AC I have 4 node entries for the leak sensor The Wake Up node shows Is Awake, Keep, Wake interval at the top of the AC. There are drop downs for setting these values but when I try to set them the Wake Interval never shows a value. It is always blank. Is this normal? Also, the first node has Water Alarm, Battery Level at the top of the AC screen but the only time I get a value there is when I physically wake up the sensor then do a query in the AC. Just wondering how to get this field to automatically update so that I can be notified of a low battery level. thanks, Gary

I am on 3.1.24 which I believe is the latest version

I am not able to upgrade from 0.7.4 to 0.8.88. I am on IOX 5.5.9 and PG3x 3.1.24 on eisy. I tried reinstalling to the same slot but that did not work. I also have the same problem upgrading Weatherflow from 3.0.26 to 3.0.29. Gary

Forget it. Looks like it just took some time. Works now

Just got back from a months holiday and thought I would upgrade my eisy from 5.5.4 to 5.5.9 and got this message. I tried power cycling the eisy twice but got the same result. Any suggests on what to do would be appreciated. thanks, Gary

thanks... no hurry on my part

OK thanks. I will be away for a few days starting tomorrow; so, I might try that when I get back. Everything except the node server updating is working very well. I don't want things disrupted while I am away (WAF considerations). In the mean time I also submitted a ticket

OK Here is the log fileYoLink_2-8-2023_113941-AM.zipYoLink_2-8-2023_113941-AM.zipYoLink_2-8-2023_113941-AM.zip when I do a restart. Same result. If I reinstall on another slot do I have to reenter my custom parameters? I think you are right though about something being stuck. I had the same problem just now updating one of my other node servers

Just tried upgrading to 0.8.20 but the same thing happened as before when I tried updating to 0.7.5 If I do a restart I see Current Version: 0.8.20 [Production] but after a few seconds it switches back to Current Version: 0.7.4 [Production] . I tried stop then start with the same result. I also did a reinstall with the same result.

OK thanks. Not a problem as 0.7.4 is working great for me

OK here it is pg3_1-26-2023_13746-PM.zip

Thanks. I just dis another restart with the same results. I have attached the log file YoLink_1-26-2023_110727-AM.zip

I'm having a problem trying to install the latest version of YoLink on Polyglot 3.1.21 with eisy IoX 5.4.5. If I do a restart I see Current Version: 0.7.5 [Production] but after a few seconds it switches back to Current Version: 0.7.4 [Production] . I tried stop then start with the same result. I also did a reinstall with the same result. Not sure if I am running the 0.7.5 version or not? Gary

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