tomg1970
(tomg1970)
December 30, 2024, 8:49am
133
Yes i have read this. But I don’t know what exactly I need to find the Shelly BLU TRV.
The above code for “mqtt” does not work.
Mking
(Mking)
January 7, 2025, 2:51pm
134
Oke, After Day’s of struggling and sometimes with some improvements. i give up the case is: the MQTT connection from myBLUGW is up. as you can see in the screenshot below. but in HA (left side) the response of the devices stay’s ‘not availible’
The ID of my blutrv is correct
THe ID of my BLUgateway have i copied from the bottom left of the webinterface (and hover text say’s ID) but i cannot find out why in HA i do not get the device running. the only thing i can think of is, that i have one other MQTT device that MQTT did find on its own and is NOT in the configuration.yaml. but this device also a HAVC (Airconditioning) is working. Please someone any idea’s
mqtt:
- climate:
name: "Blutrv"
unique_id: "f8:44:77:2a:f9:32"
current_temperature_topic: "shellyblugwg3-34cdb078aec4/status/bthomesensor:203"
current_temperature_template: "{{ value_json.value }}"
max_temp: 30
min_temp: 4
temp_step: 0.1
temperature_state_topic: "shellyblugwg3-34cdb078aec4/status/bthomesensor:202"
temperature_state_template: "{{ value_json.value }}"
temperature_command_template: "{{ {'id': 0, 'src': 'homeassistant', 'method': 'BluTRV.Call', 'params': {'id': 200, 'method': 'TRV.SetTarget', 'params': {'id': 0, 'target_C': value | round(1)}}} | to_json }}"
temperature_command_topic: "shellyblugwg3-34cdb078aec4/rpc"
mode_state_topic: "shellyblugwg3-34cdb078aec4/status/bthomesensor:202"
mode_state_template: "heat"
modes: ["heat"]
availability:
- topic: "shellyblugwg3-34cdb078aec4/status/blutrv:200"
value_template: "{%if value_json.rpc%}online{%else%}offline{%endif%}"
device:
connections:
- - bluetooth
- f8:44:77:2a:f9:32
name: Blutrv
model: Blutrv
model_id: SBTR-EU867E
manufacturer: Allterco Robotics
Mking
(Mking)
January 7, 2025, 2:55pm
135
What the earlier reply was is that the ‘TAB’s’ or something like that are not correct.
Your code is not formated in the right way HA wants to. i also had this issue and this is an HA logic and not an BluTRV issue.
Mking
(Mking)
January 7, 2025, 3:13pm
137
But how dit i manage to change the topic in the webinterface of the BLUGW?
or in other words is the sollution to change the YAML with replacing the ID
"shellyblugwg3-34cdb078aec4/ to “blutrv”
Bieniu
(Maciek)
January 7, 2025, 3:16pm
138
MQTT Prefix field.
Yes, you can use such topic in the YAML configuration.
1 Like
Great work from @Bieniu ! But i gave up and send them back to Shelly.
Its weird that normal support takes so long while all other devices work fine with the shelly intergration.
I bought 6 Sonoff TRV’s for half the money and they work flawless since i installed them. Just something to think about if you might consider buying smart valves.
Bieniu
(Maciek)
January 9, 2025, 3:45pm
141
New configuration with HVAC action support (firmware 20250109-090619/1.5.0-beta1-g16e0ef4
for BLU Gateway required)
mqtt:
- climate:
name: "Shelly BLU TRV Thermostat"
unique_id: "112233445566"
current_temperature_topic: "shellyblugwg3-aabbccddeeff/status/blutrv:200"
current_temperature_template: "{{value_json.current_C}}"
max_temp: 30
min_temp: 4
temp_step: 0.1
temperature_state_topic: "shellyblugwg3-aabbccddeeff/status/blutrv:200"
temperature_state_template: "{{value_json.target_C}}"
temperature_command_template: "{{ {'id': 0, 'src': 'homeassistant', 'method': 'BluTRV.Call', 'params': {'id': 200, 'method': 'TRV.SetTarget', 'params': {'id': 0, 'target_C': value | round(1)}}} | to_json }}"
temperature_command_topic: "shellyblugwg3-aabbccddeeff/rpc"
mode_state_topic: "shellyblugwg3-aabbccddeeff/status/blutrv:200"
mode_state_template: "heat"
modes: ["heat"]
action_topic: "shellyblugwg3-aabbccddeeff/status/blutrv:200"
action_template: "{% if value_json.pos > 0 %}heating{% else %}idle{% endif %}"
availability:
- topic: "shellyblugwg3-aabbccddeeff/status/blutrv:200"
value_template: "{% if value_json.rpc %}online{% else %}offline{% endif %}"
device:
connections:
- - bluetooth
- 11:22:33:44:55:66
name: Shelly BLU TRV
model: Shelly BLU TRV
model_id: SBTR-EU867E
manufacturer: Allterco Robotics
112233445566
- BLU TRV ID
aabbccddeeff
- BLU Gateway ID
200
- BLU TRV ID from BLU Gateway webpanel
ivdimitro
(Ivan Dimitrov)
January 16, 2025, 10:55am
142
Hi, do we need the BLU gateway at all? I have a shellyplus1pm and interface is practically the same with the same functionality and running faster than the gateway.
Has anybody tried to integrate the TRV via Gen2/3 switch?
One more thing - where is the option to enable the zigbee radio? I tried the latest beta but can’t see such option.
Bieniu
(Maciek)
January 16, 2025, 2:30pm
143
Yes, only BLU Gateway Gen3 supports BLU TRV.
Push 3 times the button on the device.
1 Like
Are there any Updates on the official integration?
Or can anyone post a link to an Step by Step Guide for the MQTT variant?
I’m not talented enough for this. Im used to plug and play from shelly devices.
BJeffrey
(Bryan Jeffrey)
January 17, 2025, 5:16pm
145
I have copied and pasted the code for my BluTrv but my editor is coming up with some errors on the action lines,I am not used to editing code and have tried a couple of things but they did not work any ideas?
action_topic: “shellyblugwg3-e4b3231668e0/status/blutrv:200” Value is not accepted. Valid Values:“cooling”, “Drying”, “fan”, “heating”, “idle”, “off”.
mqtt:
- climate:
name: "Kitchen TRV"
unique_id: "F8:44:77:3A:C4:37"
current_temperature_topic: "shellyblugwg3-e4b3231668e0/status/blutrv:200"
current_temperature_template: "{{value_json.current_C}}"
max_temp: 30
min_temp: 4
temp_step: 0.1
temperature_state_topic: "shellyblugwg3-e4b3231668e0/status/blutrv:200"
temperature_state_template: "{{value_json.target_C}}"
temperature_command_template: "{{ {'id': 0, 'src': 'homeassistant', 'method': 'BluTRV.Call', 'params': {'id': 200, 'method': 'TRV.SetTarget', 'params': {'id': 0, 'target_C': value | round(1)}}} | to_json }}"
temperature_command_topic: "shellyblugwg3-e4b3231668e0/rpc"
mode_state_topic: "shellyblugwg3-e4b3231668e0/status/blutrv:200"
mode_state_template: "heat"
modes: ["heat"]
action_topic: "shellyblugwg3-e4b3231668e0/status/blutrv:200"
action_template: "{% if value_json.pos > 0 %}heating{% else %}idle{% endif %}"
availability:
- topic: "shellyblugwg3-e4b3231668e0/status/blutrv:200"
value_template: "{% if value_json.rpc %}online{% else %}offline{% endif %}"
device:
connections:
- - bluetooth
- F8:44:77:3A:C4:37
name: "Kitchen TRV"
model: Shelly BLU TRV
model_id: SBTR-EU867E
manufacturer: Allterco Robotics
Hope this makes sense this is my first post.
@Bieniu what are you saying? I am not too versed with this stuff as well, but the action_topic
in your YAML provided here is exactly as the one in the question from @BJeffrey (and mine). I am not sure, if you are saying we need to change the YAML, of this indicates another error. Maybe you can add a sentence or two to help those struggling here?
Bieniu
(Maciek)
January 19, 2025, 12:36pm
148
I’m saying the documentation confirms the configuration is correct.
1 Like
I figured out my issue: I downgraded from the 1.5.0-beta firmware after I saw some issues. That broke the integration for me. After upgrading again, everything looks schwifty now. Thanks for all your work @Bieniu !
Bieniu
(Maciek)
January 19, 2025, 12:50pm
150
Last configuration REQUIRES firmware 1.5.0 beta 1. There will be no HVAC action without this firmware.
1 Like
Bieniu
(Maciek)
January 20, 2025, 11:06pm
151
PRs merged
home-assistant:dev
← chemelli74:chemelli74-shelly-trv
opened 10:28AM - 15 Oct 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Add support for new device: Shelly BLU TRV
Release notes: https://github.com/home-assistant-libs/aioshelly/releases/tag/12.3.0
changelog: https://github.com/home-assistant-libs/aioshelly/compare/12.2.0...12.3.0
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
home-assistant:dev
← bieniu:shelly-blu-trv-valve-pos
opened 10:39PM - 09 Jan 25 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR introduces new entities for Shelly BLU TRV:
- `battery` sensor
- `signal strength` sensor
- `valve position` sensor (only if automatic temperature control is disabled for the device)
- `calibration` binary sensor
- `external temperature` number entity
- `valve position` number entity (only if automatic temperature control is enabled for the device)
PR introduces the ability to select an entity class via `entity description`. I added a helper `get_entity_class` to easily select the appropriate class for the entity. In future changes we may migrate more entity descriptions to pass information about the appropriate entity class.
![obraz](https://github.com/user-attachments/assets/61b4d066-9b87-4348-9f18-a4c8765717a5)
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
and Shelly BLU TRV will be supported in HA 2025.2.
4 Likes