@Janssens The problem isn’t coming from you but from Enedis unfortunately, it’s a bug that appeared on March 5 ( Problème avec l'intégration Enedis - #17 par pierre-gilles ), which was fixed on April 22 ( Problème avec l'intégration Enedis - #21 par pierre-gilles ), and has just come back.
I’ve forwarded the information to Enedis, I’ll keep you posted.
I’ll see if I can make some adjustments on my side so we can do without this API route which is clearly not stable unfortunately… ![]()