Just recently my Elk plugin has stopped updating the nodes on my Eisy. The controller node seems fine in admin console but no nodes show up in the plugin in PG3. I've restarted the plugin, restarted admin console but nothing.

its telling me area 1 does not exist

2026-01-06 21:56:45.846 Command udi_interface.interface ERROR interface:_handleInput: parseInput: node address area1 does not exist. {'address': 'area_1', 'cmd': 'GV11', 'query': {'Beep.uom2': '0', 'Clear.uom25': '1', 'Content.uom145': '+0.0KW 25.4 Sprd'}}

Rest error
2026-01-06 21:56:03.316 Thread-9 (handler_start) udi_interface INFO Controller:start_rest_server: ELK Controller: REST Server not running for light_method=NONE

and
2026-01-06 21:59:41.906 Thread-1 (send_thread) udi_interface.interface ERROR interface:_send: MQTT Send Error: Object of type ElkRPStatus is not JSON serializable

I've included a log package

Any help would be appreciated

ELK_1-6-2026_95842_PM.zip

I just opened a ticket on mine. I noticed that Elk in Home Assistant nodes were showing unknown. After some investigation, like you I find it connected. I can log into my Elk and it's fine as well. No weird IP changes or anything. Then I notice in Home Assistant, there are two entities (sensors) with the same name but one is under Elkm1 and one is under House Area. The one under House Area no longer works. Seems like something changed in the Eisy update and shifted. However, even after reloading the module in Home Assistant the problem persists.
Interested to see how this shakes out. I can reselect all the entities but I don't like the double names in Home Assistant and would rather see it resolved.
I hope to hear soon.

So we all know, what firmware version of eisy are you running and what version of pg3 are you on?