core: Broadlink remote.send_command problem
The problem
When I set the switch to send the command it works perfectly.
- platform: broadlink host: 192.168.1.48 mac: ‘34:ea:34:d0:a6:ab’ switches: !include_dir_merge_named /config/Broadlink/
Inside the merge file ‘tv_samsung_key_channelup’: friendly_name: “TV_samsung_KEY_CHANNELUP” command_on: ‘JgBGAJWTEzcTNxM3ExITEhMSExITEhM3EzcTNxMSExITEhMSExITEhM3ExITEhM3ExITEhMSEzcTEhM3EzcTEhM3EzcTNxMABgUNBQ==’
If I use the switch, everything works fine.
The problem is when I try to use the service: remote.send_command When I go to the menu --> “Developer tools” --> “services” service: remote.send_command entity: remote.broadlink_salon_remote Service Data (YAML, optional): entity_id: remote.family_room command: b64:JgBGAJWTEzcTNxM3ExITEhMSExITEhM3EzcTNxMSExITEhMSExITEhM3ExITEhM3ExITEhMSEzcTEhM3EzcTEhM3EzcTNxMABgUNBQ==
When I press the button “CALL SERVICE” it does not send anything (the orange led on Boradlink does not turn on)
The entity “remote.broadlink_salon_remote” is configure with Broadlink integration
Environment
- Home Assistant Core release with the issue: 0.115.6
- Last working Home Assistant Core release (if known):
- Operating environment (OS/Container/Supervised/Core): HassOS 4.13
- Integration causing this issue: Broadlink
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/broadlink/
Problem-relevant configuration.yaml
Menu --> “Developer tools” --> “services” service: remote.send_command entity: remote.broadlink_salon_remote Service Data (YAML, optional): entity_id: remote.family_room command: b64:JgBGAJWTEzcTNxM3ExITEhMSExITEhM3EzcTNxMSExITEhMSExITEhM3ExITEhM3ExITEhMSEzcTEhM3EzcTEhM3EzcTNxMABgUNBQ==
Traceback/Error logs
No logs
Additional information
If I remove this switch, the problem is the same. remote.send_command does not work.
- platform: broadlink host: 192.168.1.48 mac: ‘34:ea:34:d0:a6:ab’ switches: !include_dir_merge_named /config/Broadlink/
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (6 by maintainers)
Now it is working. Thanks for your help. The problem was: “I have to go into the device and turn on the entity switch” Beginner’s mistake. Sorry for the inconvenience. The confusion was due to having the old and new systems active.
Thanks for the reply, and fair enough, my workaround for forcing it always on by checking state change will remain in place then, which is suitable 👍
Here are the logs for both times it happens. Interestingly the first (05/12) it was unavailable -> off, whereas the recent one it was just unavailable.
And the “Daylight savings” event:
Unfortunately I don’t have access to the home-assistant.log for these times as I’ve done a few server restarts.
Anyways, as mentioned I’m currently using a workaround, happy to help test if needed though.
I found that mine stopped working, literally reset the whole integration and still no luck, then I saw this comment and found out that HA had turned the entity to “off”.
Is this standard behavior? First time I experienced it, what would cause it to turn “off”, can we default the value to “always on” somehow?
Please make sure the entity is turned on. You cannot learn or send with the remote turned off.