hart2hart

I use the Bond hub and Bond BS to control a 15 year old inductive fan’s on/off and speed. Bond directly links with Alexa if that’s of interest.

Look at post above yours.

Upgraded. Deleted Java cache and downloaded fresh copy of start.jnlp to stop Not Found message.

Make me an offer. Don’t want this to end up In pile of unused electronics. SOLD

I’m seeing it a few times per day recently.

Upgraded Packages.

@Michel Kohanim I upgraded to latest version on eISY a few days ago snd all is working well. Should I perform another update or simply wait for next update?

What version of pg3 did you upgrade from? If older than a couple ago, you need to reinstall all node servers per instructions.

I was able to locate the FW version I had at failure and installed it to keep number of change at minimum but I feel both would work.

Upgraded from 3.2.2.

If deemed failed microSD card, the replacement instructions in wiki link: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card

Could this mean the SD card has gone bad and you should replace it before doing the restore?

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!