Core: Broadlink out of order since upgrade to 0.108.0

[cm86]

So i have upgraded to 0.108.0 Yesterday and my Broadlink scripts aren't working anymore
So yesterday i have rolled back to 0.107.7
Today i saw that there was 0.108.1 out and thought i try this... (didn't find details about broadlink)
So also with 0.108.1 broadlink is still broken.

I'm running CentOS 8 and Homeassistant in docker...
my docker-compose file is looking like this:
version: '3' services: home-assistant: image: "homeassistant/home-assistant" restart: always container_name: hassio network_mode: host volumes: - "/etc/localtime:/etc/localtime" - "/opt/home-assistant:/config"

So there is nothing in the log (not in home assistant and nothing in the docker logs).

mfg
Chris

[frenck]

Could you please use the issue template provided when creating an issue? Thanks for updating the issue 👍

[cm86]

The problem

Broadlink scripts aren't working anymore

Environment

• Home Assistant Core release with the issue: 0.108.0
• Last working Home Assistant Core release (if known): 0.107.7
• Operating environment (Home Assistant/Supervised/Docker/venv): docker
• Integration causing this issue: broadlink
• Link to integration documentation on our website: https://github.com/home-assistant/core/tree/dev/homeassistant/components/broadlink

Problem-relevant configuration.yaml

- platform: broadlink
    host: XXX.XXX.XXX.XXX
    mac: 'xx:xx:xx:xx'
    timeout: 15
    type: rm2_pro_plus
    switches:
      stern01:
        friendly_name: "Stern01"
        command_on: ''
        command_off: ''
      stern02:
        friendly_name: "Stern02"
        command_on: ''
        command_off: ''
      stern03:
        friendly_name: "Stern03"
        command_on: ''
        command_off: ''

scripts

buero_stop:
  alias: Büro stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
buero_down:
  alias: Büro down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
buero_up:
  alias: Büro up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
all_stop:
  alias: ALL stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
all_down:
  alias: ALL down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
all_up:
  alias: ALL up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
hwr_stop:
  alias: HWR stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
hwr_down:
  alias: HWR down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
hwr_up:
  alias: HWR up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda01_stop:
  alias: Matilda01 stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda01_down:
  alias: Matilda01 down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda01_up:
  alias: Matilda01 up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda02_stop:
  alias: Matilda02 stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda02_down:
  alias: Matilda02 down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
matilda02_up:
  alias: Matilda02 up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
gaestebad_stop:
  alias: Gästebad stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
gaestebad_down:
  alias: Gästebad down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
gaestebad_up:
  alias: Gästebad up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
bad_stop:
  alias: Bad stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
bad_down:
  alias: Bad down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
bad_up:
  alias: Bad up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
schlafzimmer_stop:
  alias: Schalfzimmer stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
schlafzimmer_down:
  alias: Schalfzimmer down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
schlafzimmer_up:
  alias: Schalfzimmer up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube01_stop:
  alias: Stube01 stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube01_down:
  alias: Stube01 down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube01_up:
  alias: Stube01 up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube02_stop:
  alias: Stube02 stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube02_down:
  alias: Stube02 down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stube02_up:
  alias: Stube02 up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
terrasse_stop:
  alias: Terrasse stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
terrasse_down:
  alias: Terrasse down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
terrasse_up:
  alias: Terrasse up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
kueche_stop:
  alias: Küche stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
kueche_down:
  alias: Küche down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
kueche_up:
  alias: Küche up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
phil_stop:
  alias: Phil stop
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
phil_down:
  alias: Phil down
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
phil_up:
  alias: Phil up
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      -
stern01_on:
  alias: Stern01 ON
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stern01_off:
  alias: Stern01 OFF
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stern02_on:
  alias: Stern02 ON
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stern02_off:
  alias: Stern02 OFF
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stern03_on:
  alias: Stern03 ON
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 
stern03_off:
  alias: Stern03 OFF
  sequence:
  - service: broadlink.send
    data:
      host: XXX.XXX.XXX.XXX
      packet:
      - 

Traceback/Error logs

There is nothing to find in the logs

Additional information

nothing

i hope i offered the needed informations

mfg
Chris

[lielle1]

I'll try to give information of my own:
since version 1.108 the broadlink platform not sending most of the configured IR and RF codes. the broadlink device not blink when the command is sent.
the broadlink devices does work in term of showing temperature, switch entities are presented.

version: 1.108.1

last working version: 1.107.7

working environment: HASSIO on pie 4

config:

• platform: broadlink
  host: 192.168.0.115
  mac: ---------------
  type: rm2_pro_plus
  friendly_name: Broadlink_roof
  switches:

  north_shade:
    friendly_name: "North shade"
    command_on: 'sgKEAxgMFwwLGAsYDB very long code...'

https://www.home-assistant.io/integrations/broadlink/

[pniewiadowski]

Same for me. I have noticed the short codes are sent, long doesn't so for example:

This is not sent:
command_on: JgCwBA0PDRANLA0PDRANDw0QDQ8NEAwQDRAMEA0sDQ8NEA0PDRANDw0QDQ8NEA0sDQ8NLA0sDSwNLA0PDRANLA0PDSwNLA0sDSwNEAwsDQAJf3E6DRANLA0PDRANDw0QDBANEAwQDRAMEA0PDRANLA0PDRANDw0QDQ8NEA0PDRANDw0sDRAMEA0QDBANDw0QDQ8NEA0sDQ8NLA0sDSwNLA0QDBANLA0PDSwNLA0sDSwNEA0sDQAJfnE6DRANLA0PDBENDw0QDQ8NEA0PDRAMEA0QDBANLA0QDBAMEQwQDBANEAwQDRANDwwtDRAMEA0QDBAMEQ0PDRAMEA0sDRAMLA0sDSwNLA0QDBAMLQ0QDC0MLA0sDSwNEA0sDQAJfnE7DBAMLQ0QCxEMEQsRDQ8MEQ0PDRAMEA0QDQ8NLA0QDBANEAwQDRAMEAwRDBANEAwsDRANDw0QDBAMEQwQDBEMEA0sDRAMLQsuDCwNLA0QDBANLAwRDC0NLA0sDSwMEAwtDQAJf288DQ8NLAwRDBAMEQwQDRAMEAwRCxENEAsRDBELLQwRDBAMEQwQDRANDw0QDBANEAwtDBAMEQsRDBELEQwRCxENDwwtDRANLA0sDC0NLAwQDRALLQ0QDC0NLA0sDSwNDw0sDQAJf3E3EBAMLA0QDBANEA0PDRANDw0QDQ8NEA0PDRAMLQwQDRALEQ0QDBANDw0QDQ8NEA0sDQ8NEA0PDRAMEA0QDQ8NEAwtDBANLA0sDSwNLA0PDBENLA0PDSwNLA0sDSwNDw0sDQAJf3E6DRAMLQwQDRALEQ0QCxEMEQwQDBAMEQ0PDBENLA0PDRANDwwRDBAMEQwQDRAMEAwtDRALEQ0PDRAMEA0QDBANEAwtDQ8NLA0sDSwNLA0QCxENLA0PDC0NLA0sDSwNEAwtDAAJf3E6DRAMLQ0PDRANDw0QDBAMEQwQDRAMEA0QDBANLA0PDRANEAwQDQ8NEA0PDBENDw0sDBENDwwRDBAMEQsRDRAMEA0sDQ8NLA0sDSwNLA0QDBANLA0QDCwNLA0sDSwNEAwtDQAJfnE7DBANLA0QCxENDwwRDQ8NEAwQDRANDw0QDQ8NLA0QDBANEAwQDRAMEA0QCxENDw0sDRANDw0QDQ8NEA0PDRAMEA0sDRAMLQwsDSwNLA0QDQ8NLA0QDSwNLAwtDCwNEAwtDQAJf3A7DBANLA0QDBANEAwQDBEMEAwRDBANEAsRDBAMLQ0QDQ8MEQ0PDBEMEA0QDBANEAwtDBANEAwQDBEMEA0PDRAMEA0sDRAMLQ0sDC0NLAwQDRALLQ0QDSwNLA0sDSwNDwwtDAAJgG88DQ8MLQ0QDQ8MEQ0PDBEMEAwRDBANEAwQDBEMLA0QDBELEQwQDRANDwwRDBANEA0sDBANEAwQDRAMEA0QDBANEAwsDRAMLQwtDSwNLA0PDRAMLQ0PDC0NLA0sDC0MEA0sDQAJf3E6DRAMLQwQDRAMEA0QCxENDw0QDQ8NEA0PDRANLA0PDRANDwwRDBANEAwQDRAMEA0sDQ8NEAwQDRAMEA0QDQ8NEA0sDQ8MLQ0sDSwNLA0PDRAMLQ0PDSwNLA0sDSwNEAwsDQANBQAAAAAAAAAA

This on is:
command_off: JgDMAHA7DBEMLQwQDBEMEAwRDBAMEQwQDBEMEAwRCxEMLQwRCxEMEAwRDBAMEQwQDBEMEAwtDBEMEAwRDBANEAsRDBELEQwtDBAMLQwtDC0MLQwRDBANLAwRCy0MLQwtDC0MEQwtDQAJfnA8DBAMLQwRCxEMEAwRDBAMEQwQDBEMEAwRDBAMLQwRDBAMEQwQDBELEQwRCxEMEAwtDBEMEAwRDBAMEQwQDBEMEAwtDBEMLAwtDC0MLQwRDQ8MLQwRDSwMLQwtDC0LEQwtDAANBQAAAAAAAAAAAAAAAA==

No info in the log.
I have the Broadlink RM Mini 3

[Macdave78]

Same identical problem, I hope it will be solved, thanks for the support

[canedje]

I do experience the same.
After update to 108 broadlink is not operating the commands anymore.
The length of the commands can be the reason

I also hope this will be fixed in the next update patch
I also have the Broadlink RM Mini 3
HA is running on a Raspberry PI 4+ 4G

[Macdave78]

yes it is the length of the command because with some devices it works and with some it doesn't, the problem is how to shorten the command code

[probot-home-assistant[bot]]

Hey there @danielhiversen, @felipediel, mind taking a look at this issue as its been labeled with a integration (broadlink) you are listed as a codeowner for? Thanks!

[lockyt]

Yes I have exactly the same problem.

[cm86]

hello,
today i have tried 0.108.2
it's still the same behavior...

[Danielhiversen]

It is probably this change: https://github.com/home-assistant/core/pull/33240

Could some of you try with broadlink==0.12.0 ?

[cm86]

ok i'm willing to try this.
But i don't know how i can do this...
I'm running home assistant in docker on centos 8.

[canedje]

@Danielhiversen:
How to test broadlink 0.12.0
Is there a ha code/command in core_ssh to do so, after installing HA 0.108.2?

something like:
ha core update --broadlink=0.12.0

will this work?

[aberesek]

Same problem here,
Synology docker environment.
And yes short commands works.

[lielle1]

It is probably this change: #33240

Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

[cm86]

It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

So how did downgrade broadlink to version 0.12.0?!
When nobody is offering here the way to do this, nobody can test and verify this...
So but i tried a bit but nothing is working...

[boggiano]

Here same problem :
This works:

      barra_audio_sala_volume:
        friendly_name: Barra Sala Volume
        command_on: 'JgDwAJWREg8SDxEQEQ8SLxIwEg4SEBEvEy8SLxMvEg8SDxEQEQ8SjxQPEg8REBEPEi8SMBIvEg8SLxIwEi8SDxIPEg8REBEvEw4SEBEPEi8SAAcOlZATDxIPEg8REBEvEy0UDxIOEjASLxIwEi8SDxIPEg8REBGREg8SDxIPERARLxMvEi8TDhIwEi8SLxMOEg8SDxIPETASDxIPERARLxIABw+VjxQOEhARDxIPETASLxIPEg8SLxIwEi0ULxMOEg8SDxIPEZETDhIPEg8SDxEwEi8SMBIOEy8SLxIwEg4TDxEQEQ8SLxIPEg8SDxEwEgANBQAAAAAAAAAA'

but this doesn't work:

      barra_audio_sala:
        friendly_name: Barra Audio Sala
        command_on: 'JgDQApGVEBAQERARDxIPMhAyDxEQEQ8yEDIQMRAyEBAQERAREBEPlA8REBEPEhARDxEPEg8SEBEPMhAxDzMQEQ8yEDEPMxAxEBEQERAQEDIQAAcQkpQREBEPERAREBEwEjAREBAQETERMBExEDEQEREPERAREBGSEBEQEBAREBEREA8REBEQERAxEDIPMhAREDEQMhAxEDEQERAREBEPMhAABxCSlBAREBEPERAREDEQMhARDxEQMhAxEDIPMhAREBAQERAREJMQERARDxEQERAREBAQERAREDEQMhAxEBEQMRAyEDEQMg8REBEQERAxEAAHEJKUEBEQEQ8REBEQMg8yEBEQEBAyEDEQMhAxEBEQEQ8REBEQkxAREBEPERAREBEQEBAREBEQMRAyEDEQERAxEDIQMRAyDxEQERAREDEQAAcRkZQQERAREBAQERAyDzIQERAQEDIQMRAyEDEQERARDxEQERCTEBEQEQ8REBEQERARDxEQERAxETEQMRAREDEQMhAxEDIQEBAREBEQMRAABxGRlBEQERARDxEQETEPMhAREQ8RMRAxEDIQMRARERARDxEQEZIQERAREQ8REBARERAQEBEQEDEQMhEwEBERMBExETARMRAQERAREBIvEQAHEJGUERAREBEQEBARMREwEg8QERAxETARMREwERAREBEPEBESkREQERARDxEQERAREA8RDxIRMBExETAREBEwETERMBExERAQEBEQDzIRAAcQkpMQERAREBEPERAyDzIQERARDzIQMRAyEDEQERAREBAQERCTEBEPEhARDxEPEhARDxEQEQ8zDzIQMRAREDIPMg8yEDIQEQ8REBEQMRAABxGSlA8REBEQEQ8REDIQMRAREA4SMhAyDzIQMRAREBEPEg8RD5QQERAPEhEPERARDxIPERAREDIPMhAxEBEQMg8yEDEQMhAREBAPEhAyDwANBQAAAAAAAAAA'
        command_off: 'JgDQApGVEBAQERARDxIPMhAyDxEQEQ8yEDIQMRAyEBAQERAREBEPlA8REBEPEhARDxEPEg8SEBEPMhAxDzMQEQ8yEDEPMxAxEBEQERAQEDIQAAcQkpQREBEPERAREBEwEjAREBAQETERMBExEDEQEREPERAREBGSEBEQEBAREBEREA8REBEQERAxEDIPMhAREDEQMhAxEDEQERAREBEPMhAABxCSlBAREBEPERAREDEQMhARDxEQMhAxEDIPMhAREBAQERAREJMQERARDxEQERAREBAQERAREDEQMhAxEBEQMRAyEDEQMg8REBEQERAxEAAHEJKUEBEQEQ8REBEQMg8yEBEQEBAyEDEQMhAxEBEQEQ8REBEQkxAREBEPERAREBEQEBAREBEQMRAyEDEQERAxEDIQMRAyDxEQERAREDEQAAcRkZQQERAREBAQERAyDzIQERAQEDIQMRAyEDEQERARDxEQERCTEBEQEQ8REBEQERARDxEQERAxETEQMRAREDEQMhAxEDIQEBAREBEQMRAABxGRlBEQERARDxEQETEPMhAREQ8RMRAxEDIQMRARERARDxEQEZIQERAREQ8REBARERAQEBEQEDEQMhEwEBERMBExETARMRAQERAREBIvEQAHEJGUERAREBEQEBARMREwEg8QERAxETARMREwERAREBEPEBESkREQERARDxEQERAREA8RDxIRMBExETAREBEwETERMBExERAQEBEQDzIRAAcQkpMQERAREBEPERAyDzIQERARDzIQMRAyEDEQERAREBAQERCTEBEPEhARDxEPEhARDxEQEQ8zDzIQMRAREDIPMg8yEDIQEQ8REBEQMRAABxGSlA8REBEQEQ8REDIQMRAREA4SMhAyDzIQMRAREBEPEg8RD5QQERAPEhEPERARDxIPERAREDIPMhAxEBEQMg8yEDEQMhAREBAPEhAyDwANBQAAAAAAAAAA'

[lielle1]

It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

So how did downgrade broadlink to version 0.12.0?!
When nobody is offering here the way to do this, nobody can test and verify this...
So but i tried a bit but nothing is working...

Several ways to to do this, I think the easiest is:
Go to https://github.com/home-assistant/core/tree/0.107.7 clone or download.
Extract the broadlink folder from components
Put broadlink folder under custom_components folder.
Restart HA

[cm86]

It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

So how did downgrade broadlink to version 0.12.0?!
When nobody is offering here the way to do this, nobody can test and verify this...
So but i tried a bit but nothing is working...

Several ways to to do this, I think the easiest is:
Go to https://github.com/home-assistant/core/tree/0.107.7 clone or download.
Extract the broadlink folder from components
Put broadlink folder under custom_components folder.
Restart HA

--> So ok. that worked for me too.
thanks for the short explanation @lielle1

[pniewiadowski]

It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

So how did downgrade broadlink to version 0.12.0?!
When nobody is offering here the way to do this, nobody can test and verify this...
So but i tried a bit but nothing is working...

Several ways to to do this, I think the easiest is:
Go to https://github.com/home-assistant/core/tree/0.107.7 clone or download.
Extract the broadlink folder from components
Put broadlink folder under custom_components folder.
Restart HA

once the fix will be deployed to prod release, do we have to remove the broadlink form custom_component and it should work back again?

[aberesek]

yep the workaround works for me too.
Thank you

[canedje]

Yes the workaround is working for me also
I'm happy

[pkishino]

custom component WA works :)

