Domoticz

Hello folks,

I have a lyric T6R-HW (later model incorporating hot water functionality). The domoticz (v 4.11020 on Ubuntu) integration via the HoneyWell API (steps as described above) is working very well for monitoring central heating/thermostat temperatures but I was wondering if anyone had any experience with getting the HW channel running too?

Thanks,

Rob

In step 4 of the wiki I am stuck.

I have given in: https://api.honeywell.com/oauth2/author ... t_uri=none
The reply is: "The redirect URL provided does not match the redirect URL registered for the app."
The app of which the API key is, has my home IP address as the URL registered for the app. It is the address that https://www.whatsmyip.org/ gives.

So I cannot login and get the code.
Any ideas?

OOPS. Good reading is an art... I had to put none instead of my home IP address into the app setting. Now it works

Hi,

is there also a way to get this info on a windows platform??

7. Base64 encode the following string (without quotes) "[[APIKey]]:[[APISecret]]" . This can be done from the Linux command line by using
echo -n "[[APIKey]]:[[APISecret]]" | base64

thanks

Maybe Powershell?

But my go to is WSL (Windows Subsystem for Linux). Standard option in Win10. Just enable it and select for example Ubuntu in the Windows Store.

Gives you a Linux shell where you can execute commands like the one you are looking for.

worked fine! thanks for the reply.. one step further again..

now building a script on a cisco DX80 to control my T6

Hi all,
Does anyone have issues with the T6 thermostat after the update ? Mine was stopped working. After deleting it and reinstall this device I don't see it even back in devices.

Had something simular, I solved it by giving the device another name

DannyK wrote: ↑Tuesday 20 April 2021 19:55 Hi all,
Does anyone have issues with the T6 thermostat after the update ? Mine was stopped working. After deleting it and reinstall this device I don't see it even back in devices.

i have the same isseu since i did a fresh new install of the latest stable version. Renaming the device and reinstaling did not work for me. Is the a bug? In the Wiki i noticed the Honeywell Page is not there.. Any info on this??

After some issues updating to newer (beta) release the Honeywell API interface has stopped (again).

Is there an easy way to get this working again without eg doing the whole definition of user/secret/64code bla bla again.

Why does it stop actually assume all keys at a point in time are valid and as far as I noticed during intial setup all keys never should expire.

Quite quick solution:
https://api.honeywell.com/oauth2/author ... client_id=[[YOURAPIKEY]]&redirect_uri=none
will give you a new Code.

Due to this changing response code the latest curl command needs to be adapted and rerun with this new code.

The base64 code you generated before remains the same.

i put all in a mail to myself and now only need the first step getting the new code and the curl command with the new code.
Copy paste this way and the access/refresh keys can be put into appropriate field.

Hello, I have a problem for a while now with my T6. Multiple times a day i get an error in the log:

Spoiler: show

2023-11-14 18:36:21.489 Error: Thermostaat: Error getting thermostat data!
2023-11-14 18:41:22.093 Error: Thermostaat: Error getting thermostat data!
2023-11-14 18:46:22.705 Error: Thermostaat: Error getting thermostat data!
2023-11-14 19:06:34.822 Error: Thermostaat: Error getting thermostat data!
2023-11-14 19:11:36.327 Error: Thermostaat: Error getting thermostat data!
2023-11-14 19:36:41.982 Error: Thermostaat: Error getting thermostat data!
2023-11-14 19:52:22.606 Error: Thermostaat: Error getting thermostat data!
2023-11-14 20:02:50.351 Error: Thermostaat: Error getting thermostat data!
2023-11-14 20:22:54.125 Error: Thermostaat: Error getting thermostat data!
2023-11-14 20:27:54.729 Error: Thermostaat: Error getting thermostat data!
2023-11-14 21:53:09.471 Error: Thermostaat: Error getting thermostat data!
2023-11-14 21:58:10.077 Error: Thermostaat: Error getting thermostat data!
2023-11-15 02:59:35.388 Error: Thermostaat: Error getting thermostat data!
2023-11-15 07:00:29.710 Error: Thermostaat: Error getting thermostat data!
2023-11-15 08:20:47.472 Error: Thermostaat: Error getting thermostat data!
2023-11-15 08:25:48.077 Error: Thermostaat: Error getting thermostat data!
2023-11-15 08:30:48.663 Error: Thermostaat: Error getting thermostat data!
2023-11-15 09:51:02.346 Error: Thermostaat: Error getting thermostat data!
2023-11-15 09:56:02.965 Error: Thermostaat: Error getting thermostat data!
2023-11-15 10:01:03.581 Error: Thermostaat: Error getting thermostat data!
2023-11-15 12:21:27.032 Error: Thermostaat: Error getting thermostat data!
2023-11-15 12:26:27.602 Error: Thermostaat: Error getting thermostat data!
2023-11-15 12:31:28.235 Error: Thermostaat: Error getting thermostat data!
2023-11-15 13:57:00.796 Error: Thermostaat: Error getting thermostat data!
2023-11-15 14:02:01.415 Error: Thermostaat: Error getting thermostat data!

