v1.0

• Upgraded to .NET 8.0.
• Switched to Managed MQTT Client that automatically reconnects when connections are broken.
• Log declaration of all devices.
• Graceful shutdown when plug-in is stopped. All Easywave devices will be marked as unavailable.
• Add support for Blinds and report their states when opening & closing (based of fixed 10 seconds delay, as Easywave devices do not report their status).

v0.6

Changes in this release

Add automatic reconnect to MQTT server when connection drops.

When the Home Assistant or Mosquito restarts, the add will automatically reconnect when it is back up, instead of needing a restart.

Persist state of switches in MQTT

After reboot of Home Assistant the state of the NIKO switches was lost. State changes are now sent with retain set to True. This will make sure that Home Assistant will get the latest state change message after a restart, causing it to reflect the last state of the lights correctly.

v0.4

• Updated addon configuration to automatically add all serial devices in the addon container, removing the need to alter the dockerfile configuration when your receiver is plugged-in in another port.
• Added configuration options for serial device, mqtt & log level, making it possible to change certain settings & increase logging for debugging purposes without needing to reinstall the addon.
• Switched to SeriLog for logging.
• Added test project to simulate a local Eldat RX09 device. This test project requires on the com0com Null-modem emulator and an MQTT server where the Easywave2Mqtt process is connected to.
• Simplified addon building & faster startup:
  • removed the .tar.gz file and made the addon binaries & config file are directly available in the repo, making it easier for non-developers to alter the configuration and to deploy the addon in Home Assistant.
  • Switched to .NET 7.0 to improve the performance.
  • Configuration options are directly read from data subfolder (if available), removing the need for the startup.sh script to copy it to the correct location.
• Lowered logging level for a few MessagingService messages that were logged twice, but in a different way.

---

I could use some help with the following topics:

1. I'm still struggling to make it possible to do the device configuration directly in Home Assistant. The option & schema configuration in the config.yaml file seems to be too limited for what I need.
2. Since some time, when upgrading Home Assistant, the addon stops responding and needs to be restarted. I've tried to use a managed MQTT client to automatically reconnect to MQTT when that goes down, but that doesn't seem to help.

v0.2

First public release