[Nodinodi]

I can confirm that custom component workaround works for me

[Danielhiversen]

Could someone test this?
https://github.com/mjg59/python-broadlink/issues/338#issuecomment-612805121

[ElvisJaime]

It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?

Work for me with broadlink version 0.12

So how did downgrade broadlink to version 0.12.0?!
When nobody is offering here the way to do this, nobody can test and verify this...
So but i tried a bit but nothing is working...

Several ways to to do this, I think the easiest is:
Go to https://github.com/home-assistant/core/tree/0.107.7 clone or download.
Extract the broadlink folder from components
Put broadlink folder under custom_components folder.
Restart HA

WORKSSSS GREAT !!!! Many many thanks

[littlbee]

Also implemented the workaround. Thanks.
Seems a fix is not yet include in 0.108.4. Any planned sub-release already ?

[canedje]

Also no fix in 0.108.5

[Amir974]

According to https://github.com/mjg59/python-broadlink/issues/338#issuecomment-612805121
Was the fix done on the dependency library and should resolve the issue with no further change in HA code? @Danielhiversen

[Danielhiversen]

I will upgrade the HA code today

[pkishino]

Upgraded to .6 but still command_on doesnt work, only command_off...reverting back to workaround

[lielle1]

34290 not fix the issue. same problem.

