Well, since i’m on ZHA update didn’t reach me yet anyway…
Note that temperature sensor can be inaccurate for more than that… :-), so, i agree, it’s perfect.
The strange thing for me is that even with the smart mode enabled I don’t hear the TRV making any adjustments to change the flow when getting close to target temp.
I am also getting overheating for some reason. See my son’s room below. 19.5 target yet heating still on at over 20c
Well, it could be that if smart control is enabled it will always say “heating”, since only valve opening percent is changing as valve is trying to find optimal open percentage.
But, in your case it obviously heats too much, yes.
you are searching for a ‘number.', wheras a temperature sensor is usualy a 'sensor.’
@darki12 and @Protoncek, other users have also experienced not so great results with the new smart feature. Sonoff is aware and will probably make it ‘smarter’ in the future.
1 Like
Hi @photomoose
Thx for the blueprint. I have just separated my Z2M setup from Home Assistant so now it is running on the side in a container on Proxmox. I have been using the blueprint to setup my TRVZB to get temperatures from my Aqara sensors. I’m just wondering one thing: Normally when using Zigbee2MQTT I would have to edit the Zigbee2MQTT devices.yaml file to make sure the force_update setting on each external temperature sensor is explicitly set.
Does anyone know which file I have to edit in my Zigbee2MQTT container?
Huh? What do you mean, why you need to update devices.yaml ?
Constant Temperatures (Max Rep Interval)
To prevent the TRV from entering fail-safe mode, the external temperature has to be regularly sent to the TRV. This blueprint is triggered by changes made to any of the attributes of the external temperature sensor entity in Home Assistant. The “Max Rep Interval” reporting setting on a device specifies how long a Zigbee device must wait before rebroadcasting its state even if there have been no changes in value. A value of 3600 typically means the Zigbee device will report its state once every hour. It is advised to ensure this value remains under 7200 (2 hours) so that the device is still reporting during long periods of constant temperature.
If using Zigbee2MQTT, further configuration of the external temperature sensor may be required. By default, Zigbee2MQTT does not report back into Home Assistant if an entity’s value has not changed, regardless of its reporting interval. To ensure this happens, the force_update setting on each external temperature sensor needs to be explicitly set. This is done by editing the Zigbee2MQTT devices.yaml file, as follows:
'0xd44867fffe111ce1':
friendly_name: Kitchen Temperature Sensor
homeassistant:
temperature:
force_update: true
By doing the above, the blueprint automation will be triggered by each report from the external temperature sensor, ensuring that fail-safe mode will not be activated on the TRV during a 2 hour period of constant temperature.
Hey, it’s been a while since I’ve been active on this thread…
I have also just discovered the STC feature and I’m giving a test now. Initial findings suggest the rooms tend to overheat, but that could be because my temperature sensor reporting settings reverted to the default of 1C. I will give it some more time to settle and see what happens.
Hi everyone.
This is my adjustments for this blueprint: GitHub - shaggee/Sonoff-TRVZB-external-temp-report-and-update-interval · GitHub
- Configurable update interval
- Deterministic per-instance start offset
- Per-TRV delay
- Auto-ensure external sensor
If you need more features/adjusments let me know.
PSA: Fix your TRVZB automations (and probably TRVZBT as well) if using Z2M
feat(improve): imporve SONOFF TRV-ZBT, TP-WGZBA controls by CubeZ2mDeveloper · Pull Request #13268 · Koenkk/zigbee-herdsman-converters · GitHub changed the way the TRV has its external sensor configured to new values. This breaks any automations that had they as triggers as well as those who interact with them.
In my case, I had a trigger if a TRV was external_3, meaning the external temp didn’t update - this is gone and replaced with remote_source_offline.
Then I configured the TRV back to external_1 and forced an update with the external temp sensor value - this action no longer works since external_1 is replaced with remote_temperature.
This is not a big deal but not all users read the release notes and might have to find about broken automations the hard way, so I’m mentioning here to bring it forward.