Skip to content

v1.3.0: Homie topics more configurable and stability improvements
Compare
Choose a tag to compare
@marvinroger marvinroger released this 02 Apr 10:41
v1.3.0
4812138

This is kind of a big one. Thanks to everyone involved.

New features

  • You can now set the base topic used on MQTT if you don't want the default devices/ base topic (#44)
  • You can also set the device ID to be used on the MQTT topic if you don't want the default hardware ID (#45)
  • Breaking change (not in the API so still 1.x.x): The new OTA version string sent to the server is now of the following format: device-id=firmware-name=current-device-version=version-advertised-by-$ota (eg. da828fe0=sub2-relay=1.0.0=1.1.0). This makes it easier to parse server-side (#50)

Fixes

  • A lot of work has been done to improve the stability of the MQTT connection when using SSL. Huge thanks to @jpmens which has been very active at testing, he helped a lot 👍 (#46)

Note: This required a lot of changes in the code, the most notable being most of the dynamic allocations were removed. In other words, there are now hard limits for things like the firmware name (see Limits.hpp and customize it if you need to).

  • SSL/TLS fingerprint verification now works for MQTT (#42)

Note: The way the verification is done is not very secure due to some limitations of PubSubClient. Consider it as more secure than no fingerprint at all, but not bulletproof.

Docs

  • The documentation was moved from the Wiki to the repo. So now, whenever you download a copy of the library, you have an up-to-date documentation for your current Homie library version

Web UI

  • Polyfills are now included in the Web UI, so more web browsers are compatible (#48)
  • The Web UI is updated to reflect the latest changes in the library
  • It is visually cleaner
  • SSL is now configurable from the Web UI
Assets 2
Loading