[Zamunda4Eva]

I tried 0.13.1 as well - this did not resolve the issue

[roi1010]

The problem is not solved, why did you close the issue?
I was trying to figure out Daniel's solution to add Broadlink as "custom_components" But I couldn't do it, if anyone has a link to explain how to do it step by step it will help me a lot

[pkishino]

The problem is not solved, why did you close the issue?
I was trying to figure out Daniel's solution to add Broadlink as "custom_components" But I couldn't do it, if anyone has a link to explain how to do it step by step it will help me a lot

Look at @ElvisJaime ’s post, step by step how to add custom component

[David0669]

I also have found that the 108.6 HA version with broadlink 13.1 has not fixed this issue.

[jooka1978]

Just pulled the 108.6 docker image, it didn't solve the issue.

[CarpeDiemRo]

I have 2 broadlink RM Pro. One RM2 PRO and an RM4 Pro. RM2 works perfectly just from the first moment when I used it. After I upgraded HA to the latest version 0.108.6, I am not able to integrate RM4 Pro.
These are my settings from configuration.yaml

for the switch

  - platform: broadlink
    host: 192.168.1.166
    mac: 24:DF:A7:B9:C6:81
    type: rm4_pro

for the sensor

  - platform: broadlink
    host: 192.168.1.166
    mac: 24:DF:A7:B9:C6:81
    type: rm4_pro
    monitored_conditions:
      - 'temperature'
      - 'humidity'

