hart2hart

Thank you @Michel Kohanim ! The update made a big improvement in speed of update.

Thanks @bpwwer. I've seen same thing from at least two other NS. I'll submit them with logs.

@markv58 The NS was almost instantaneous with updates to virtual devices. With one of the last PG3x updates or last IOX update the NS has starting being slow or missing updates to the virtual devices from both the AC and UD Mobile. Short log segment below shows the slowness. I’ve reinstalled and restarted 2023-08-21 10:47:14,444 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:47:14,445 Command udi_interface INFO Virtual:listValues: {'switchStatus': 0} 2023-08-21 10:47:19,517 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 0 UOM 25 2023-08-21 10:47:36,730 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:47:36,731 Command udi_interface INFO Virtual:listValues: {'switchStatus': 1} 2023-08-21 10:47:46,900 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 1 UOM 25 2023-08-21 10:47:55,162 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:47:55,163 Command udi_interface INFO Virtual:listValues: {'switchStatus': 0} 2023-08-21 10:47:55,231 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 0 UOM 25 2023-08-21 10:48:01,318 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:48:01,320 Command udi_interface INFO Virtual:listValues: {'switchStatus': 1} 2023-08-21 10:48:01,384 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 1 UOM 25 2023-08-21 10:48:08,745 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:48:08,746 Command udi_interface INFO Virtual:listValues: {'switchStatus': 0} 2023-08-21 10:48:08,810 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 0 UOM 25 2023-08-21 10:48:16,861 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:48:16,862 Command udi_interface INFO Virtual:listValues: {'switchStatus': 1} 2023-08-21 10:48:26,945 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 1 UOM 25 2023-08-21 10:48:40,805 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:48:40,806 Command udi_interface INFO Virtual:listValues: {'switchStatus': 0} 2023-08-21 10:48:40,871 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 0 UOM 25 2023-08-21 10:48:43,691 Command udi_interface INFO Virtual:storeValues: Storing Values 2023-08-21 10:48:43,692 Command udi_interface INFO Virtual:listValues: {'switchStatus': 1} 2023-08-21 10:48:53,805 MQTT udi_interface.interface INFO interface:_message: Successfully set 02 :: ST to 1 UOM 25

Thank you @firstone for the Nodeserver and the fix. I just ran Update and eISYIR versioning is now in sync.

I first installed the Free version, and it was still hung at 3.6.9 so I installed the Standard version and it says 3.6.11 is installed but it did not ask me to pay. Happy to pay if you can tell me how.

Thanks. I tagged developer in first entry so we’ll see if they respond.

Thanks for confirming. Do you know if data will be corrected so it shows correctly as installed is 1.0.0?

I’m sorry Bob. It is on the purchases page but it’s on a beta version line and not the production version (correctly showing Re-Install). Do you know if there been thought s towards removing the beta version if production version has been purchased and installed? Got same thing on eISYIR. I’d be fine with an option to remove it from list or nothing as it not a big deal.

@firstoneand @gzahar I installed PGx 3.2.1 yesterday and 3.2.2 today. the NS shows 1.0.0 as the latest version and I show having 1.0.00 installed. "Update" is listed as the action (I'm thinking the difference between 1.0.00 and 1.0.0) but taking that action does not result in it being upgraded to 1.0.0 as it stays at 1.0.00 so "Update" remains as the action.

@Jimbo.AutomatesI installed PGx 3.2.1 yesterday and 3.2.2 today. Notification NS shows 3.6.10 as the latest version and I have 3.6.9 installed so "Update" is listed as the action but taking that action does not result in it being upgraded to 3.6.10 as it stays at 3.6.9 so "Update" remains as the action.

@bpwwerI installed PG3x 3.2.2 and it lists "Install" as the action option for the nodeserver which has been running great. I installed again and it still lists option as "Install" -- not a big deal to me but wanted to let you know.

Updated from 3.2.1 and all good so far. I'll be posting about into a couple node servers topics that version number or install issues.

Installed 3.2.1 and reinstalled 14 node servers. It all ran fine and initial results are good. Confirmed that purchases not showing upgrades on all NS. Thanks for the continued improvements!

Installed and running. Thanks!

I’ve got one I’ll sell. PM if interested.

Few things for my Schlage deadbolts in the interview process with eISY and zmater unit. o I took 2 locks out of the doors and hung them on a camera tripod 3 inches away from Zwave antenna. You could get the same results if you could get Polisy near lock. o I woke them up by opening them with a one of the user codes at the After this process, I may have had to do a reset on locks to get it to properly extend and and retract the bolt. After the reset I had to reenter user codes but the other programming and links stayed.

You delete it from Eisy. Under nodeservers.

Good! If I recall correctly (@MrBill or @Geddy can you confirm) the ISY will show devices in Safe Mode. Given that no devices are showing, could this be the ISY that was never used? Maybe you could power it off and pull SD card from the other ISY and then restart to see what you get by following same steps.

Ethernet to USB is not the right adapter. As @MrBill points out it would require a serial to usb adapter and if memory serves me correctly the ISY does not support its use. I believe the goal with the ISY994 is get it running enough to run the proper upgrade and migration steps to obtain a proper backup that can be used to migrate to the eISY. The next step is to move further into the AC. With IoX, when you click on the ISY link do you get launch from cloud?

Are you plugging the ISY994 into same Ethernet cable that the eISY (or is eISY on wireless wifi) was plugged into from your original posting? Is the PLM plugged into the ISY994 and the PLM plugged into an outlet? So we are on same page., can you snap a photo of the ISY994 showing all the wires it is connected to when all plugged in?

Good. Sounds like you may have at least one working ISY994. Can you locate the other ISY994 to see if it powers up? If the other one does not power up, it may be the one you’ve been using most recently and hence, it’s SD card would have the most recent data. Keep in mind if it does not power up that we need to try the power supply from the ISY that did appear to get power. Let me know how that goes.

Thanks for your service to us and our country. With other here, I’d love to assist you sorting migration to the great eISY if possible. If it is ok with you I’d like to take one step at a time in the process? As others said, it would be so much easier if we could get the ISY 994 back or at least the data on SD card. You said your ISY994 is dead. So to determine if it might be the power supply, does dead include as a symptom that none of the ISY994’s blue LED lights come on?

Thanks. Based on description, it felt like it was pure polling. I do have a Ring camera (mapped to the Ring NS) in the garage that I could use to detect motion and then Force Update just before lock entry so I’ll keep that in mind as future unfolds.

Thanks for the explanation. Is there anything we as users of the NS could do to make it easier? Pure spitballing here but could we “see” the GUID Name string in the NS log and then create a custom parameter to map it to an integer “user number”?

Thanks again, @Goose66 . I would like to see the user name or number available when the lock is unlocked and/or locked. I would use it to disarm the security system.