But photomoose has changed it so even if the temperature stays the same the automation still sends an update.
I’m really not sure I’m understanding your issue.
If the TRV is off and the temp is the same then there is no need for the TRV to react. If the temp changes enough to trigger the TRV then it will be captured by the updates.
Providing your max rep interval is less than what it takes for the TRV to determine the sensor if offline it shouldn’t cause any issues.
I am afraid that force_update: true does not work.
Edit: Narrowed it down to syntax error on my side
I had:
homeassistant: {}
force_update: true
Parenthesis was inserted either by z2m or fileeditor. Following worked:
homeassistant: {
force_update: true
}
Many thanks for this blueprint, Tom.
I observe a weird (but not serious) bug: when the external sensor reports 19.9°C (and only in that case), the automation always adjusts it to 19.8°C…
It was a known issue, and it’s already fixed! The fix is available on the Z2M dev branch, or a few days later in the next Z2M release.
I have had the TRVZB since yesterday and am very glad to have found this right away.
Many thanks @photomoose for this blueprint and the accompanying instructions, it works very well. The value is up to date within 2-3 seconds. My settings:
Hi all, thanks for this great blueprint - have been using this now for about 2 months.
in general, it’s been going great, but am experiencing the following bug:
Any idea what I could test? Many thanks in advance.
Hello. Referring to the comment at this link: Sonoff TRVZB: expose external temperature sensor attributes by photomoose · Pull Request #8873 · Koenkk/zigbee-herdsman-converters · GitHub, has anyone figured out the 3 external sensor options yet? There are currently 4 options to choose from in the Z2M.
I just discovered this blueprint and i thank you for it a lot! I just wondered what i should use instead better thermostat, since i only need open and close valve regarding to external sensor, so better thermostat is “too much” for my needs, while “versatile thermostat” is even more too-complicated. I need simple.
My question, though, is: i use “zigbee home automation” integration, not Zigbee2MQTT, so should i do anything to ensure at least 2 hours report interval? I looked history of my temp.sensor i use for my valve and in the summer there are times when temperature is stable for more than 2 hours, which would mean that sonoff will swith to internal sensor. Ok, it’s off during the summer, but still…
For now i found out that i could set up a new automation to monitor this with template trigger:
{{ (( now().timestamp() - as_timestamp(state_attr('automation.sonoff_trvzb_external_temperature_sensor_calibration','last_triggered'))) /3600)>1.9}}
Is that necesarry?
I can’t seem to find the devices.yaml file… Where is it located?
Thanks
Thanks for the blueprint @photomoose
Just one question. When using Z2M I have to make sure the external temp sensor is forced to update. The blueprint says I must edit my Zigbee2MQTT ‘devices.yaml’ file. I don’t think I have such a file. I have a “/homeassistant/zigbee2mqtt/configuration.yaml” file. Is that the correct one?
I’m asking because I have tried to edit it as described, but after a couple of days or restarts or whatever happens, the force update instruction is removed by itself. It’s there when I edit and restart HA, but then at some point it disappears. Anyone have the same issue?
I modifid the blueprint with a simple additional trigger that updates the TRVZB every full hour, so I dont have to deal with Z2M config files.
triggers:
- trigger: state
entity_id: !input external_temperature_sensor
- trigger: time_pattern
hours: /1
seems to work fine, before the TRVZB went into fallback on a regular basis.
So far it works great, thanks!
Hi Sorry I don’t have a direct answer to your question, but like you I don’t have a specific “devices.yaml” file in config/zigbee2mqtt/ but all my devices are in my /zigbee2mqtt/configuration.yaml. I have added the appropriate coding as suggested to the temperature devices in my config file, they don’t disappear but they also don’t stop the TRVZB’s from switching back to internal over night? I hope @photomoose will shed some light on this for us. I see others have suggested making a seperate devices.yaml but not sure why this is necessary.
Everything has been working perfectly here for quite some time.
It is correct that the change described must be made in the file /homeassistant/zigbee2mqtt/configuration.yaml.
For example my device:
'0x08ddebfffeac6b33':
friendly_name: Temperatur u. Feuchte Büro
homeassistant:
temperature:
force_update: true
I have made the following changes in Z2M for temperature reporting (external sensor):
Maybe it will help some of you. I’m not entirely sure anymore, but I think after a major Z2M update, I had to re-add the entry in configuration.yaml once.
Hi, I am trying to use this blueprint for my TRVZBs but I am using ZHA. I can select the external temperature sensor, but I cannot select the temperature input number.trvzb…external. It simply doesn’t show in the selection dropdown: The Reason seems simple: the class of that input number is probably not set to temperature by ZHA. Is there an eazy way to fix this? (the entities come with the generated device upon registration … )
btw: the actual automation looks really simple so it is not difficult to copy but a nice blueprint like this is an easy way of installing, so that is highly appreciated.
I have similar issue, is there any fixes out there. TRVZB and SNZB-02P
Quick solution is to delete or comment “device_class” lines in the “filter” section of the blueprint (with studio code):
trv_external_temperature_input:
name: Sonoff TRVZB(s)
description:
The entity of the Sonoff TRVZB device that represents the external
temperature value.
selector:
entity:
multiple: true
filter:
- domain:
- number
# device_class:
# - temperature
reorder: false
Then just reload automations and you’ll be able to select appropriate entity.
yes, that is indeed a good quickfix. Edit in Visualstudio or simply in the file editor.
and indeed make sure to do a “quick reload” of HomeAssistant (settings/system/ → go to the on-off button right-top-of the screen and select quick reload): needed to activate the change in the loaded blueprint.
(if you reload the blueprint itself → you reload from git, so you will simply get the original version again)
Hi,
it seems that the Sonoff TRVZB sometimes switches back to internal even though it got updated in time.
Would it be maybe possible to add MQTT call to set it back to “external”?
Regards,
meiser
You can do that easily via Automation, I created one to check if my workaround I also posted in this Thread works
triggers:
- trigger: state
entity_id:
- select.heizung_flur_temperature_sensor_select
from: external
Then just set the state back to external. My Automation also sends me a notification that this error occured.