photogeek54

So I updated my programs to use the new ecobee plugin and there are a few things that look strange. I have added 3 new climate types to my ecobee, "wakeup", "hot day" and "retiring". In ecobee I only see one additional climate type it calls "smart1", not sure which of those it is and 2 missing. In one of my programs it is trying to set climate type to "smart3" but the action below for that row calls it "home". I've attached photos.

got production udi_poly_homekit and ecobee to work! remember to restart admin console after configuring and starting each Other than ecobee, will the homekit plugin allow me to access any other apple home devices like apple TV or apple home knowing if I am home or away?

Trying to setup ecobee plugin from the beta store. I upgraded packages to get the latest software like was suggested. The configuration instructions are overwhelming: Install and configure udi-poly-homekit first (PG3 store): pair your Ecobee(s), then enable the hub MQTT transport (mqtt_enable and broker settings in that plugin; see its PROTOCOL.md). MQTT is the preferred transport for new installs and is the default of hk_transport here — point both plugins at the same broker and matching *_hub_slug. WebSocket (ws_host / ws_port and optional ws_token) remains supported as a fallback when MQTT is not available. This nodeserver’s HomeKit mode talks to that hub only; it does not replace it. Missing backend param: the plugin seeds a default once: homekit for a fresh NS (no OAuth, no api_key, no saved Ecobee tokens/PIN in customdata, no extra nodes yet); cloud if Polyglot OAuth is enabled for this NS, api_key is set, customdata has tokenData / pin_code, or the NS already has nodes besides the controller (legacy upgrade). If backend is already stored in PG3, it is never changed by seeding. Ecobee cloud (REST API): Ecobee has cut off UDI / Polyglot Cloud access for this integration. Cloud mode only remains viable if you use your own Ecobee developer application key that you registered before Ecobee stopped honoring requests for the old shared keys, and you configure api_key / PIN flow as documented for local Polyglot. Do not rely on historical OAuth or UDI-provided keys for new setups. can you give a simplified verbose example of what we should enter, especially in the homekit plugin? I do not have a personal API key for ecobee. Thanks

The Ikea Matter thread devices are amazingly low cost so I really want to get them all to work and plan to buy more. $7.99 for a motion sensor, wow. The successful devices are: Kajplats E26 1100 lumen bulb: I added it to Apple Home and then use the sharing code to add it to Amazon Alexa and then used another Apple Home sharing code to add it to UD mobile. I had to start with a factory reset bulb and then worked quickly to add it to the 3 systems. Grillplats mini smart plug: used same technique as above. Unsuccessful devices: Billresa switch: above technique added it to Apple Home and Amazon Alexa but can't add to UD mobile. Just times out. MYGGSPRAY motion sensor: added to Apple Home and Alexa but UD mobile says can’t find thread border router. Tried sharing codes from Apple Home and Alexa. Anyone else have luck with these devices?

The failing solaredge plugin has been removed from the production store. The new updated version (now 1.1.8) has been installed in the production store. If you are using the original Mike King version, you cannot just do an update, you need to delete it in the PG3 dashboard and install this new version which has a different plugin ID. You will also need to re-enter your api_key in the custom configuration parameters using the key "api_key" and value of your actual API key.

Great news. Since the production version is broken I’m surprised no one else has commented. May not be many users ? I’ll let all know when I update this to the production store.

@GQuack I have found and fixed the problem with API keys. Although solaredge claimed their latest API update (March 2026) is backward compatible it looks like they deprecated the /version command used by the plugin to check for a valid API key. I changed this to use the /sites command and also fixed some time functions that no longer worked correctly (with copilot help). Both the production and non-production versions of the plugin are failing. I have uploaded my fixed version (1.1.8) to the non-production store for some testing by others. If it looks stable to others, I will also move it to the production store. Thanks @bpwwer for your help with this.

Several weeks ago my plugin started getting an "API request failed" error. I see this same error with the production plugin and the non-production plugin. I've confirmed that its not just me as GQuack is seeing the same error. I've reached out to solaredge to see if they have changed the API but couldn't get anyone knowledgeable. My installer hasn't been able to get any response either. Are others seeing this issue? Any ideas what might be happening? 2026-04-16 19:46:57.748 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS custom message {'customparamsdoc': '<h2>Configuration</h2>\n\n<p>The SolarEdge node server requires a valid API key to access your site\ninfomation. You can obtain an API key by logging into your SolarEdge\nmonitoring account. From your monitoring dashboard select "Admin" and go to \nthe "Site Access" section. Near the bottom of the page is a section to\nenable API access and get an API key.</p>\n\n<p>Copy the API key to the api_key custom parameter below.</p>\n'} from Polyglot2026-04-16 19:46:57.748 Command udi_interface.interface DEBUG interface:_handleInput: Process custom message customparamsdoc from Polyglot 2026-04-16 19:46:57.751 Thread-2 (handleParameters) udi_interface ERROR solaredge-poly:_api_request: Request failed: Expecting value: line 1 column 1 (char 0) 2026-04-16 19:46:57.751 Thread-2 (handleParameters) udi_interface INFO solaredge-poly:handleParameters: API request failed. Invalid api key? 2026-04-16 19:46:57.792 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2026-04-16 19:46:58.342 MQTT udi_interface.interface INFO interface:_message: Profile installation finished

Mine has started running again. Latest OS and PG3

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

Mine is working again also

just started failing for me too. Hope emporia can fix the problem.

Sucessfully added the tapo P125M smart plug, and a govee LED strip light, thanks. I have a Aqara U200 lock installed in Apple Home but it won't add to UD mobile with QR code or setup code. It recognizes it as a lock but can't add it. Any ideas?

0.5.9 has solved my eisyui/finder issues. A restart of my solaredge plugin also solved its problems

loading start.jnlp from https://www.universal-devices.com/ gives me the same results as Admin Console (Cloud) in finder. I think I need to get back to a working system like I had a few days ago where my plugin still works. How can I do that. Should I enter a ticket for this or keep replying in the forum?