Skip to content

Releases: thevoltagesource/eagle-mqtt-bridge

EAGLE-200 Support / Code improvements / Security fixes

11 Feb 20:42
d938913
Compare
Choose a tag to compare

Thanks to @normanr, the bridge now parses messages from EAGLE-200 devices. v2.0.0 for model 200! He also rewrote the the timeout logic to more accurately track the state of the Eagle and remove duplicate availability messages. There were other minor changes to clean up code, and some dependancies were updated for security reasons.

Add Home Assistant Discovery

26 Jul 21:20
Compare
Choose a tag to compare

By setting the environment variable HA_DISCOVERY="true", the bridge will publish Home Assistant discovery messages to the default HA discovery topic. With this enabled, two devices will be created under the MQTT integration. Eagle to MQTT Bridge with an entity to report the status of the bridge, and Rainforest Eagle with entities for each of the currently supported messages.

Fix pricing data / Handle negative demand (net metering) / RPi 4 Fix

06 Sep 19:02
Compare
Choose a tag to compare

I have downgraded the base image to use Alpine 3.12 instead of Alpine 3.13 that Node uses by default for v16. Alpine made changes in 3.13 that breaks compatibility with Raspbian on Pi 4s and some Pi 3s. There are workarounds available but for now I will just stick with 3.12.

New features (thanks to the contribution of others!):

  • Handle negative demand - Meter shows negative demand when local generation (solar) is providing power back to the utility provider.
  • Price data is now properly adjusted by the multiplier to show the correct value.

Clean-up

  • Rebuilt dependancies to remove items no longer required and to bump versions to address vulnerabilities.

Pricing Data Addition / Breaking change - removed meter/reading

05 Jun 23:36
Compare
Choose a tag to compare
  • Added pricing data (price and tier) reporting.
  • Moved Docker image to user Node 16
  • Bumped dependency version to address security issue
  • Removed deprecated meter/reading topic

1.0 and MQTT Broker Auto-Reconnect

22 May 22:38
Compare
Choose a tag to compare

Changed MQTT client implementation error handling to allow the bridge to auto-reconnect to the MQTT broker if connection is lost.

I think the bridge has matured enough to earn the 1.0 status. And since I run the project, why not!

Improved Logging

10 May 04:22
Compare
Choose a tag to compare

Fixed log messages that failed to actually relay the message. Added timestamps and some color to the log for improved readability and trouble shooting.

Making Optional Variables Optional

24 Mar 18:56
Compare
Choose a tag to compare

This release fixes issue #6. The app now properly uses the default value if SUMMATION_WATTS is not defined. The other environment variables are also validated to make sure that reasonable values have been provided if defined. App will now exit with an error if required MQTT_HOST variable is not a valid IPv4 address.

Summation Received

21 Mar 20:41
Compare
Choose a tag to compare

Exposed the Summation Received value as MQTT_TOPIC/meter/received. This value reports power returned to the grid from local generation.

Provided an option to report summation values in Wh instead of kWh. This is done by setting the new environment variable SUMMATION_WATTS to true.

Removed retain flag on the device status to avoid possible confusion. The bridge regularly updates the device status topic and the status of the device is unknown if the bridge is down.

The MQTT topic MQTT_TOPIC/meter/reading for Summation Delivered (traditional 'Meter Reading') has been deprecated in favor of MQTT_TOPIC/meter/delivered to match the actual message provided by the Eagle. The MQTT_TOPIC/meter/reading topic will be removed in a future version.

Device Availability

07 Mar 00:01
Compare
Choose a tag to compare

This change is to enable the ability to have appropriate automated alerts and responses by providing the status of the device and the bridge.

The /availability topic now tracks the state of the Rainforest Eagle, This is accomplished by setting the topic to online whenever a new message is received and to offline if a messages has not been received for at least 30 seconds.

The /bridge/status topic is set to online when the bridge connects to the MQTT broker and to offline when the LWT is triggered. With this data you can differentiate between the bridge being down and the device not sending data.

The Zigbee connection information (status, signal, and channel) reported by the Rainforest Eagle has moved to individual topics under /zigbee.

Dependency version bump

25 Oct 20:26
Compare
Choose a tag to compare

Updated to address 'bl' security issue. Bumped other dependancies while I was at it.