0.6.1 - Fix default message retain setting for clients to avoid receiving the last message on startup

Small change to how we tell clients to send messages, should prevent weird startup messages from being received. May require clearing your MQTT topics, until a new message is sent on that topic I think.

What's Changed

• fix: Don't tell client to use retain=true for messages. by @W-Floyd in #56

Full Changelog: 0.6.0...0.6.1

0.6.0 - New device updates from upstream, reliability fixes

A good bit of code churn since last release due to upstream device changes. So far the automatic code generation has been keeping up pretty well with minor tweaking to cope with updated docs. Special thanks to @pa-sowa and @dev-foo-bar for work on scripts and @phallows for work on connectivity issues.

I have opted to cross-compile to as many platforms as possible, but almost all of these come with no testing. I did test one of the MIPS builds in the past on my router, and it did work, so YMMV.

New Contributors

• @pa-sowa made their first contribution in #34
• @dev-foo-bar made their first contribution in #37
• @phallows made their first contribution in #54

Full Changelog: 0.5.5...0.6.0

0.5.5

What's Changed

• fix: Correct local command appending that failed when command was only one line by @W-Floyd in #32
• fix: Logging levels in the config actually take effect. by @W-Floyd in #33

Also added new lock config example and script.

Full Changelog: 0.5.4...0.5.5

0.5.4 - Ignore empty command message

Useful for empty payloads that trigger buttons.

Full Changelog: 0.5.3...0.5.4

0.5.3 - Correct `device_tracker` struct

Working around a quirk of the markdown documentation.

Full Changelog: 0.5.2...0.5.3

0.5.2 - Generate UniqueId from Name if not specified

Previously, if unique_id was missing, it would simply fail. Now it is generated from the name given in the config. Added is a simple select example config.

Full Changelog: 0.5.1...0.5.2

0.5.1 - Fix automatic code generation for cameras, device_triggers, and tags

Cameras, device triggers, and tags have a single topic field, which wasn't previously propagated correctly. It is now treated as a state field in all but the final json output.

Full Changelog: 0.5.0...0.5.1

0.5.0 - Add all device types, enable all fields

All device types have been implemented, though not all have been tested yet.

Full Changelog: 0.4.5...0.5.0

Breaking Changes

Config schema is different, check the new sample configs for examples. It should be trivial to adapt.

0.4.5 - Add option to specify minimum and maximum mireds

feat: bump software version for release

0.4.4 - Add flags to allow specifying config and secrets locations

release: Bump version number, update license years.