Skip to content

Releases: krahabb/meross_lan

Cloudy.5.2

05 Jan 23:16
520f3d8
Compare
Choose a tag to compare

fixes

  • error in garageDoor (msgXXX) response parsing (#361)
  • deprecation for TIME_SECONDS unit (#362)
  • error when creating a Cloud Profile while retrieving the device key from the Meross account (#365)

Cloudy.5.1

30 Dec 10:23
4f54017
Compare
Choose a tag to compare

fixes

  • deprecated units (#354): any previous release of meross_lan will likely fail to load in HA core 2025.1
  • error in parsing light payload (#357): release Cloudy.5 raises an exception while previous one where silently discarding that but the bug was there

Cloudy.5

26 Dec 21:57
fe4be5d
Compare
Choose a tag to compare

Final release of the Cloudy series. This brings little big fixes and improvements as usual. Special note to the resolution of a possibly devastating bug affecting devices connected over HTTP (99% likely) where the DHCP leases could be exchanged between two Meross devices (identical or different types doesn't matter, the mess is there!). This bug affects every meross_lan release since the beginning of times and has never popped up likely because routers typically renew the clients leases by assigning the same IP to the same mac over and over....so no issues there. But if at some point two Meross devices have their IP exchanged, meross_lan is not able to detect there's something wrong and keep talking to your plug even if it's now a bulb (or a garage door). See #341

Beside that, there are some nice features like thermostat automatic correction/tracking where you can use a different sensor to track an ambient temperature. This is particularly useful for MTS valves which are abviously extremely biased in their readings by being very close to the source of heating. Typically you would manually 'adjust' the MTS sensor reading and this concept is now implemented automatically in meross_lan where you can use any other HA temperature sensor to adjust the MTS. See #334)

features

  • support for ms400 waterLeak sensor (#332)
  • added automatic correction/tracking of climate (all the MTSXXX series) temperature reading by using a different HA sensor (#334)
  • added the MQTT connectivity check in the device configuration form (Options). When updating the configuration it now verifies the device works depending on the protocol selected. If setting 'auto' it verifies at least one of the transports is working before accepting the update
  • support reading and configuring the MTS200 schedule (implemented as a calendar entity like for the MTS100)
  • updated HA core compatibility to 2023.7.0 in HACS manifest (#348)
  • improved local MQTT device binding support (#346)

fixes

  • entity (default) naming for mts100 (#351)
  • restore garageDoor emulated open/close timer controls (mistakenly removed in Cloudy.4) (#338)
  • added stricter checking to "who we're talking with" in order to prevent bug #341
  • fixed incorrect 'adjust' settings for MS100 sensors

Cloudy.5.beta.0

22 Dec 16:18
Compare
Choose a tag to compare
Cloudy.5.beta.0 Pre-release
Pre-release

features

  • improved local mqtt binding session management (trying to fix #346)

fixes

  • entity (default) naming for mts100 (#351)
  • resolved the issue in setpoints rounding when climate tracking is enabled (#334)
  • resolved state restoration in climate tracking (#334)

Cloudy.5.alpha.2

16 Dec 19:52
Compare
Choose a tag to compare
Cloudy.5.alpha.2 Pre-release
Pre-release

Pre-release expecially targeting #346

features

  • experimental implementation of device init/pairing protocol for local MQTT binded devices

Cloudy.5.alpha.1

14 Dec 10:11
Compare
Choose a tag to compare
Cloudy.5.alpha.1 Pre-release
Pre-release

Quick release to try fix some pending issues while the new official release is waiting to be rolled out.
This version is still rather experimental and only update it if you need to quickly fix those issues. Beside that, some features are already being implemented. Check pre-release 'Cloudy.5.alpha.0' for all of these features/fixes already implemented and carried on

fixes

  • update HA core compatibility to 2023.7.0 in HACS manifest (#348)
  • try resolve failing pairing in local MQTT binded devices (#346)

Cloudy.5.alpha.0

07 Dec 15:20
Compare
Choose a tag to compare
Cloudy.5.alpha.0 Pre-release
Pre-release

This is a preview (alpha) of the next release carrying 'a lot' of fixes and improvements. This is, as usual, internally tested and working but, since it carries some wide-range refactorings, it needs some care before going to 'production'

features

  • implemented support for MS400 'waterLeak' sensor (#332)
  • support reading and configuring the MTS200 schedule (implemented as a calendar entity like for the MTS100)
  • added a special feature where you can override the temperature readings of your MTS100/150/200 and track the temperature reported by another sensor in HA (#334) - not tested on MTS200...might work
  • added the MQTT connectivity check in the configuration form (option_flow). When updating the configuration it now verifies the device works depending on the protocol selected. If setting 'auto' it verifies at least one of the transports is working before accepting the update

fixes

  • resolved a rather rare but dangerous bug with 'roaming' addresses (see #341)
  • fixed/restored the emulated open/close timeout entities for legacy garage doors (#338)
  • improved/fixed 'summerMode' support for MTS200 (#339)
  • fixed incorrect adjust settings for MS100 sensors

Cloudy.4.1

25 Nov 15:59
Compare
Choose a tag to compare

Quick fix for MTS200 being broken after experimental 'summerMode' implementation.

fixes

  • reverting back the summerMode support (#339)

Cloudy.4

23 Nov 18:20
a788b07
Compare
Choose a tag to compare

This release carries nothing big but a lot of fixes and tweaks. Also, there are some newer devices/features being supported (some still very experimental)

features

  • removed warning on received signature error
  • added calibration for MTS200 (experimental)
  • added support for MTS200 Summer Mode (#323) (experimental)
  • while implementing new HVAC cooling mode for MTS200, also MTS100 were a bit refactored (dropped HVAC auto mode - use preset instead)
  • reload/reinit device configuration after detecting a firmware update
  • added support for newer garageDoor (msgXXX) firmwares with open/close delay x channel (fixing also #301)
  • automatically enable/disable entities in MSG200 when those are enabled/disabled in Meross app (#330)
  • implement response support in meross_lan.request service (thus removing the legacy 'notification' system)
  • initial (experimental) implementation of 'OverTemp' feature for newer smart switches
  • improving timezone/daylight saving time configuration for locally mqtt paired devices (Thus trying to fix #300)
  • recognize RollerShutter fw ver 6.6.6 as providing a valid native position (#319)

fixes

  • memory leak in MTS200 unload/cleanup code
  • light/dimmers flashing on turning on (#279 #218 #325)
  • error (on HA core 2023.11) when configuring meross_lan with an incorrect device key
  • missing obfuscation of some debug log payloads
  • error on malformed RGB parameter when using adaptive_lighting integration (#309)
  • incorrect state refresh of GarageDoor (when configured with a Meross Cloud profile - #272)

Cloudy.4.alpha.3

14 Nov 16:49
Compare
Choose a tag to compare
Cloudy.4.alpha.3 Pre-release
Pre-release

Maintenance/bugfix release for some pending issues.
This release has gone some hard restructuring in MQTT message handling thus possibly introducing some unexpected behaviors (read: bugs).
It was as usual tested for some basic scenarios/devices and looks like everything is working as before but...

features

  • add support for newer garageDoor (msgXXX) firmwares with open/close delay x channel
  • automatically enable/disable entities in MSG200 when those are enabled/disabled in Meross app (#330)
  • implement response support in meross_lan.request service (thus removing the legacy 'notification' system)

fixes

  • error (on HA core 2023.11) when configuring meross_lan with an incorrect device key
  • missing obfuscation of some debug log payloads