Fix xiaomi binary_sensor warning

[Danielhiversen]

Description:

Fix xiaomi binary_sensor warning
@arsaboo

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

[arsaboo]

Also fixes #17408

[amelchio]

This will fire the None in the event. Just checking that this is intended :)

[arsaboo]

Indeed, that is not the intent. Infact, I was wondering why not use something like

        if value in ('vibrate', 'tilt', 'free_fall'):
            self.hass.bus.fire('xiaomi_aqara.movement', {
                'entity_id': self.entity_id,
                'movement_type': value
            })
            self._last_action = value
            return True
        else:
            return False

Since the other events are useless for us anyways.

[Danielhiversen]

Ok, I see.
So None is never a real movement?

[arsaboo]

Yes, None is not a real movement and should be ignored

[shishos]

Yes, None is not a real movement and should be ignored

If the sensor is being used to work in an environment where constant vibration is the desired and "normal" state. Wouldn't one want to know once vibration has paused and the sensor is now sampling no movement - "none"?

[arsaboo]

@shishos The state reverts to off after some time (which is how it works for other binary sensors).

Although, in my testing, the state is always off even though there was some movement.

[arsaboo]

Tested the code and it eliminates the noise in the logs.