Domoticz

In the source there are traces of code indicating native support for Thermosmart is coming. However these traces are several months old, so I wonder if there is still being worked on.

Would be nice though!

mastair wrote:In the source there are traces of code indicating native support for Thermosmart is coming. However these traces are several months old, so I wonder if there is still being worked on.

Would be nice though!

Rob is still working on it. I gave him access to my system. There was a small problem but i hope it can be solved.

In V2.2907 is thermosmart intergrated in domoticz! Much thanks to Gizmocus for his work!

Very nice. It does not work for me however. Log says 'check username/password', so I checked it three times.

Client id and secret I got from the back of the thermosmart where id starts with ITxxxxx.

Am I missing something?

mastair wrote:Very nice. It does not work for me however. Log says 'check username/password', so I checked it three times.

Client id and secret I got from the back of the thermosmart where id starts with ITxxxxx.

Am I missing something?

Client id and secret you got from thermosmart, id starts with api-xxx. It xxxx is your thermostart id and you don' t have to fill this in. Username and password are the same as the webinterface.

When or where should I have received this client id and secret? I was one of the first with Thermosmart long before the api was there.

Shouldn't Domoticz sign up for an API key once (through https://docs.google.com/forms/d/1_uojxF ... rm?c=0&w=1) and use that for every domoticz user? Just like IFTTT does?

mastair wrote:When or where should I have received this client id and secret? I was one of the first with Thermosmart long before the api was there.

Shouldn't Domoticz sign up for an API key once (through https://docs.google.com/forms/d/1_uojxF ... rm?c=0&w=1) and use that for every domoticz user? Just like IFTTT does?

You must sent a email to thermosmart and apply for a api then you get a client id and a secret.

Exactly my point. That is not how the API is designed. Then every user will have to apply for an API key, in stead of every product (and they will have to process the requests manually).

I am pretty sure Gizmocuz should apply for one API key for Domoticz and hardcode it in the source. Only downside is that the webhook cannot be used but who really cares. Domoticz now polls every 30 sec anyway.

mastair wrote:Exactly my point. That is not how the API is designed. Then every user will have to apply for an API key, in stead of every product (and they will have to process the requests manually).

I am pretty sure Gizmocuz should apply for one API key for Domoticz and hardcode it in the source. Only downside is that the webhook cannot be used but who really cares. Domoticz now polls every 30 sec anyway.

I cann't do anything on that problem. You have to make a comment by thermosmart for that. I only know that for pvoutput( solar) i also have to apply for an api by mail.
But the bottom line is that there's a intergration with domoticz.

My guess is you did not read my messages nor the link I posted (but I'll forgive you... ).

So again, Thermosmart has an api. The software supplier who wants to integrate Thermosmart in its software package should apply for an API key (see the link I posted), not the user.

That's exactly why we do NOT need an API key to control Thermosmart with IFTTT. IFTTT applied for an API key for Thermosmart (the users should not). I just need my username and password to connect Thermosmart to IFTTT (no API key).

Hopely GizMoCuz can join this discussion because I'm feeling not understood....

mastair wrote:My guess is you did not read my messages nor the link I posted (but I'll forgive you... ).

So again, Thermosmart has an api. The software supplier who wants to integrate Thermosmart in its software package should apply for an API key (see the link I posted), not the user.

That's exactly why we do NOT need an API key to control Thermosmart with IFTTT. IFTTT applied for an API key for Thermosmart (the users should not). I just need my username and password to connect Thermosmart to IFTTT (no API key).

Hopely GizMoCuz can join this discussion because I'm feeling not understood....

I understand your point but I think, correct me if I'm wrong, if the api key is applied by domoticz you can only read out your temperature and not controlling your device.For me it is now possible to pause my thermosmart.

We can do all of that with IFTTT, so that is not the case.

The thermosmart webhook does a hppt get from an url provided by the API registration to signal changes in the thermosmart parameters or settings
As domoticz does NOT run a central service you can not have domoticz register for an API key but every user of Thermosmart needs to register and you need to provide a webhook url that connects to your domoticz instance.

You do not need the webhook.

Domoticz does polling.

Agree the webhook is not needed, but if used it provides much quicker updates of temperature changes

Agreed... So the golden solution would be that a default Domoticz Thermosmart api key is provided, but the user can override it, but I hardly think there is a true benefit to that.

i applied for an API key now almost 2 weeks ago, and did not received back any reply
maybe because i do not own the hardware?

Maybe someone can PM me an API key that we can use globally ?

I send you PM

I have to agree with mastair. If the functionality is embedded in domoticz this would make it a lot easier to use and implement for the "common user".

I received an api client_id/secret, there is a new beta available.
After the update, you have to setup the hardware again and provide your username/password