Similar to how homebridge has its serial number set to its MAC address

This will allow a couple of things:

• Code simplification
• Setting serial number as mac address

While the device can auto reconnect, that does not prevent the plugin from attempting to send new signals to the device. Ping the device every so often to check if it is connected. If it is not, prevent the states from updating, or possibly even set them to error characteristic values.

broadlinkjs-rm has functions to get these values given the right hardware is used. Include an option to enable this, disabled by default.

Split up methods to make this cleaner:

async initState // load the states from persist or defaults. Called in the constructor.

async initBroadLink // connect to the BroadLink device and update the value of device after it has been found. Device initially set to null.

async startKeepAlive // start a loop to keep pinging the rm every so often. A failed ping will call initBroadLink. Called in the constructor.

async startStateUpdates // current loop function. Check if device is not null first. Called within the constructor

Hey,

https://github.com/jeremynoesen/homebridge-dyson-bp01/blob/main/img/Demo.gif is like a 50mb file, would it be possible to upload this elsewhere so cloning this doesn't take a massive amount of time?

Issues arise when trying to turn on the machine then immediately do anything else. Either increase the default interval to 400, or figure out a new way to add a minimum delay after each signal.

hello, thank you for the plug in. i have a homebridge installed in the container, homebridge rm pro and dyson plug ins are working but i could not manage to run this plug in. in the logs it says [Dyson Pure Cool Me] Not connected to BroadLink RM. i think i should somehow make Broadlink and this plug in talk but how?
Thank you.

Power states will need to be numbers instead of booleans.

This reduces extra code and follows the spec defined for fanv2.

Move the local variables back to instance variables