[BUG]: Camera State (Idle, Streaming, Recording) doesn't update as features are enabled / disabled

[NickM-27]

Steps to reproduce:

1. HA starts with camera recording disabled so state is set to idle.
2. Recording is enabled
3. The camera state remains at idle when it should be recording

@dermotduffy You can assign to me as I intend to fix this, still brainstorming a good way to key in to other entities / state in general to trigger an update since currently the state is only set in init.

[dermotduffy]

Thanks @NickM-27 . Yes, I noticed this in the past also. Sounds good, thanks for taking a look!

[NickM-27]

@dermotduffy do you have any recommendations? Is it possible / good idea to link into the recording switch or use the recording switch updates to trigger updates in other entities?

[dermotduffy]

Two spur-of-moment ideas:

• In the switch code, detect the change and send a HA signal (example) using a dispatcher. Connect/Listen for that signal from the camera.

• Or have the camera subscribe to MQTT separately (I'd first try to have the camera just inherit from FrigateMQTTEntity and see if I can get that to work, or otherwise re-use/abstract some code out and integrate it into the camera, e.g. using async_subscribe_topics by hand).

Whilst the second option may be more duplication (e.g. if you can't get just inheriting from FrigateMQTTEntity to work), I think it's the better option. Otherwise, if you directly link the entity functionality like option 1, the camera state would not longer change when/if the user disables the switch entity (and so that's generally not a recommended path).

[NickM-27]

The second one works implementing FrigateMQTTEntity Also seeing a bug where the mqtt state was coming back in format b'OFF' which is weird. Will fix that in this PR as well

EDIT: Seems to be behaving differently in the camera class for some reason 🤔