-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding multiple Shelly BLU TRVs to single Shelly Gateway GEN3 #498
Comments
Please fill up the form. I'm not able to help you without any information. |
Describe the bug If there are more than 1 TRVs on the same GW Gen3, none of them are showing up in HA. Expected behavior Versions:
Shellies Discovery GEN2 automations: - id: shellies_announce_gen2
alias: "Shellies Announce Gen2"
triggers:
- platform: homeassistant
event: start
variables:
get_config_payload: "{{ {'id': 1, 'src': 'shellies_discovery', 'method': 'Shelly.GetConfig'} | to_json }}"
get_components_payload: "{{ {'id': 1, 'src': 'shellies_discovery', 'method':'Shelly.GetComponents'} | to_json }}"
device_ids: # enter the list of device IDs (MQTT prefixes) here
- LR-GW3
- KTCN-GW3
- BR-GW3
actions:
- repeat:
for_each: "{{ device_ids }}"
sequence:
- action: mqtt.publish
data:
topic: "{{ repeat.item }}/rpc"
payload: "{{ get_config_payload }}"
- service: mqtt.publish
data:
topic: "{{ repeat.item }}/rpc"
payload: "{{ get_components_payload }}"
- id: shellies_discovery_gen2
alias: "Shellies Discovery Gen2"
mode: queued
max: 999
triggers:
- platform: mqtt
topic: shellies_discovery/rpc
actions:
- action: python_script.shellies_discovery_gen2
data:
id: "{{ trigger.payload_json.src }}"
device_config: "{{ trigger.payload_json.result }}"
- condition: template
value_template: "{{ 'mqtt' in trigger.payload_json.result }}"
- service: mqtt.publish
data:
topic: "{{ trigger.payload_json.result.mqtt.topic_prefix }}/command"
payload: "status_update" |
Debug log? |
Nothing in the log related to LR-GW3. |
home-assistant_2024-10-23T19-19-14.157Z.log |
The response to |
so i guess the workaround until\if Shelly will fix this in their FW is to have 1 TRV per GW, which is nonsense in case there is good coverage of the GW, as it is in my case. @bieniu many thanks for your quick and excellent support!! |
Unfortunately Shelly won't change the approach. Maybe I can find a workaround. At the moment the only solution is to use one gateway per one TRV. |
Hi all, multiple BLU H&T are also not working with a single GW, so I guess it is the same issue as it is with the 1TRV |
Life is too short for guessing, show me the log and I'll answer you |
Hi Maciej, ja, you´re right! If you want to bring this forward, you need support! Attached you can find the log. Once the second device is attached to the Shelly device, the first BLU H&T (in my case wk) is also not working anymore in Homassistant. Both BLU H&T (wk and ha) deliver data, as you can see in the screenshot from the mqtt explorer. home-assistant_2024-10-30T07-20-02.456Z.log If you need more details, pls. let me know! |
@Spartacus68 Sorry, I commented too quickly. This is actually the same problem. Pagination of response for Shelly.GetComponents. But I can see that
|
The frequency of data updates has nothing to do with Shellies Discovery. If the MQTT device configuration is correct, then Shellies Discovery has completed its work successfully. The rest is on the Shelly devices side.
Show me the log. |
Hi Maciej, please believe me! HomeAssitant receives no data from the BLU H&T devices if more than one BLU H&T is configured on the shelly. I checked this by pressing the button on the BLU H&T. In the mqtt Explorer, I can see, that the data are sent out when I press the button on the BLU H&T. But in HA still the outdoated data are avaulable. HA does not receive it. If I remove all BLU H&T from the shelly and if I reconfigure only one BLU H&T on the shelly device, HA receives the data. |
I believe you but I will repeat it once again Shellies Discovery has nothing to do with data transfer between the device and HA. The device itself, BLU gateway, MQTT broker and MQTT integration are responsible for this. The log shows the correct device configuration that matches what is in your MQTT broker so from my point of view the script works. This issue concerns the inability to configure more than one BLU device for one gateway and let's stay on this topic. Discussing other issues here is pointless. |
Could someone with multiple BLU TRV paired with one gateway show me the response to:
|
Hi,
|
Could you also show me the output for:
|
|
Please test new # automations.yaml file
- id: shellies_announce_gen2
alias: "Shellies Announce Gen2"
triggers:
- platform: homeassistant
event: start
variables:
get_config_payload: "{{ {'id': 1, 'src': 'shellies_discovery', 'method': 'Shelly.GetConfig'} | to_json }}"
get_components_payload: "{{ {'id': 1, 'src': 'shellies_discovery', 'method':'Shelly.GetComponents', 'params': {'include': ['config']}} | to_json }}"
device_ids: # enter the list of device IDs (MQTT prefixes) here
- shellyplus2pm-485519a1ff8c
- custom-prefix/shelly-kitchen
actions:
- repeat:
for_each: "{{ device_ids }}"
sequence:
- action: mqtt.publish
data:
topic: "{{ repeat.item }}/rpc"
payload: "{{ get_config_payload }}"
- service: mqtt.publish
data:
topic: "{{ repeat.item }}/rpc"
payload: "{{ get_components_payload }}" |
Debug log please. |
Fixed in 3.5.2. |
thank you very much for your support! I am looking forward to download the new version. |
I've added a GW3 to my setup with 2 BLU TRVs connected to it. I see the GW added in MQTT, but the TRVs are not showing up.
Here is my config:
All GWs have the same configuration.
The text was updated successfully, but these errors were encountered: