The following components and platforms could not be set up: broadlink

Configuration
1

What i miss or make wrong? after 1H i give up and ask for help

Invalid config
The following components and platforms could not be set up:

discovery
switch.broadlink

Please check your config

2

Two = signs at the end of the ir code, eg:

command_on: 'JgBGAJKVDzsQ<snip>Og8ADQUAAA=='

3

Or if you have any other switches defined then make switch: to switch 255: or some large number

4

Grrrr!! Yes one more = work!

Do you know why now i get a error about Invalid config
The following components and platforms could not be set up:

discovery ?

i dont now why that start without any of my hand

5

Perhaps you have discovery: in your config file?

6

yes i have, this is not a default on the config ?
why he stop working/./

7

Take it out if you don’t need it, it’s not a default. Personally I’ve only recently started using since I started using RF Link, I’ve always put everything in manually.
Are there any logs as to what’s wrong with discovery?

8

i dont know what is worng now, also automation.yaml stop working

Thisis my log,

https://paste.ofcode.org/wen4MQrx7Wmy2Uvgn7BsYD

9

Well the automation error has been existent for a few weeks now you can’t use state but must use ‘to’ or ‘at’ - check the docs - you can use state in conditions just not triggers. I don’t have clue what’s wrong with xiaomi. If you show the offending automations we can help :slight_smile:

   trigger:
     - platform: state
       entity_id: switch.rfl_freezer_open
       to: 'on'

# instead of state: 'on'

the at: is for time triggers.

10

So i need to change all ?

  • alias: “Back door is open”
    trigger:
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d00010f9c1b
      state: ‘255’
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d00010f9c1b
      state: ‘on’
      action:
      service: notify.xiaomi
      data:
      message: “Back door open”
      target: “device/LGE Nexus 5X”

to like this ? state: ‘on’ = to: ‘on’

  • alias: “Back door is open”
    trigger:
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d00010f9c1b
      state: ‘255’
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d00010f9c1b
      to: ‘on’
      action:
      service: notify.xiaomi
      data:
      message: “Back door open”
      target: “device/LGE Nexus 5X”
11

Are you sure your home assistant instance has a notify service called “xiaomi”?

12

That work for long time, i just add a new broadlink and then the issue start.
i back to my backup and now this stop working…

maby i need service: notify.pushbullet ?

13

How do you receive notifications?

14

to pushbullet

still not working

the command work fine foe long time

  • alias: “Front door is open”
    trigger:
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d000127ae25
      state: ‘255’
    • platform: state
      entity_id: binary_sensor.door_window_sensor_158d000127ae25
      state: ‘on’
      action:
      service: notify.xiaomi
      data:
      message: “Front door open”
      target: “device/LGE Nexus 5X”
15

Just give it a try:

- alias: Front door is open
  trigger:
    - platform: state
      entity_id: binary_sensor.door_window_sensor_158d000127ae25
      from: 'off'
      to: 'on'
  action:
    - service: notify.xiaomi
      data:
        message: "Front door open"
        target: "device/LGE Nexus 5X"
16

Yes!!! Work!
Why did it suddenly change?
PS, Before amazon alexa find all this via “automation” as hue light, now after the new code did not, do you have any idea how to make it on/off with alexa? my this issue with my discovery?

you are the King!!!

17

It was a breaking change from a while ago, you should always read the change logs before upgrading :frowning: