Got production caught up to dynamic JSON profiles as well as fixing a Ratgo depreciated label issue.

Let me know of any feedback. I have seen in other plugins (Tahoma) that with the jump to the JSON profile migrated plugins from the old PG3 to the new Eisy-ui needed an Eisy reboot to remove a profile error. When installed straight from Eisy-ui it seemed to be fine. YMMV.

3.2.3 \

DONE VirtualGarage Ratgdo: ESPHome REST URLs use entity display names (e.g. /light/Light) instead of deprecated object_id paths; SSE state events accept new id format ahead of ESPHome 2026.7

3.2.2 \

DONE dynamic JSON profiles (Phase 1): updateJsonProfile instead of static profile/ zip for eisy-ui sync
; requires IoX 6.0.6+, PG3x 3.4.5+, udi_interface 3.4.5+; install.sh renames profile/ to profile.static on EISY; profile/ XML remains source for data/base_profile.json; bump profile_version in server.json when JSON base changes

3.2.1 \

DONE fix config overwrite: stop re-injecting example devfile and sample devices on every parameter loal
DONE remove example customParams from server.json so Polyglot updates do not reset user configuration
DONE clear "Waiting on valid configuration" notice when discovery fails

I did the upgrade and it seems there is a problem according to the log file but it seems to me like things are still working. I don't know if this is because I'm still using the old config where I list them within PG3 instead of uploading a file to eisy.

2026-10-17 20:25:05.756 Thread-761 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:08.757 Thread-762 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:11.758 Thread-763 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:14.545 Command udi_interface INFO VirtualSwitch:DOF_cmd: 1:switch 1, {'address': '1', 'cmd': 'DOF', 'query': {}}

2026-10-17 20:25:14.545 Command udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot.

2026-10-17 20:25:14.597 MQTT udi_interface.interface INFO interface:_message: Successfully set 1 :: ST to 0 UOM 25

2026-10-17 20:25:14.638 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata

2026-10-17 20:25:14.761 Thread-765 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:17.764 Thread-766 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:20.764 Thread-767 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:22.770 Command udi_interface INFO VirtualSwitch:DON_cmd: 1:switch 1, {'address': '1', 'cmd': 'DON', 'query': {}}

2026-10-17 20:25:22.770 Command udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot.

2026-10-17 20:25:22.816 MQTT udi_interface.interface INFO interface:_message: Successfully set 1 :: ST to 1 UOM 25

2026-10-17 20:25:22.858 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata

2026-10-17 20:25:23.794 Thread-769 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:26.767 Thread-770 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

2026-10-17 20:25:29.772 Thread-771 (poll) udi_interface ERROR Controller:poll: Node not ready yet, exiting

I also tried migrating the plugin to eisy and the temperature nodes did not work so I migrated back to PG3

There was a devfile on my configuration page and things seemed to clear up after deleting that. I worry about trying the migration again, maybe I will give it a try when I have more time. Thanks for all you do sjenkins!

@tazman ,

Wondering if the devfile was the example one which is pushed on a new install. Did it have example in the name? Just to be clear when you say migration are you talking upgrading to the latest version or migration to eisy-ui from pg3?

@sjenkins yes it was the example one with the example in the names. I ended up doing the migration from PG3 to eisy-ui and had to rename everything but I guess that is the price of being the early adopters since it sounds like they fixed the naming resets in a later release.

Interesting, I migrated really early and had all my 20 or so plugins came along. Didn’t have the issue where the example got reactivated either. Wonder if you were one of the lucky ones who did it in a version with some issues; I certainly read about them & wondered why mine went so slick.

It’s not as if I did anything beyond hitting the button. So you know I have been running this plugin in the new environment since then so all should be ok once over.