Domoticz

I have the same problem.. hope some update will fix this..

There is a topic at the eneco forum with more information on how to possibly solve this.

https://forum.eneco.nl/storingen-proble ... ring-12123

Sent from my LG-F800L using Tapatalk

The problem is clear. Eneco has blocked access to the toonopafstand.eneco.nl API, that was never meant to be an public API. There is a new public API (that's still not public AFAIK) see documentation at http://www.toonapi.com/

The problem is that this API will not work for the in the same way the "old" API does. You need a licence and OATH2 credentials.. So domoticz will need some sort of cloud solution in the future to access this API (because it will not be possible for all Domoticz users to get a license).

So by making an open API, Eneco has actually made the whole system less open...

I also have the same problems. After more than a year I found Toon to be immature and buggy (mainly because of the Eneco service center). Because of the recent problems and the lack of communication from Eneco I am going to switch to Essent and try the Nest for a while.

It is the User-Agent .. Domoticz used now "domoticz/1.0"
Maybe someone can make Domoticz with new user agent for the pi?

Credits to the person finding out that certain user agents were blocked now. I changed it in the httpclient to mimic a chrome browser, compiled it, and now indeed all the Toon data is being retrieved again. I guess we'll have to decide if this is an acceptable fix to put in the normal source? Cheers.

lukev wrote:

mAiden88 wrote:...for the pi?

Why only for the Pi?

Sorry, couple of ppl run domoticz on nas,

The problem with a general patch to change the User Agent for the Toon in Domoticz is that the new User Agent string can easily be blocked also.
I'm thinking of letting the users choose their own User Agent string in the config of the Toon hardware in Domoticz. Any other ideas?

IgorYbema wrote:The problem with a general patch to change the User Agent for the Toon in Domoticz is that the new User Agent string can easily be blocked also.
I'm thinking of letting the users choose their own User Agent string in the config of the Toon hardware in Domoticz. Any other ideas?

It would be really silly (not to say dumb) to block the generic chrome/firefox/ie user agents. Because that way nobody could use https://toonopafstand.eneco.nl anymore. It would be far more easy for Eneco to just whitelist those generic Agents and if they did that, your solution would not help a bit.

We already got a call from Eneco.
The problem is indeed that there is a lot of traffic from domoticz users, like twice as much as from phone users, and 4x as much as web users.
This is not strange, and domoticz continuously polls for new data, and a phone user does this on demand.

Now i want to suggest to increase the poll interval, this is now 30 seconds, lets make it 300 (each 5 minutes)

That will decrease the millions of requests/year

I hope to have an answer next week with a solution that fit both parties.

Bdw, you can not block a ios user agent request, that would mean all ios users are not able to login....

gizmocuz wrote: Now i want to suggest to increase the poll interval, this is now 30 seconds, lets make it 300 (each 5 minutes)
That will decrease the millions of requests/year
I hope to have an answer next week with a solution that fit both parties.

Nice! To bad I have to wait an other week to be able to use Domoticz/Toon again. What are your thoughts on using the public oath2 API?

It is not so easy to integrate an oauth2 server in domoticz... if someone want to do this, that would be great as more and more web based management systems are using oauth2
There is still a rest API

Adriaan25 wrote:Credits to the person finding out that certain user agents were blocked now. I changed it in the httpclient to mimic a chrome browser, compiled it, and now indeed all the Toon data is being retrieved again.

Is this hard to do?
How does it work, just pull the source from github and do a make/install on my raspberry pi?

I'd be content with a temporary solution. Not being able to properly use my thermostat is annoying.

See: https://github.com/domoticz/domoticz/pu ... 5796497ffd
Line: 170

IgorYbema have change the useragent, by Toon script..
Now lets wait.. I hope soon Domoticz will work agian with Toon.

You don't need to wait for Domoticz to allow the patch. You can easily change it yourself. If a better solution comes in hand you can remove the old patch done by yourself and override it with Domoticz's solutions again.

IgorYbema wrote:You don't need to wait for Domoticz to allow the patch. You can easily change it yourself. If a better solution comes in hand you can remove the old patch done by yourself and override it with Domoticz's solutions again.

How?
I get always error by make.
Maybe you can help me?

where to find this file on an Rpi?

Install latest beta (5769). The httpclient is changed and most likely the interval has been increased.

Still get the message Error: ToonThermostat: Error getting current state!
Also setting the programState via json doesn't work.
I tried setting the setPoint via json, that works.

It looks like somethings changed at Eneco side. I get no P1 information from Toon anymore.
Also setting state seems no longer possible, with the current implementation...