2022.2: Let's start streamlining!

Blog
675

There’s nothing to agree with… that’s why it’s there. I’m stating the reason. Agree or disagree, this is the reason.

676

Don’t fight the system. Guys it’s ok. I can’t remember anyone asking or having an issue with not having a unknown state. I now have to figure out why my binary sensors return unknown state when in fact they are not…

1 Like
677

Every other domain has it… it was just added to binary_sensor. Like it or not, this has been in home assistant for 8+ years.

678

Is ok. Doesn’t mean I like it since it gives problems I don’t understand.

1 Like
679

But we don’t care about what knowledge the button has.
The button is not running HA, is it?

The button knows, HA doesn’t, so HA tells you it doesn’t know by setting the state of the HA button representing the button to unknown.

Is it really that hard to understand?
You know your age, I don’t.
You know if your kitchen lights are ON or OFF, I don’t.
You know if you currently press the button of your kitchen lights, I don’t and neither HA.

680

The new button entity works fine in lovelace but Google Home responds to “press the blue button” with "Sorry I don’t understand:

 template:
  - button:
    - name: "The Blue Button"
      press:
        - service: nodered.trigger
          entity_id: switch.weatherforecast
681

Well, they may have to be renamed ‘trinary’ sensors eventually, as they now have three states, and not two anymore… :wink:

5 Likes
682

Quaternary. :wink:

  1. on
  2. off
  3. unavailable
  4. unknown
2 Likes
683

Then spend time learning what you don’t understand.

684

They were ternary before. FYI it’s ternary not trinary

685

On things which were not a problem before. You see my point.

1 Like
686

It was based on a lie before.

Without knowledge of the binary_sensor’s actual state, it was being reported as off. Basing decisions on false information isn’t a good strategy (and not only for home automation). Now it correctly reports unknown when it has no knowledge of the device’s state.

1 Like
687

I don’t see your point. Everyone here has had to deal with changes, your cries fall on deaf ears.

688

I know. Thank you!

689

You’re welcome

690

I upgraded to zwavejs 2 MQTT 6.5.0 and everything works just fine. All devices came back and work. I also now can report that the Dome audible alarm can be commanded using scripts and secondary alarm configurations for sound, time, duration (num cycles), and volume all work now! The bug fix worked.

691

Hello everyone, after the latest update of Home Assistant to version 2022, the device tracker related to turning the lights on or off when I enter or leave the house no longer works. It no longer works for me unless the presence of my car in the garage and outside tells me entity not available, for the sake of completeness I used a function of BMW Connected now after the update the device tracker that in previous versions of Home Assistant works with the new 2022 does not work the more it is gray. can you help me to restore this function otherwise I cannot make updates

692

Not sure how to use the media browser now…
I thought i need to select the spotify in the bottom right, and i would be able to select a speaker new to play to…

Or am i wrong.
Cause when i select the spotify, i see the the album covers.
However, when i select a speaker, its empty

(And i also have spotcast installed)

693

Device tracker changed the way it handles devices and only creates a device if it can be tied to a known integration. In your automation, you probably have to use the entity instead of the device.

Example:

trigger:
  - platform: state
    entity_id: device_tracker.your_phone
    from: 'not_home'
    to: 'home'
action:
  - service: light.turn_on
    target:
      entity_id: light.entrance_lights
694

Depends on version number.