What a result, great investigating and uncovering. Nice work, really happy you managed to get to the bottom of it and now have heating working as you envisaged.
Hopefully now thats put to bed and one more thing that just works and is forgotten about.
Except I set it to 21.5 while testing, and forgot to turn it off … what a toasty night we had 
Hey there. So glad you guys discussed this topic! I’ve been trying to a while to get this working and it’s driving me insane! My SLR2b is running in dual mode, and I can see the zigbee2mqtt is receiving the changes, but it won’t budge out of “idle” state. If I manually turn them either CH or water to “on”, I can’t turn them off via z2m.
Example payload:
mosquitto_pub -h mqtt -t 'zigbee2mqtt/Boiler Control/set' -m '{"system_mode_water":"off","temperature_setpoint_hold_water":0,"running_state_water":"off"}'
mosquitto_pub -h mqtt -t 'zigbee2mqtt/Boiler Control/set' -m '{"system_mode":"heat","temperature_setpoint_hold":"1","occupied_heating_setpoint":"21.5"}'
Any help would be greatly appreciated!
Try “reconfiguring” the device in Zigbee2mqtt. Also, temperature_setpoint_hold should be true/false, not "1"/"0".
Even with true/false, no joy. Could you tell me what firmware version you’re running? Mine could be old (potentially buggy?). And, which version of zigbee2mqtt? I’ve upgraded as a long shot to 1.27.2 but no dice.
Another questions… If you turn on the thermostat manually, what happens? Does it show up in z2m?
"device": {
"applicationVersion": 50,
"dateCode": "20190618",
"friendlyName": "x",
"hardwareVersion": 1,
"ieeeAddr": "x",
"manufacturerID": 4153,
"manufacturerName": "Computime",
"model": "SLR2b",
"networkAddress": 23208,
"powerSource": "Mains (single phase)",
"stackVersion": 2,
"type": "Router",
"zclVersion": 1
}
OK, one disclaimer… I’m not running a thermostat, so literally just the relay on its own. I can’t see it being an issue within the docs.
Hi everyone
i
first of all thanks to everyone so far for their suggestions. I’ve looked into the problem with the temperature jumping back to 1 degrees and it looks as though it’s because of the thermostat receiving invalid commands. Mainly HA publishing data that is incompatible with the remote.
I’ve created an alternative config to get round the problem to more closely match how the hive remote works. It’s here if anyone finds it useful
HI, I haven’t checked @greeeny101’s solution yet, but I will try, but in the meantime I can start the Hive, but any duration I input resets to 65535. Is there anyway round this?
Hi,
Thanks for the effort, but do you think it would be possible to write up some instructions? I genuinely don’t even know where to start with this. I am learning this all the hard way as I migrate to Zigbee2MQTT.
Thanks again!
Edit: I figured it out with some trial and error. I will write a short tutorial in future.
Hi,
I’m having similar issues was wondering if you’d managed to write some instructions or had some tips?
Thanks
Fairly sure this is the most recent firmware.
I’m looking into this now myself, bit of a minefield with lots of different ideas / device.
Based on this thread simply being more recent I’ll try some of the ideas here.
This is a rough guide because I meant to do this sooner, but was busy and I can’t remember everything perfectly.
I can’t remember if I missed anything, but that’s how its setup looking at mine. Also, those links are for the SLR2 same process for SLR1 just use those configs instead.
This is not an optimal layout for this. You’d ideally want to split your MQTT stuff out differently, but this gets the general gist across, which is where I was initially lost.
My overall recommendation is to move away from Hive because even with this very useful script, it’s still a bit finicky. I got some Drayton Wiser stuff and will be switching soon instead. But in the meantime its functioned well enough for me.
Also, just want to say Hive sucks for their e-waste hub scam. Absolute nerds.
Thanks - it was the formatting of the main yaml file that threw me. Throws a lot of errors in VS Code so I assumed there was something else needed.
I’ll take a look at your instructions and report back.
What I found interesting is the zigbee payload messages include weekday information on mine.
Be interesting to see if there’s anything that can be done with that (I tried a few publish messages but they definitely don’t take hold).
When i copy in the config_input_number i seem to get loads of errors. Can anyone help?
I’m not sure if this is greeny’s setup, or a similar one I found. Seems to work for me. Plan to improve the boost setup at some stage if I can (I’d love for them to add a “boost” to their thermostat integration to be honest!).
It’s very much in progress haha.
configuration.yaml
mqtt:
!include_dir_merge_named hive/mqtt
#Load automations
automation ui: !include automations.yaml #UI designed Automations
automation hive_down: #Hive Automations
!include hive/automation/Hive_Downstairs.yaml
automation hive_up: #Hive Automations
!include hive/automation/Hive_Upstairs.yaml
#Load custom packages
homeassistant:
packages:
!include_dir_merge_named hive/integrations
!include_dir_named packages/
Created a folder called hive in config with the below subdirectories:
I’m having issues with the multiple files / multiple stats right now FYI.
Hi @Burgess101 ,
I tried this but got nowhere… Do I need to do something with MQTT HVAC? The card I added to the dash didn’t do anything but allow a temperature to increase.
@alexcf did you ever get it working without a thermostat? I am struggling to get the relays to switch on and I’m beginning to wonder if the lack of thermostat is the reason.
I ended up having to pair everything back to Hive. The thermostat is the “thing” that kicks it on, so you might well need it. Super annoying if you want HA to control it. The only way I can see a way of doing it is disabling the schedules and having HA do “boosts” when it sees temp dropping. I need to do a proper overhaul!
Yes, you need both the receiver and the thermostat. Whilst you can ignore the thermostat (and use any temps Ensor you like), it is quite accurate and so is useful as such.
My method is to have the Hive App in ‘manual mode’ (in fact the app has been deleted) and everything is controlled via HA. To ensure this works, I have an automation that does everything including ensuing the mode is correct when HA restarts.
The following might help you. Note I have truncated sensor.hive_heating_target_temp as it is a long and not central to this point. The entire package is here if you are interested, but I have tinkered with it since to include a schedule setting that reacts to my house ‘waking up’ with a ‘pre-heat’ to warm the house before ‘waking up’).
input_select: #-----------------------------------------------------------------
hive_heating_target_mode:
name: Hive heating mode
icon: mdi:radiator-disabled
options:
- "off" # Hive thermostat is in frost protect
- "heat" # Hive thermostat is in manual control
template: #---------------------------------------------------------------------
- sensor:
# Mode as reported by HIVE thermostat: off, heat, auto (Hive schedule), emergency_heating (Hive boost)
# mum (SLR1c) James SLR2c:
# state: climate.hive climate.hive_heat
- name: "Hive heating reported mode"
unique_id: hive_heating_reported_mode
state: "{{ states('climate.hive_heat') }}"
- name: "Hive heating target temp"
unique_id: hive_heating_target_temp
device_class: temperature
unit_of_measurement: °C
[...]
automation: #------------------------------------------------------------------
# set mode and temp
# Name of receiver is "Hive":
# SLR1c: zigbee2mqtt/Hive/set
# SLR2c: zigbee2mqtt/Hive/heat/set
# &: zigbee2mqtt/Hive/water/set
- alias: Hive heating
id: "hive_heating"
description: ''
mode: queued
initial_state: true # ensure automation is on at startup
trigger:
- platform: template # reset mode if out-of-sync
value_template: "{{ states('sensor.hive_heating_reported_mode') != states('input_select.hive_heating_target_mode') }}"
- platform: state
entity_id: input_select.hive_heating_target_mode # user sets sets new mode
- platform: homeassistant
event: start # set correct mode on startup
- platform: state
entity_id: sensor.hive_heating_target_temp # programme sets new temp
action:
- choose:
- conditions:
- condition: state
entity_id: input_select.hive_heating_target_mode
state: 'off'
sequence:
- service: mqtt.publish
data:
topic: zigbee2mqtt/Hive/heat/set
payload: |-
{
"system_mode":"off",
"temperature_setpoint_hold":"0"
}
- conditions:
- condition: state
entity_id: input_select.hive_heating_target_mode
state: 'heat'
sequence:
- service: mqtt.publish
data:
topic: zigbee2mqtt/Hive/heat/set
payload: |-
{
"system_mode":"heat",
"temperature_setpoint_hold":"1",
"occupied_heating_setpoint":"{{ states('sensor.hive_heating_target_temp') }}"
}
- conditions:
- condition: state
entity_id: input_select.hive_heating_target_mode
state: 'auto'
sequence:
- service: mqtt.publish
data:
topic: zigbee2mqtt/Hive/heat/set
payload: |-
{
"system_mode":"auto",
"temperature_setpoint_hold":"1"
}
- conditions:
- condition: state
entity_id: input_select.hive_heating_target_mode
state: 'emergency_heating'
sequence:
- service: mqtt.publish
data:
topic: zigbee2mqtt/Hive/heat/set
payload: |-
{
"system_mode":"emergency_heating",
"temperature_setpoint_hold":"1",
"temperature_setpoint_hold_duration":"{{ states('input_number.hive_heating_boost_time')|float *60 }}",
"occupied_heating_setpoint":"{{ states('sensor.hive_heating_reported_current_temp')|float + states('input_number.hive_heating_boost_temp')|float }}"
}
I can report greeny101 solution works, but I was using updated fix by
Please Note yaml file config_automation folder was throwing back errors because some brackets were not properly indented
I just ran it trough the https://www.yamllint.com/ to find them and fix them and everything worked after that