Domoticz

Version: 2025.1
Platform: openSUSE Leap 15.6
Plugin/Hardware: Enphase

At least since September 5th hardware Enphase does not collect any data and gives:

Invalid data received! (production/json)

The cause might be that the token was no longer valid and it looks as if no new token could be obtained.

Today I removed the hardware and tried to re-enable it with a user-id and password that has been renewed, but still I get the same error message. In User Variables I see three entries, the third one, with Production in the name, has a value 0, the other two are empty.

Any suggestion for a solution?

Hi, @freekdk,

The owner of an Enphase installation will get a token that expires after a year and an installer will get one, that expires after 12 hours.
If the token has expired or has got lost for another reason, you will need a new token and a new Session_ID.

And there is the issue:

See my post of September 20, 2025: viewtopic.php?p=328380#p328380

The new documentation of June 2025, you will find here: https://enphase.com/download/iq-gateway ... sing-token.

I have been able to solve it for Node-RED, with the help of https://github.com/Maarten234/Enphase-E ... d/issues/3,
but I'm not able to do that for the native Domoticz solution. Lack of knowledge of C++.

Maybe this will help you.

Regards

Hi @FireWizard

Thanks for the answer. I already guessed that an invalid token was the cause. Somehow this token is saved in a User Variable, which gets created with a suffix of the harware-id, but it does not contain a requested token. Apparently the code to get a new token in the code needs some changes. However I have no idea where and how to do that. I did read the new documentation of Enphase and I am trying to find the proper commands in a bash script to get such a token. I already have one via the webbrowser and I am able to read counter values etc.

Thanks anyway. Maybe I will write a Python script to "replace" the code in Domoticz. I already wrote such scripts for HomeWizard devices.

Regards.

I found the location in the code and indeed the used URL there needed change. I made issue #6395 and got a reaction that it is repaired in beta 16800. Still waiting to have it appear in the stable version.