Closed cm86 closed 4 years ago
Could you please use the issue template provided when creating an issue? Thanks for updating the issue 👍
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: ''
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:
-
There is nothing to find in the logs
nothing
i hope i offered the needed informations
mfg Chris
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...'
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
Same identical problem, I hope it will be solved, thanks for the support
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
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
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!
Yes I have exactly the same problem.
hello, today i have tried 0.108.2 it's still the same behavior...
It is probably this change: https://github.com/home-assistant/core/pull/33240
Could some of you try with broadlink==0.12.0 ?
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.
@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?
Same problem here, Synology docker environment. And yes short commands works.
It is probably this change: #33240
Could some of you try with broadlink==0.12.0 ?
Work for me with broadlink version 0.12
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...
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'
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
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
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?
yep the workaround works for me too. Thank you
Yes the workaround is working for me also I'm happy
custom component WA works :)
I can confirm that custom component workaround works for me
Could someone test this? https://github.com/mjg59/python-broadlink/issues/338#issuecomment-612805121
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
Also implemented the workaround. Thanks. Seems a fix is not yet include in 0.108.4. Any planned sub-release already ?
Also no fix in 0.108.5
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
I will upgrade the HA code today
Upgraded to .6 but still command_on doesnt work, only command_off...reverting back to workaround
I tried 0.13.1 as well - this did not resolve the issue
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
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 also have found that the 108.6 HA version with broadlink 13.1 has not fixed this issue.
Just pulled the 108.6 docker image, it didn't solve the issue.
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
@roi1010 put the broadlink folder under custom_components
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 put the broadlink folder under custom_components
I did it, nothing happened:
@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
@roi1010 so maybe this is not the solution for your problem. It stopped working since the upgrade to 0.108.X?
@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
I already fixed it here. Now we just need to wait for the next release.
Thanks!
Thanks indeed Waiting for the new release
Just tried the new 108.7 version but still the same. Rolling back to 107.7.
@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.
Does anyone know which version of HA the new broadlink wil be available? I'm running now 0.108.8
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:
So there is nothing in the log (not in home assistant and nothing in the docker logs).
mfg Chris