Whats in your log file?
Hi,
I’m trying this module to connect my Decdeal thermostat to HA but I’ve been unable to.
The thermostat is installed and working, and correctly connected to the network and working through the manufacturers android app.
I’ve set the MAC address of the thermostat so it has a fixed IP address. I’ve configured it on HA using the latest code from the github project (latest commit is from Aug 17th). This is the code (with mac redacted):
climate:
- platform: hysen
devices:
termostat_menjador:
name: Termostat Menjador
host: 192.168.1.5
mac: "98:xx:xx:xx:xx:xx"
But initialization fails:
Logger: custom_components.hysen.climate
Source: custom_components/hysen/climate.py:271
Integration: hysen
First occurred: 17:46:26 (1 occurrences)
Last logged: 17:46:26
Failed to add Broadlink Hysen Climate device:termostat_menjador @192.168.1.5, 98:xx:xx:xx:xx:xx, to HA
Logger: custom_components.hysen.climate
Source: custom_components/hysen/climate.py:314
Integration: hysen
First occurred: 17:46:26 (1 occurrences)
Last logged: 17:46:26
Failed to Authenticate with Broadlink Hysen Climate device:climate.termostat_menjador , ('broadlink_response_error: ', 'The device is offline')
The device is currently on.
Any ideas about what I’m doing wrong?
@sargue, dependent on which model of Decdeal thermostat you have, it probably means it not a Hysen/broadlink device. Is it one of the new ones that supports Alexa/Goggle home etc directly though tuya app etc then it won’t work.
If it is a tuya type HomeAsstiant can control them I’m sure
Oh man… yes, the app shows possible integrations with alexa, google, ifttt…
Do you know by chance if this new models can be integrated with HA?
It’s not accepting my credentials (the ones for the “My Smart Thermostat” app). It says “username” but I got registered using an email address.
Do you know how I can be sure my Decdeal is one of the newer ones? I don’t see any reference to “tuya” anywhere on the app.
Anyway it makes sense… I just bought it. Maybe I should return it and buy a “beok bot-313 wifi”.
@sargue don’t know just assumed it was one of the new round ones and everything I’ve seen refers to it being tuya controlled. Yep beok bot-313 wifi should work I think very similar to my beok one
1 Like
Got the beok and it’s working great. Thanks!
I’ve just rebooted HA and I lost the thermostat…
This is from the logs, not very informative I’m afraid:
Logger: custom_components.hysen.climate
Source: custom_components/hysen/climate.py:314
Integration: hysen
First occurred: 15:48:41 (1 occurrences)
Last logged: 15:48:41
Failed to Authenticate with Broadlink Hysen Climate device:climate.termostat_menjador , ('broadlink_response_error: ', 'The device is offline')
Logger: custom_components.hysen.climate
Source: custom_components/hysen/climate.py:271
Integration: hysen
First occurred: 15:48:41 (1 occurrences)
Last logged: 15:48:41
Failed to add Broadlink Hysen Climate device:termostat_menjador @192.168.1.5, C8:[...] , to HA
It worked before the restart. Any idea what the problem might be?
Hi try a reboot of the thermostat, kill the power and then switch it on again, I get this very rarely but it does happen
Indeed, after a power cycle and a HA reboot its working again.
Thanks!
EDIT: I cannot post more than 3 replies as a new user, so editing:
After rebooting HA it’s again not working.
So it looks like a power cycle is needed after each HA boot ?
EDIT 2: This 3 replies limit is a bit annoying…
Confirmed. I rebooted HA again, and again no response from the thermostat. A power cycle fixes it.
Hi.
I’ve been using this component without any major issues until now.
I set loop_mode = 2 but, for some reason, the device uses a different timeschedule for days 1…5 and another for days 6-7. Exactly as if it were configured with loop_mode = 0.
I did try restarting home assistant also, to no avail…
Is there anything I am missing?
Best regards, and thank you for this nice software.
Just to inform, I got the following message in my log:
No ‘version’ key in the manifest file for custom integration ‘hysen’. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of ‘hysen’
9:20:17 – loader.py (WARNING) - bericht kwam voor het eerst om 9:20:16 en verschijnt 2 keer
added to the manifest so warning no longer occurs
2 Likes
Hi, my hysen integration is not working. A few months ago it worked without problem.
This is the error message: Platform error climate.hysen - Integration ‘hysen’ not found.
I use hassio, version Home Assistant 2021.11.3
I’m try to install again and still no work
Upgraded integration still working for me
Great Lovelace idea. Can you share the script script.set_thermostat_schedule that you are using to set the thermostat schedule? I have one thermostat per room and I’m struggling to set the schedule. Thanks.
Sure, this is what I have in the scripts.yaml:
set_thermostat_schedule:
alias: Set Thermostat Schedule
sequence:
- service: climate.hysen_set_timeschedule
data_template:
entity_id: climate.main_thermostat
week_period1_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period1_start'',
''hour''), state_attr(''input_datetime.week_period1_start'', ''minute''))}}'
week_period1_temp: '{{states(''input_number.week_period1_temp'')}}'
week_period2_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period2_start'',
''hour''), state_attr(''input_datetime.week_period2_start'', ''minute''))}}'
week_period2_temp: '{{states(''input_number.week_period2_temp'')}}'
week_period3_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period3_start'',
''hour''), state_attr(''input_datetime.week_period3_start'', ''minute''))}}'
week_period3_temp: '{{states(''input_number.week_period3_temp'')}}'
week_period4_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period4_start'',
''hour''), state_attr(''input_datetime.week_period4_start'', ''minute''))}}'
week_period4_temp: '{{states(''input_number.week_period4_temp'')}}'
week_period5_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period5_start'',
''hour''), state_attr(''input_datetime.week_period5_start'', ''minute''))}}'
week_period5_temp: '{{states(''input_number.week_period5_temp'')}}'
week_period6_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.week_period6_start'',
''hour''), state_attr(''input_datetime.week_period6_start'', ''minute''))}}'
week_period6_temp: '{{states(''input_number.week_period6_temp'')}}'
weekend_period1_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.weekend_period1_start'',
''hour''), state_attr(''input_datetime.weekend_period1_start'', ''minute''))}}'
weekend_period1_temp: '{{states(''input_number.weekend_period1_temp'')}}'
weekend_period2_start: '{{''{:02}:{:02}''.format(state_attr(''input_datetime.weekend_period2_start'',
''hour''), state_attr(''input_datetime.weekend_period2_start'', ''minute''))}}'
weekend_period2_temp: '{{states(''input_number.weekend_period2_temp'')}}'
1 Like