TJF1960

Hi @maxnorth, If I recall, from the Admin Console select the main (on-off) node of the 6-button KPL. Select "Buttons Toggle Mode." Select the first node (main on-off node) and select "Non-Toggle." At the KPL push the on button then the off button. The on LED behind the button will turn on and off as normal. When the press the off button the off LED should remain off now.

I am looking for performance so I will not select mirror. Once the process of converting from emmc to nvme is done, emmc is wiped out and the OS is installed and ran from the new nvme. God forbid something happens down the line and the nvme goes bad, what is the recovery process aside from installing a new ssd? Also, is there a way to clone the newly installed drive to another ssd just for a backup in the even a failure occurs? Finally, is the emmc available for any purpose or is it bypassed completely and not used? Thanks, Tim

I am having the same issue with the installation, "setup_nvme_boot: command not found" I even tried adding .sh to the end of the command " setup_nvme_boot.sh: command not found -Tim

Hi @Panda88, The leak sensor went offline yesterday. I was not able to capture it go offline with debug on. But I turned debug on this morning then queried the device then an hour or so later I pushed the link button on the bottom of the device and it reconnected. I have Attached and pm'ed you the logs, hopefully they will help. I am leaving debug on to catch the next time the leak sensor goes offline. After pressing the link button, the Yolink app should the status as connected. The Yolink plug in in the admin console did update the temp from 79 to 66 degrees, so the temp is working, just not the connection status. Thank you so much! -Tim

@Panda88, Thank you for this plugin! It has been working flawlessly for me. I have been using it for about 3 or 4 months and it is working awesome. I am trying to set up a program to let me know when one of the leak sensors fails. I have 1 out of 10 that fails intermittently. YoLink will send me an email, but I don't check my emails nearly as often as I should so it may be 3 or more days before I realize there is a problem. I noticed In the Yolink phone app, in the details page for the sensor, that they do offer State (Normal or Offline) as well as Battery level, Signal Intensity and Temperature readings. This may be a huge ask, but I was wondering if some or all of those could be implemented? Thanks for your time and contributions to this forum! btw, anyone considering Yolink, I have found that while they are cloud based, the devices are easy to link, and are very quick to respond in both the phone app as well as @Panda88's plugin. Their system is by far one of the best and easiest to set up and deploy that I have seen. -Tim

I moved over all of my message mp3's from a pi4 to eisy. An amp is connected to the eisy which drives small speakers in each room of the house. Reminders such as to put the garbage cans out or there is someone at the front door or the garage door is still open and more important ones such as a water leak detected. I love that with the addition of this plug in, my pi4 that was used for PG2 and Nodelink and audio spokens is almost decommissioned. The plug in is simple to setup and executes quickly and painlessly. Thanks Michel!!! -Tim

Thanks! Did you restart the Vue node server after Emporia was back up and running? Mine started working after restarting the node server.

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