When this happens i can see the thermostat has connection with the internet. I can reach it with the app on my mobile phone at the time the error is in the log. After a while it seems to restore and the error goes away.

As there must be a few number of errors, does anyone know if there is a way to see what is causing this error, specifically?

having same issue.

Same here.. they are notorious for their flakey api servers. I even have a process to monitor the Domoticz log and do a hardware restart one time after it cails to force refresh the oauth tokens, which mostly works, but the last couple of days there has been a lot of downtime.

Ah so it is on their side. Thanks for acknowledging, yes is script that would keep track of the error message and then refresh tokens or restart hardware would be a good idea. ...

Looking at the log which monitors the Honeywell device for failures and token updates, it seems that only the GetData requests that are done after 900 second the token was refreshed that are failing, never one that is done between the 0-620 seconds, while the token should be valid for 1799 seconds. Just as test I have proxied the api.honeywell.com calls via an nginx server which will change the returned JSON from the API request from "expires_in":"1799" to "expires_in":"699". I see this in my domoticz log as: This is now running for a couple of hours and haven't had a issue since then. Will keep an eye on this the coming days and propose an change for the hardware option to set it to divide the received expires_in by 2 when that fixes it.
As a side note: we need to call https://api.honeywell.com/oauth2/token which returns "expires_in":"1799"
while as described here:https://developer.honeywellhome.com/con ... uth2-guide
an API call to https://api.honeywellhome.com/oauth2/token returns "expires_in":"699" which sort of underlines my thinking here.

There have not been any issues after I lowered the refresh-token to 699 till now.

Well, that is good news, right! Perhaps in next beta it could be implemented?
Bit weird though that it expires too early. Pretty nice of you to figure this out for me, us and the rest, thanks
Ah yes also strange it says expires in 599 and we see 1799. I read the doc guide later, now i see.

Thuis wrote: ↑Friday 08 December 2023 14:18 Well, that is good news, right! Perhaps in next beta it could be implemented?

Not sure yet what to propose and I currently do not have a development environment to program the changes and test.
It currently takes the returned value which we either need to divide by 2 or simply hardcode to 699.
@gizmocus, I case you read this, feel free to jump in as to the best solution for this.

Thuis wrote: ↑Friday 08 December 2023 14:18 Bit weird though that it expires too early. Pretty nice of you to figure this out for me, us and the rest, thanks
Ah yes also strange it says expires in 599 and we see 1799. I read the doc guide later, now i see.

They are 2 different API sites for Honeywell! api.honeywell.co and api.homewellhome.com
You could implement the same workaround as I did in case you have a nginx server (192.168.1.123) running that can support port 443 or already supports 443 and add this specific site that only responds to https://api.honeywell.com requests.
The implemented workaround is:

• Add an site to nginx on any nginx server that supports port 443 with any ssl token:

  Code: Select all

  server  {
  	include    /etc/nginx/proxy_params;
  	listen 443 ssl;
  	keepalive_timeout 70;
  	server_name api.honeywell.com;
  	## added this to force dns resolution  -> https://forum.nginx.org/read.php?2,215830,215832#msg-215832
  	set $backend "api.honeywell.com";
  	ssl on;
  	ssl_certificate             /etc/ssl/letsencrypt/SSLcertificate.crt;
  	ssl_certificate_key         /etc/ssl/letsencrypt/SSLprivatekey.key;
  	access_log /var/log/nginx/honeywell.access.log;
  	error_log /var/log/nginx/honeywell.error.log;
  	resolver 8.8.8.8 valid=10s;
  	location / {
  		proxy_set_header Host api.honeywell.com;
  		## Changed this to force dns resolution  -> https://forum.nginx.org/read.php?2,215830,215832#msg-215832
  		# proxy_pass https://api.honeywell.com;
  		proxy_pass https://$backend;
  		sub_filter '"expires_in":"1799"' '"expires_in":"699"';
  		sub_filter 'Invalid' 'foutje';
  		sub_filter_types *;
  	}
  }

• Change /etc/hosts on the RPI that runs domoticz and add this record:

  Code: Select all

  192.168.1.123  api.honeywell.com

That should do it. It will make the Domoticz requests go to the Server with the NGINX proxy, which will update the returned JSON info.

Well... i do not have nginx, i even have to google it to see what it does, haha.
I do know what apache is, so im not that stupid, haha, sorry i have a bit of a laughy mood, it''s friday !

Im sorry, thanks for sharing, not for me, perhaps others can use it though!

Looks like this workaroud works for me. Thx