Better `DeviceInfo` management

The main idea behind the DeviceInfo was to allow some bridge-like mechanisms. However, there was a bug (see #3).

Now the error should be fixed, and there is a new multiple_devices.py example that showcases how to have an application configure more than one device (which is a common case for bridge-like applications, but not limited to).

Minor fixes on Number

Now Number integration includes

• device_class
• unit_of_measurement

These are optional. The example (see simple_number.py in the folder examples) shows how to add values for those attributes. The Home Assistant documentation shows valid values. Which should match the Home Assistant developers documentation.

Now with Fans for my fans

Hi! I don't have a lot of fans but I have added quite a lot of Fans. This release adds basic support for Fans. So now hopefully some fans with Fans will be able to use their Fans!

(sorry)

User-defined `unique_identifier`

Now the user can specify a unique_identifier, that will be used for generating the unique_id fields of the Things.

By default, the MAC was being used. For certain scenarios where this is not desirable, the Manager can have a user-defined unique_identifier. This is a parameter of the __init__.

Binary Sensor, and an easy personalization mechanism for the device_info

I had not needed Binary Sensor yet, but it was very easy to adapt (it's like a Sensor, but simpler).

Now the device_info is generated during the constructor of the Manager. That means that it can be modified by the main application reliably (if I have not messed up). There is an example of how the manufacturer and the model can be set (see the example for inspiration).

Entities have attributes

I wasn't sure if attributes were really useful, but I finally stumbled upon a certain use case that needs them.

So, from this point forward, all Things (Sensor, Button, Switch... as well as any future ones) have a .attributes write-only property that accepts a dict.

We have SENSORS!

I didn't have a need for MQTT Sensors until now, so the library didn't have them.

Now I have implemented them, in addition to some minor improvements related to the get_config mechanism. Everything seems to be working as intended so far, so let's release v0.5.0 🥳

Changing the build system

I had some issues with the packaging and decided to modernize. From now on, I'll be using hatch.

This release is just to check that all GitHub actions and package publishing keeps working as intended. The final package should remain identical in terms of functionality (crossing fingers!)

First bugfix release!

Version 0.4.0 had some stinky bugs that I overlooked. I discovered them and fixed them. There isn't anything new in this release, but now it works 😅

New components, new config fields mechanism

This release is somewhat partial, as some additional mechanism for configuration fields (such as optimistic or min and max) has been prepared, but the definition is non-exhaustive at the moment (I want to play around before committing to that).

Number and Button things can be instantiated with this library. The README should be updated, but there are examples to compensate.

Hopefully the PyPI release will be cleaner and more descriptive. Otherwise I will need to create a new v0.4.1 release soon 😨

Happy holidays!