I migrated my Bond Bridge plugin today into eisyui and at first test nothing appears to be responsive when I go to the node panel and manually toggle lights or turn on the fan. When I look at the log file it appears to be using the correct device IDs... example here for a few different trys for different devices...

2026-10-23 16:12:31.202 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address 2ffd4fe1 does not exist. {'address': '2ffd4fe1', 'cmd': 'DOF', 'query': {}}

2026-10-23 16:12:31.242 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address 355343b0 does not exist. {'address': '355343b0', 'cmd': 'DOF', 'query': {}}

2026-10-23 16:16:45.517 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address 2278430c does not exist. {'address': '2278430c', 'cmd': 'DON', 'query': {}}

2026-10-23 16:16:45.559 Command udi_interface.interface ERROR interface:_handleInput: parseInput: node address 2278430c does not exist. {'address': '2278430c', 'cmd': 'SETSPEED', 'query': {'FAN_SPEED.uom56': '1'}}

The node addresses shown in this log grab are correct for the device I was trying to enable or toggle and the Token for the Bridge itself is verified as correct in the configuration tab. The Bond Bridge does show as connecting in eisyui and I have tried to restart the plugin with still always getting the same error on the node addresses not existing.

Has anyone migrated the Bond Bridge from PG3x to eisyui and had verified that things are working?

Edited October 26Oct 26 by ISY4Me

I could not find any reason for all Bond Bridge subnodes not working, I assume there is some tweaks necessary. When the Bond Bridge node was pushed back from eisyui to PG3x, everything responded as I would expect.

This post should have been posted into the eisyui sub-forum... sorry about that.

A new day, so I thought I would try again. I migrated the Bond Bridge from PG3x to EISY-ui and that seemed to go OK. When I look at the Bond Bridge in EISY-ui, I see everything and all the sub-nodes, but now today when I click on any of the sub-nodes in the EISY-ui Nodes list, I do not see the buttons in the right panel and instead I see a red "internal server error". I tried rebooting and that did not change and I then power cycled the box and again this performance did not change.

@Goose66 Are you aware of any issues with the Bond Bridge after migrating to the EISY-ui?

When I reversed the process and put the Bond Bridge back in PG3, everything returned to normal and I can go to the EISY-ui Nodes list (as shown above) and the buttons and lists for all the submodes appear in the right panel and I can change them as desired and all is good.

I suspect some help is needed from the EISY-ui team since everything is OK when the plugin is left in PG3.

I approached the Bond Bridge migration again this evening. Tried to do this as cleanly as possible, purged the cache on Safari and started eisy-ui in a web window. the migration showed no issues and produced the following view in the nodes list...

The nodes and sub-nodes all showed as before and the sub-node buttons appear in the right panel. However, when clicking on the buttons to turn the test light on/off they did not work... nor did any of the others for the Bond Bridge.

The other strange thing I noticed in rebooting after installing the Bond Bridge plugin in EISY-ui, it apparently caused the OpenWeatherMap and SUN plug-in to go into a Disconnected state when viewed in the Node List. However, when you examined the plug-ins in the EISY PLUGINs list in EISY-ui they all showed connected. When the plug-ins were restarted in the EISY Plugins view all the plugins in the Nodes view changed to connected. I am not sure what caused this, but I will watch out for this pattern on future reboots and if it occurs again I will submit a Ticket.

So, after getting all the plugins to show a "connected" status in the EISY-ui Nodes view, I still did not see any change the Bond Bridge sub-nodes (buttons and stuff in the right panel not working) and I was still seeing the comment "node address xxxxxx does not exist" in the log file. I then wondered if I had to re-discover these sub-nodes even thought they had migrated over OK. After I did a "Discover" from the EISY-ui "eisy Plugins" Bond Bridge view, this is what I saw in the Nodes View...

Now the "Status" column was showing the current state of the Bond Bridge sub-nodes. After I saw that change, I tried the buttons for a single sub-node (as shown in the above view) and they worked.

This is progress and I will now leave the system in this state and see if everything continues behaves normally. But it does leave a few questions for the experts.

1) Should running Discover become the default recommendation after a migration from PG3 to EISY-ui?

2) Why am I seeing some of the Plug-Ins (In the Nodes View) drop to a disconnected state after a reboot? Then I have to restart them.