TJF1960

Last night the api for Emporia Vue went down, came back up this morning. It seems I was not the only one, there were some reports on their forum. I waited a couple of hours after it was back up but the Vue plugin did not seem to connect back up to the emporia server, at least none of the values were ever updated in IoX. Once I restarted the plug in all the values repopulated in IoX and it has seemed to run and control emporia switch plugs just fine. I went to look at the logs but they never populated in PGx. I do have rolling logs from PGx but not sure what I am looking for. PGx f/w 3.2.16 Vue 1.0.26 IoX 5.7.1 If you would like to look at the logs, please let me know where to send them. Thanks! Tim

Same here! Thank you!!!

If the motion sensors are Insteon, you may be experiencing the all on/ all off command that Insteon has since gotten rid of in new devices. There are many posts about it on this forum. Here is a link to UDI mention: INSTEON Random All On Events - Universal Devices, Inc. Wiki (universal-devices.com)

This suggestion is a little late but might come in handy in the future. This was from @Chris Jahn from a few days ago,

@bpwwer and all, Great news! I just updated to IoX 5.6.4, after restarting eIsy all of the Vue node status values populated Without having to restart Vue node server. Thank you all very much! -Tim

Hi @bpwwer, makes sense. Question, Nightly query and or pressing the query button in the node page in AC must act differently, it must not clear the values like the query at startup does? Also, I wonder why pressing the query or even when the nightly query runs those blank fields never populate? I have gone days without restarting the NS after a hardware reboot and the blank fields stay blank until the NS is rebooted. Thank you for all your help in tracking this down. -TIm

Hi @bpwwer, I only have time to run once right now, all fields for all vue node are populated after hardware reboot with query turned off. I want to run it a couple of times to be sure but this is the first time all fields have been populated after hardware reboot. Before hitting restart on vue node server: <nodeInfo> <node flag="128" nodeDefId="outlet"> <address>n013_187658</address> <name>WR Bench Charger</name> <family instance="13">10</family> <parent type="3">2249</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n013_187658</pnode> </node> <properties> <property id="CPW" value="0" formatted="0 kW" uom="30" name=""/> <property id="GV1" value="0" formatted="0 kWh" uom="33" name=""/> <property id="GV2" value="0" formatted="0 kWh" uom="33" name=""/> <property id="GV3" value="2528" formatted="0.2528 kWh" uom="33" prec="4" name=""/> <property id="ST" value="0" formatted="Off" uom="25" name=""/> </properties> </nodeInfo> after hitting restart on NS: <nodeInfo> <node flag="128" nodeDefId="outlet"> <address>n013_187658</address> <name>WR Bench Charger</name> <family instance="13">10</family> <parent type="3">2249</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n013_187658</pnode> </node> <properties> <property id="CPW" value="0" formatted="0 kW" uom="30" name=""/> <property id="GV1" value="0" formatted="0 kWh" uom="33" name=""/> <property id="GV2" value="0" formatted="0 kWh" uom="33" name=""/> <property id="GV3" value="2528" formatted="0.2528 kWh" uom="33" prec="4" name=""/> <property id="ST" value="0" formatted="Off" uom="25" name=""/> </properties> </nodeInfo> Edit: I was able to run this test one more time last night with the same results. With query box in AC unchecked all node fields populate as they should. When the query box is checked some fields are missing. You guys are on to something for sure. Thanks! Tim

@bpwwer, only those two fields in AC were populated, the rest were blank.

@bpwwer, Thanks Bob, interesting results below. Here is the capture after hardware reboot using "eisy.local": <nodeInfo> <node flag="128" nodeDefId="outlet"> <address>n013_187658</address> <name>WR Bench Charger</name> <family instance="13">10</family> <parent type="3">2249</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n013_187658</pnode> </node> <properties> <property id="CPW" value="653" formatted="0.0653 kW" uom="30" prec="4" name=""/> <property id="GV1" value="117" formatted="0.0117 kWh" uom="33" prec="4" name=""/> </properties> </nodeInfo> This is after Vue NS restarting: <nodeInfo> <node flag="128" nodeDefId="outlet"> <address>n013_187658</address> <name>WR Bench Charger</name> <family instance="13">10</family> <parent type="3">2249</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n013_187658</pnode> </node> <properties> <property id="CPW" value="656" formatted="0.0656 kW" uom="30" prec="4" name=""/> <property id="GV1" value="273" formatted="0.0273 kWh" uom="33" prec="4" name=""/> <property id="GV2" value="668" formatted="0.0668 kWh" uom="33" prec="4" name=""/> <property id="GV3" value="2261" formatted="0.2261 kWh" uom="33" prec="4" name=""/> <property id="ST" value="1" formatted="On" uom="25" name=""/> </properties> </nodeInfo>

Hi @bpwwer, I installed 1.0.25, after reboot of eisy I am sorry to say I did not see a change. Query did not help either. What is the recommending method of query at reboot, checking the reboot at start up box or unchecking the box and having a program run a system query 5 or so minutes after reboot? I am reaching for straws here. It must be something on my end here, a program or setting or something. I looked at the error log but didn't see anything out of the ordinary. I have attached it though. Not sure what to try next. A_E.v5.6.2__Sat 2023.07.08 04.52.29 AM.isy

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