Each time when I press Check Config button I receive the following message:

Blockquote
Invalid config for [sensor.broadlink]: [type] is an invalid option for [sensor.broadlink]. Check: sensor.broadlink->type. (See ?, line ?).
Invalid config for [switch.broadlink]: value is not allowed for dictionary value @ data['type']. Got 'rm4_pro'. (See ?, line ?).

Can you help me please with some advises? I want to mention that RM4 PRO is already Registered in the Broadlink app and has a fix IP.

[Later Edit]
I comment out type line from both blocks of code and I didn't receive any error when I check the configuration. After reboot, the switch is not available and the sensors return the following state

[pniewiadowski]

@roi1010 put the broadlink folder under custom_components

[roi1010]

The problem is not solved, why did you close the issue?
I was trying to figure out Daniel's solution to add Broadlink as "custom_components" But I couldn't do it, if anyone has a link to explain how to do it step by step it will help me a lot

Look at @ElvisJaime ’s post, step by step how to add custom component

I couldn't find an explanation for this user.
Can you give me a link?
That's what I've done so far:

I opened a folder in the "custom_components" called "Broadlink"
I put all the files in Daniel in the folder (after displaying them in Raw ׂ
I restarted the server
Should I add something in the configuration code?
this my code This is the code that worked for me until I upgraded to 0.108.0:

config:

switch:

• platform: broadlink
  host: 10.0.1.14
  mac: 'B4:43:0D:9B:E1:17'
  timeout: 15
  switches:

  tv_hisense:
  friendly_name: "טלויזיה בסלון"
  command_on: 'JgBoAAABJpMSEhITEhMRExITEhMRExITETgSOBI3ETgSOBI3EhMSNxI3EhMROBI4ERMSExEUERMRFBE4ERQRFBE4ETgSOBE4EgAFQwABJUsRAAxDAAEmShEADEQAASZKEQAMQwABJUsSAA0F'
  command_off: 'JgBoAAABJpMSEhITEhMRExITEhMRExITETgSOBI3ETgSOBI3EhMSNxI3EhMROBI4ERMSExEUERMRFBE4ERQRFBE4ETgSOBE4EgAFQwABJUsRAAxDAAEmShEADEQAASZKEQAMQwABJUsSAA0F'

[roi1010]

@roi1010 put the broadlink folder under custom_components

I did it, nothing happened:

[roi1010]

@roi1010 put the broadlink folder under custom_components

I did it, nothing happened:

It is important to note that only RF switches do not work, all other IR workers will work properly

[pniewiadowski]

@roi1010 so maybe this is not the solution for your problem. It stopped working since the upgrade to 0.108.X?

[roi1010]

@roi1010 so maybe this is not the solution for your problem. It stopped working since the upgrade to 0.108.X?

After updating to 0.108.3 my Broadlink RF switches stopped functioning

[felipediel]

I already fixed it here. Now we just need to wait for the next release.

[jooka1978]

Thanks!

[canedje]

Thanks indeed
Waiting for the new release

[jooka1978]

Just tried the new 108.7 version but still the same. Rolling back to 107.7.

[felipediel]

@jooka1978 It's already merged into dev. You can update the files at /usr/src/homeassistant/homeassistant/components/broadlink/ if you don't want to wait.

[canedje]

Does anyone know which version of HA the new broadlink wil be available?
I'm running now 0.108.8

[felipediel]

@canedje 0.109 probably.

[canedje]

Thanks for the answer

[CarpeDiemRo]

I made the update to 108.9 and, unfortunately the issue is reproducible. Can you verify at your system, too. Maybe the fix was not merged in this release.

[pkishino]

If you check the release notes you would see that it’s not added to release
yet

On Sat, Apr 25, 2020 at 18:31 Cătălin Tibori [e-mail]
wrote:

I made the update to 108.9 and, unfortunately the issue is reproducible.
Can you verify at your system, too. Maybe the fix was not merged in this
release.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/core/issues/33879#issuecomment-619350448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7OFYWTAJRCDHBR2WOVAIDROKUVRANCNFSM4MESSYWA
.

[renatothome]

@felipediel Just tested version 108.9 and the issue persists with RF packets. (longer packets). It was supposed to be fixed on this version or there will be another version to fix this issue?

[pniewiadowski]

@renatothome read the comments above to see the answer.

[renatothome]

Thank you for this reply. Helped a lot!

Em seg, 27 de abr de 2020 16:21, pniewiadowski [e-mail]
escreveu:

@renatothome https://github.com/renatothome read the comments above to
see the answer.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/core/issues/33879#issuecomment-620182287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMSGHW7UXXAHEASDRYO5B5DROXLKTANCNFSM4MESSYWA
.

[i00]

Mine worked fine all through 107.X > 108.X ... then died when i went from 108.X > 109.0

[darylsargent]

@felipediel I am not sure if this is related, if not let me know and I will create a new ticket.

I have 2 devices RM_Mini and RM4_mini, contolling identical air conditioners.

broadlink.send works for RM_Mini but not RM4_Mini, for identical packet:

JgAGAWk0Dw0ODg0pDQ4NKQ0ODQ4NDg0pDSkNDg0ODQ4NKQ0pDQ4NDg0ODQ4NDg4NDg0ODQ4NDg0ODg0ODQ4NKQ0ODQ4NDg0ODQ4NDg4NDigODQ4NDg0ODQ4oDigOKA4oDigOKA4oDigNDg4NDigODQ4NDg0ODQ4oDg0ODQ4ODSkNKA4NDg4NKQ0ODSkNDg0ODSkNKQ0ODSkNDg0ODQ4NDg0ODQ4NDg4oDQ4ODQ4NDg0ODQ4NDg4NDg0ODQ4NKQ0pDQ4NDg0ODQ4NDg0pDQ4NDg4NDg0ODQ4NDg0OKA4ODSgOKA4NDg4NKQ0ODQ4NDg0ODSkNDg0ODSkNKQ0pDQ4NKQ0pDSkNKQ0ADQU=

Let me know if you want more info or to open another ticket

[nyokinyoki]

I'm having issues with my RM Mini 3 as well, but I don't know when this was broken, since I've only tried with HA 1.108.6 and later. I'm currently running 1.109.1 with the following configuration in my configuration.yaml:

# Broadlink RM Mini 3 Kitchen
switch:
  - platform: broadlink
    host: 192.168.1.11
    mac: 'c8:f7:42:xx:xx:xx'
    type: 'rm_mini'
    timeout: 160
    retry: 5

I'm getting the following warnings and errors in log:

Log Details (WARNING)
Logger: homeassistant.components.switch
Source: __main__.py:347
Integration: Switch (documentation, issues)
Setup of switch platform broadlink is taking over 10 seconds.

followed by:

Log Details (ERROR)
Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:138
Integration: Switch (documentation, issues)
Setup of platform broadlink is taking longer than 60 seconds. Startup will proceed without waiting any longer.

and finally:

Log Details (ERROR)
Logger: homeassistant.components.broadlink.switch
Source: components/broadlink/switch.py:144
Integration: broadlink (documentation, issues)
Failed to connect to device

I double checked my IP and MAC addresses, they are correct. Firmware version of my RM Mini 3 reports as version 44057 in ihc Android app.

[canedje]

Mine rm3 mini is now up and running again after update to 0.109.1.
@nyokinyoki : your sure your broadlink still connected to WiFi.?
Mine configuratie is not having: type, timeout and retry.
I also have no quotes around my mac

[felipediel]

@darylsargent @nyokinyoki You need to disable the cloud and specify the correct device type in the configuration file. These things have already been tested and are working. See the troubleshooting section of the documentation.

[canedje]

@felipediel: Mine is running without type, but what is the different between Redbean and newblackbean?

[pkishino]

I’m having a different issue, might have to do with some caching? I was using the custom component WA, which still works fine if I keep the CC. But if I remove it o get the following error for remote and switch:AttributeError: module 'broadlink' has no attribute 'rm'
Rm3 _mini ..I tried specifying the type as rm_mini , never had it before, still same..

[felipediel]

@canedje The color :smile: If yours is running fine without the type, you don't need to specify it. This is only for new models.

@pkishino There is a wrong file in the place where your library was supposed to be. I have no idea where this error came from, but you can follow these instructions to solve it.

[darylsargent]

@felipediel Perhaps I should have added - remote.learn and remote.send work fine, the packet then used for the broadlink.send test was extracted from the learned .json file.

The addin I am using is smartIR - which uses broadlink.send to send from a library of commands.

So to summarise, remote.send works, and broadlink.send doesn't work, for the same device.

[felipediel]

@darylsargent Did you specify the type in the switch config?

[darylsargent]

@darylsargent Did you specify the type in the switch config?

  - platform: broadlink
    host: 192.168.0.171
    mac: '24:df:a7:34:95:6d'
    type: rm4_mini
    name: "Sunroom IR"

[darylsargent]

@felipediel this is the output for that device from debug.py:

`
17:02:57,694 __main__ DEBUG [Device 2]
17:02:57,695 __main__ DEBUG Host: ('192.168.0.171', 80)
17:02:57,695 __main__ DEBUG Mac: 6d9534a7df24
17:02:57,695 __main__ DEBUG Type: 0x51da

17:02:57,695 __main__ DEBUG Starting authentication...

17:02:57,695 __main__ DEBUG [Request]
bytearray(b'Z\xa5\xaaUZ\xa5\xaaU\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x87\xf7\x00\x00\xdaQe\x00GMm\x954\xa7\xdf$\x00\x00\x00\x00\xa1\xc3\x00\x00E4R\xe7\xf9.\xda\x95\x83D\x93\x085\xef\x9am\xfbi-\xc3p\xb9\x04C\xac\\xd6?\xbbS\xad\xfa\x08\x81L\xa7\xf8\xcfAq\x002\x8eW\x0c;\x86\xc9M\x05p\x84I\xa3\x89\xe2\x9a\xe1\x04T6\xa0[\xdd\xdc\x02\xc1a\xaf\x13%\xe8~\x19\xb0\xf7\xd1\xce\x06\x8d\xe5\x1ba\x91V\x87m3\x8c\xff;\x99\x1e@\xcd\xb1')

17:02:57,733 __main__ DEBUG [Response]
(b'Z\xa5\xaaUZ\xa5\xaaU\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00*\xd7\x00\x00\xdaQ\xe9\x03GMm\x954\xa7\xdf$\x00\x00\x00\x00\x01\xc5\x00\x00\x964N\x83\xf7\x18\xd3\x82i\xbc\x90?\xbb\xd0\x0c\x06\x11$U\x0c\xa1\xfe\x87?\xc03\xbby8z\xa2(', ('192.168.0.171', 80))

17:02:57,734 __main__ DEBUG Authentication successful.
`

[felipediel]

@darylsargent This is the remote config. You need to specify the type in the switch config as well.

[darylsargent]

@felipediel Ah! A light turns on! (in my brain)... Thanks - that will be what it is I am sure. Sorry for wasting your time I should have worked that out, and thanks for your help.

[pkishino]

@felipediel I tried that, several times both with your files and the ones from 109.1 tag repo..rebooted etc..still same error
keeping the custom_component for now as it works fine...

[jooka1978]

Just to give a feedback, my RM Pro works fine again. Thanks for fixing it!

[felipediel]

@jooka1978 @darylsargent Thanks for the feedback!

@pkishino You said that you are getting an AttributeError: module 'broadlink' has no attribute 'rm'. But the library has this attribute. So your system is not loading the library correctly.

Some checks:
pip show broadlink must return 0.13.2.
pip show cryptography must return 2.9.
The folder /usr/local/lib/python3.7/site-packages/broadlink must have this file.

[pkishino]

results:

Name: broadlink
Version: 0.13.2
Summary: Python API for controlling Broadlink IR controllers
Home-page: http://github.com/mjg59/python-broadlink
Author: Matthew Garrett
Author-email: [email protected]
License: UNKNOWN
Location: /usr/local/lib/python3.7/site-packages
Requires: cryptography
Required-by:

$ pip3 show cryptography
Name: cryptography
Version: 2.9
Summary: cryptography is a package which provides cryptographic recipes and primitives to Python developers.
Home-page: https://github.com/pyca/cryptography
Author: The cryptography developers
Author-email: [email protected]
License: BSD or Apache License, Version 2.0
Location: /usr/local/lib/python3.7/site-packages
Requires: six, cffi
Required-by: python-miio, pyOpenSSL, josepy, homeassistant, certbot, broadlink, asyncssh, acme

file checked, I can see the rm attribute, but don't get why it's not loading properly... running core install on macos

just tried loading the 190.1 broadlink as a custom_component and it throws the same error...

[nyokinyoki]

@darylsargent @nyokinyoki You need to disable the cloud and specify the correct device type in the configuration file. These things have already been tested and are working. See the troubleshooting section of the documentation.

Hey, thank you. You are right, after doing a factory reset, deleting the "new" ihc application, installing the old "e-Control" app to add it to my network with skipping the cloud prompt, I got my RM Mini 3 to connect to HA.

[felipediel]

@nyokinyoki Thanks for the feedback!

@pkishino
pip show six must return 1.14.0
pip show cffi must return 1.14.0
pip show pycparser must return 2.20

[pkishino]

@nyokinyoki Thanks for the feedback!

@pkishino
pip show six must return 1.14.0
pip show cffi must return 1.14.0
pip show pycparser must return 2.20

Ok, thanks, manually upgraded these three, they were on 1.11.0 1.11.5 2.18..
But still getting same error :( very very strange, running high Sierra on a Mac mini 2011 and so far always stable .. the old broadlink works fine ... just tried upgrading to .2 but still same problem.. custom old broadlink is ok, packaged one or custom updated same error.. something is dirty somewhere :(

[felipediel]

@pkishino Strange. I cannot reproduce this error here. Did you try a clean installation and a minimal configuration file?

You can also try to remove all the custom components. If it solves, then you add one by one to see which one is causing problems.

[pkishino]

@pkishino Strange. I cannot reproduce this error here. Have you tried with a clean installation and a minimal configuration file?

You can also try to remove all the custom components. If it solves, then you add one by one to see which one is causing problems.

Hello, after a lot of faffing around (reset, reinstall, copy config etc etc) somehow it is working. Thanks for the help

[roi1010]

Also in version 0.109.3 it still doesn't work, I'm discouraged

[Zamunda4Eva]

@pkishino Strange. I cannot reproduce this error here. Have you tried with a clean installation and a minimal configuration file?

You can also try to remove all the custom components. If it solves, then you add one by one to see which one is causing problems.

@felipediel I'm running into the same issue as @pkishino.
AttributeError: module 'broadlink' has no attribute 'rm'

I have already reset the device and connected to WiFi per previous instructions. Also, the files look correct based on what you've directed to @pkishino I verified the correct versions of broadlink (0.13.2) and cryptography (2.9). I also verified the /usr/local/lib/python3.7/site-packages/broadlink/__init__.py shows the correct attributes. I'm kind of stuck unless I implement the custom component workaround.

[Zamunda4Eva]

@pkishino Strange. I cannot reproduce this error here. Have you tried with a clean installation and a minimal configuration file?
You can also try to remove all the custom components. If it solves, then you add one by one to see which one is causing problems.

@felipediel I'm running into the same issue as @pkishino.
AttributeError: module 'broadlink' has no attribute 'rm'

I have already reset the device and connected to WiFi per previous instructions. Also, the files look correct based on what you've directed to @pkishino I verified the correct versions of broadlink (0.13.2) and cryptography (2.9). I also verified the /usr/local/lib/python3.7/site-packages/broadlink/init.py shows the correct attributes. I'm kind of stuck unless I implement the custom component workaround.

Well, that's odd. I got it to work. Previously, I had moved the broadlink CC outside of the custom_components directory to the root of my /config folder and still experienced the issue. However, deleting the broadlink folder entirely, then restarting HA seems to be the correct method as it is now working for me!

[felipediel]

@roi1010 Could you confirm if this works for you? :point_up:

@pkishino @Zamunda4Eva Thanks for the feedback!

[roi1010]

I tried now, I deleted the Broadlink folder in the custom components.
I restart the HA server
And now it works fine !!! Thank you!!

[felipediel]

@roi1010 Great! Thanks for the feedback!

[felipediel]

Fixed in https://github.com/home-assistant/core/pull/34488.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.