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 Polyglot

2026-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

@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.

@photogeek54 Great job! Those of us using the plug-in really appreciate you finding and fixing the issue.

Thank you @photogeek54 I’ll give it a try.