Heltun HLS01 switch in thermostat mode

[youra]

Hi all.

I'm using an HLS01 in thermostat mode - I can't though see any way of accessing or using the manual switch in that mode - I'd like for example the option of using a local switch to change the thermostat mode temporarily, with a rule turning it off after an hour, for example.

Is there a driver out there somewhere that will allow this? Also, if used in switch mode, can the temperatures sensed by the NTC be read, that might allow a different approach.

Thanks!

[dmitry.rozovik]

Hello!

HIGH LOAD SWITCH HE-HLS01 USER MANUAL for Hardware v.84 & Firmware v.1.5

DEVICE TYPE “THERMOSTAT”

Parameter 08 – External Input Mode
0 – the input state changes will be ignored by the Thermostat logic.
1 – the external input will operate in “Toggle Switch” mode: if the external input is shorted (with
Sx or Line) the Thermostat switches to the operating mode selected in the Parameter 09 and
switches to OFF mode when the external input is open.
2 – the external input will operate in “Toggle Switch Reverse” mode: if the external input is
shorted the Thermostat switches to OFF mode and switches to the operating mode selected
in the Parameter 09 when the input is open.
3 – the external input will operate in “Push Button (Momentary Switch)” mode: each press of
button (shorten of input) will consistently change the mode to the operating mode selected in
the Parameter 09.
The factory default value is 0.

Parameter 09 – External Input Action
This Parameter allows selection of which Operating Mode the HE-HLS01 should revert to
when the external input is shorted. 1 = Heat, 2 = Auto, 3 = Dry, 4 = Energy Saving, 5 = Away.
The factory default value is 1

My thoughts are:

Whith this information it sounds that when configured button may change operation mode to some predefined value. Usually on mode change device should send a report to the hub about mode change. It is poosible to make RM rule that will be listening attribute change to initiate some sequence. Though one important point remains - identify if attribute change were triggered by the HUB-initiated command or not. This either can be achieved by:

• changing the driver it self (setting some local state variable or additional attribute [like "desired mode" and "actual mode"] when issuing command)
• using some external/global variable together with another RM rule to control the device (avoiding direct thermostat control either from device page or from dashboards)

Both variants are sophisticated to implement. First one is only possible with some community driver (needs source code access)

P.S.:
Manual seem to not to mention temperature measurement command class capabilities (no temperature report).

[youra]

Oh - wow - thanks - exactly what I was looking for!
I think I've seen a driver somewhere that allows arbitrary parameter setting, so I'll just do that - it's not something I'm likely to want to do often after all....

Interesting that the temperature report is not mentioned anywhere - it certainly does, but sometimes a little oddly - the decimal point (sometimes) goes astray, with, for example 23.7C being reported as 237 - internally it's using the right reading so functioning correctly, just what's sent over the air, but only sometimes....

[youra]

I've used the arbitrary parameter setting tool and set things as the manual says, but unfortunately it's not working - I'm reasonably confident that I have the right parameters, as the defaults are as the manual says they will be, and are read back to what I change them too, but the behaviour doesn't change. Maybe (but I doubt it) the behaviour is different for FW v1.7 as I can only find a manual for v1.5 latest.
I'll check with Heltun support and see what they say.