TJF1960

Hi @bpwwer, query did not work on 1.0.24, I will download 1.0.25 tonight but wont be able to test until after work tomorrow. Thank you for your perseverance Bob! -Tim

Hi @bpwwer, I did see your response last night and updated the Vue NS with the new version, thank you. I was not able to reboot the eisy hardware until just now. I am sorry to say that I am seeing the same thing after hardware reboot. Is it possible that the NS is sending the data too early or too fast in the IoX boot up process? Or maybe there is something on my end that is causing it? Is there anything you can think of I should try? Thank you! Tim

Hi @bpwwer, I added updated logs and more info to the ticket. Thanks! Tim

@bpwwer, I was unable to attach any of the zipped logs to your pm so as Geddy suggested, I opened a ticket and was able to upload all logs. Ticket #22024. Thanks! Tim

@Geddy, do you happen to know the upload size limit when sending a PM? The smallest log file is 1.4Mb and it is hanging up, the other I need to upload is 5.5Mb. @bpwwer I have been unable to attach the logs to a PM to you. Suggestions? Thanks! Tim

Where do I send the log package please?

Hello @bpwwer, Running eisy IoX 5.6.3 and PG3x 3.1.37. Vue has been an amazing NS. The only issue I have is when eisy is rebooted, not all data populates in IoX. I have to restart the NS then all data will populate. I have, from AC, tried query but that does not populate the missing data. I have even waited a day or two after eisy reboot but some data is still not populated. Everything works fine before the NS manual restart. The missing data is in the fields of Status of each note, and all of the KWH locations in each node. What logs might be beneficial? Is this a known issue, or maybe just my issue? Is there a way to restart either the NS or pg3x remotely, either by USI mobile or by a program in IoX? Thanks! -Tim

5-Star process. Easy upgrade once again! Running eisy, all is great! Thank You!!! -Tim

Perhaps UDI filled their quota for beta testers already...

Good morning, I tried upgrading this morning and received "Not Found": [admin@eisy ~]$ [admin@eisy ~]$ sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg pkg: https://pkg.isy.io/udx13.staging/All/pg3x-3.1.35.pkg: Not Found Any suggestions would be welcome. Thanks, -Tim

Upgraded without issue on eisy from 5.6.0, love the confirmation popup window at the end of the process! Thank You! -Tim

I noticed that MPG123 audio player is native to eisy. I added some audio files and they play fine when manually started in putty. Is there an easy way to have IoX play the audio files?

I just upgraded from Polisy to eisy this morning. I followed all migration instructions and took my time. I have 50+ insteon and 12 PG3 node servers. Everything migrated perfectly. There was only one minor issue, the Vue nodeserver didn't work, but that was fixed easily with guidance from the Vue forum. All in all it only took a couple of hours this morning! My hat is off and a BIG Thank You to all the behind the scene efforts and fellow ISY'ers who blazed the trail before me. You all did an excellent job and made this so easy! Thank You!!! -Tim

For anyone interested. I had MQTT working on Polisy for a long time. As I remember it required adding a mosquitto config file to change the port. Upgraded this morning to eisy, followed all instructions for migration, once PG3 was migrated to eisy and rebooted MQTT/Sonoff worked perfectly right from the restart. No additional tweaking or any changes to the config needed! Thank you to all involved!!! -Tim

Not to hijack this string, I just upgraded from Polisy to eisy, followed all instructions and found Vue ns had the same problem as the op @thewebgeek . I upgraded the dev packages as @bpwwer suggested and followed @thewebgeeklead and installed sudo pkg install py39-boto3, rebooted and Vue is now working beautifully! Thank you to both of you for forging the path! -Tim

@Javi, how can I download 1.0.30 beta for android please? Thank you!

Thank you, updated and works perfectly again. Once again, you are amazing! Thank you!

Hi @bpwwer, Just updated Polisy (IoX) on Saturday, updated thru the admin console. Everything seemed fine. Got up sunday morning and no programs or scenes which have vue switches in them were controlling the vue switches. Rebooted Vue node server and it worked ok until this morning, same thing. I turned on debug in vue node server. When I got home this evening ISY was not able to control any switches. However I noticed if I manually turn on any of the vue swtiches it updates the admin console with the on/off status as well as measurement. But trying to turn on and off thru the admin console does nothing. Around 5:10pm Pacific is about when I started turning the switch on manually. Tonight, simply rebooting PG3 did not fix it. I had to reboot Polisy. All is well again...Perhaps the problem is with IoX since that was the only thing updated on Saturday and this problem started Sunday morning. I tried to attach the node server log but it is 7.2mb zipped, 94mb unzipped, it wouldn't attach. How or where can I attach such a large file? I have attaced the error log from IoX. *** UPDATE I take it back,Everything that I try to above did not bring back switch functionality through the admin console.It continues to report data and continue to report when the switches manually turned on and off. The admin console reports when the switch is turned on and off via the vue app thru my phone as well. I am open to suggestions please. Vue version v1.0.22 PG3 version v3.1.16 ISY version V5.5.4 ISY Error Log.v5.5.4__Mon 2023.01.23 05.52.56 PM.txt

@Goose66, The file size is 2.6mb, I waited 20 minutes and it still wasn't uploaded, perhaps the forum will not allow attachments that large? Is there somewhere else I can send it to?

@Goose66, You are right, sorry, no MyQ log but I do have PG3 log. If you would like it, where should I send it?

Update: Deleting and re-installing the node service back into the same slot fixed the issue.

Hello @Goose66, after attempting to upgrade MyQ to .21 it shows as disconnected. Further restarting either the MyQ node server or PG3 results in disconnected and it still shows an upgrade is available. No logging after the upgrade. I am on Polisy with PG3 v3.1.16 and IoP on v5.5., currently MyQ reports v3.1.19 If you would like a log file from PG3 please let me know to send please. Any suggestions would be appreciated.

Thank you for the quick confirmation. Order placed. -Tim

Hi @Jimbo.Automates, Was going to order 5 of the new quad water sensors to test. I clicked on your affiliate link but the webpage that opened was the blog/news page for wireless tags. I was expecting the link to take me to the webstore. Can you please confirm please? : https://goo.gl/rXAGk9

@bpwwer, Couple of weeks ago I updated IoP by AC>Configuration>Upgrade Packages. After it was complete IoP reported it updated to v5.4.5 I read this morning PG3 had been upgraded so I performed the same procedure as last time. Waited an hour, rebooted PG3 but it did not update. We used to be able to ssh in and upgrade PG3 but have not done that as I am not sure it would be the right thing to do. I am not sure what to do next and I didn't know what logs you might need. Looking for suggestions for the next step please. Thanks! Tim