v10.8.0

Added

• Support for MS200 and MSH400

Changed

• Support node 22
• Bump node recommended versions to v18.20.4 or v20.18.0 or v22.9.0
• Updated HomeKit and Matter native ignore list
• Updated dependencies

v10.7.0

Added

• Support for MS600 presence sensor

v10.6.1

Fixed

• Do not require a new 2FA code when restarting plugin when a valid access token still exists

v10.6.0

Added

• Support MSP844 power strip

Changed

• Updated eslint and use new code style

v10.5.1

Fixed

• fix a login issue with using 2fa

v10.5.0

Added

• Support (beta) MS100F temperature sensor
• Support (beta) thermostat MTS960

Changed

• Add MSH300HK to IgnoreHKNative in constants.js (#572) (@LWatso99)

v10.4.1

Changed

• Fixed for hap-nodejs v1.0.0
• Updated dependencies
• Bump node recommended versions to v18.20.4 or v20.15.1

v10.4.0

Added

• Support SP425FW
• Enable Power Strips (#569) (@ZeliardM)
  • Expose multichannel switch/outlet devices as a single HomeKit power strip accessory

Changed

• Bump node supported versions to v18.19.1 or v20.11.1
• Updated dependencies

v10.3.0

⚠️ Some things of note:

• The recent updates to the plugin are in response to upcoming changes to the Meross API
  • You may have received an email from Meross about this (#556)
• The plugin will now store your Meross access token (when using cloud/hybrid connection) in the Homebridge storage directory:
  • This allows the plugin to persist your access token between Homebridge restarts
  • The plugin no longer needs to create a login session every time Homebridge starts
  • The plugin should initialise slightly faster when the token is available
  • Users using MFA/2FA on their Meross account will no longer need to update their config every time they restart Homebridge
  • If the stored token has expired, the plugin will attempt once to refresh the token when initialising and store the new one (when MFA/2FA is not enabled on your Meross account)
• If you are using MFA/2FA on your Meross account:
  • You will need to update the plugin config to include the current code from your authenticator app, otherwise the plugin will not be able to log in
  • The code is only valid for 30 seconds, so you will need to update your config and restart Homebridge within this time
  • If your stored access token becomes invalid/expires, you will need to update your config with the current code and restart Homebridge
  • I am unsure right now how long the access token is valid for!

Added

• persist access token for fewer logins
• config option to show Meross user key in the log when logging in
  • this used to only show when running beta versions of the plugin
  • for some security, this has been made an option in the config rather than always showing it
• auto-redirect http calls for users needing different Meross domain

Fixed

• device config setup

v10.2.8

⚠️ A note for users using MFA/2FA with Meross

• If you are not using MFA/2FA, you can ignore this message
• If you are using MFA/2FA:
  • You will need to update the plugin config to include the current code from your authenticator app, otherwise the plugin will not be able to log in
  • The code is only valid for 30 seconds, so you will need to update your config and restart Homebridge within this time
  • You will currently need to do this every time you restart Homebridge, until I can find a better way to handle this

Fixed

• Login issues