photogeek54

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?

I must be missing something very basic. I was thinking based on some previous forum posts that maybe browsing in Edge to 10.10.1.171/desc would get me to the admin console, looks like that's not the case so I'm trying to use finder. The iox finder now comes up with only 2 options: clicking http://10.10.1.171:8080 in finder lets me choose Admin Console (LAN) or Admin Console (Cloud). Admin console (LAN) locks up and I have to close the finder. Admin Console (Cloud) works with iox username and password so that's what I use but My solaredge plugin in the non production store is now having issues. clicking http://10.10.1.171/desc in finder does nothing How do I start admin console with the portal user name and password

I installed 0.5.8 but still get the same XML file error, see image. Update: if I use http://10.10.1.171:8080 without the /desc I can get in to the AC, but I have to login with my previous AC userid and password not those of the portal.

Great , I can see the process running now. I cleared edge browser cache and browsed to : https://10.10.1.171/desc and http://10.10.1.171/desc but I get an xml error

I'm just bringing up eisy-ui for the first time and can't get it to show up in Iox finder or start it. I've read this entire topic's posts and believe the update packages and reboot I did yesterday should install and enable it right? I've cleared java and browser caches. running sudo service eisyui restart gives eisyui does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable adding https://10.10.1.171:443/desc to iox finder says "not found" Should I try installing the eisy-ui package manually via ssh? If so what is the current package name and how can I see the version I am currently running? Do I need to manually install the latest iox? If so what is the latest package name and how do I find the exact version I am currently running? AC's help only shows 5.9.1 and not the latest version number. Thanks

I successfully added a Tapo S505 matter WiFi wall switch using the pairing code from Apple Home (where it was already working) and entering that into UD mobile on an android tablet. Hooray. I tried the same with a Tapo P125M WiFi smart plug and admin console said "Matter listening for matter devices to add to network (ZWAVE-CTL-EVENT Basic set from 40.0 unmapped (ignored))" but hung and never found any. Also tried Govee Matter strip lights and Govee matter permanent outdoor LED lights. Same result Waiting to try my Aqara U200 smart lock. Hoping to hear from UD as to when to try again.

UPDATE: I setup a program to send SMS to tmobile every 5 minutes. My Eisy sent the messages every 5 minutes for about 20 times (missing 2 of the messages towards the end) then became highly irregular. So yes it works somewhat but is definitely rate limited.

Seeing some progress in support for simple matter device I upgraded to 5.9.1_18 and tried to add a Tapo s505 simple on/off matter WiFi switch. I used the ud mobile app to add via QR code . Go this error: Could not Write characteristic: 18EE2EF5-263D-4559-959F-4F9C42 9F9D11: The specified UUID is not allowed for this operation. This may be caused by an iOS security measure that requires developers to install a developer profile see https://docs.silabs.com/mobile-apps/latest/mobile-apps-matter-demos/05-enabling-developer-mode

Yes adding an app password was the answer, thanks for the tips. SMTP now works. I suspect that that tmobile is rate limiting the messages coming from UD. I am able to send some texts via the phone@tmomail.net gateway using my gmail SMTP but may be rate limited too. I'll update if I figure that out.

@sdynak that is a Gmail account. I have my own domain setup in a Gmail workspace. I can’t use pushover as. I send to many people and don’t want to make each of them get a pushover app.

So I've confirmed that the t-mobile email to SMS gateway is still working when I send to it from my personal email address. I suspect they have blocked the default UD SMTP server. I tried using my own gmail login in the admin console but get smtp error -1 (see below). Do you see anything wrong with my settings?

I have the paid for notification app, never used pushover. Some of the notifications go to family members and they seldom read emails, that is why I want to send SMS.

It sounds like this may have stopped working a while ago and I haven’t noticed. Anyone know of another way to send sms messages from iOX? Maybe the notification plugin?

notifications to [phone-number]@tmomail.net are no longer working. I'm using the default smtp settings and the "send notification to" action.

So I upgraded to standard to fix the problem. FYI, what had me confused is that I didn't realize the "6249 Southridge greens event" was continuing to cause the "reached max daily message count" messages. In fact I had forgot I was the one causing those notifications to happen. I thought the 6249 messages had stopped and the max daily message count notifications were just stuck in a loop. I also didn't expect the limit on the free version to be so small (about 8 per day?). It's my lack of understanding and I'm sure that was obvious to you but not to me. Thanks for taking the time to look at it.