MerossIot icon indicating copy to clipboard operation
MerossIot copied to clipboard

Meross errors in home assistant

Open mikefrantz opened this issue 6 months ago • 4 comments

I am getting many errors in Home Assistant and need some help resolving. Here are the errors I am seeing.

Logger: meross_iot.manager Source: /usr/local/lib/python3.13/site-packages/meross_iot/manager.py:675 First occurred: 7:03:56 AM (301 occurrences) Last logged: 9:07:28 AM

Push notification parsing failed. That message won't be dispatched.

Logger: meross_iot.model.enums Source: /usr/local/lib/python3.13/site-packages/meross_iot/model/enums.py:162 First occurred: 7:03:56 AM (301 occurrences) Last logged: 9:07:28 AM

Namespace Appliance.Control.Sensor.LatestX is not currently handled/recognized.

mikefrantz avatar May 29 '25 13:05 mikefrantz

Donation bot here. Supporters can mark their interest in this issue by adding a comment starting with "+1" (without quotes) or adding the "#supporter_sponsor" keyword (without quotes) in their comments.

You can become a donor by subscribing as Sponsor from the GitHub sponsorship page or from the BuyMeACoffee page.

Issues marked by donors will be labeled accordingly and handled with special care

donations-bot-prod[bot] avatar May 29 '25 13:05 donations-bot-prod[bot]

I am using the latest Meross integration 1.3.6 with Home Assistant.

System Information

version core-2025.5.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.3
os_name Linux
os_version 6.6.74-haos-raspi
arch aarch64
timezone America/New_York
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 1922
Downloaded Repositories 8
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 15.2
update_channel stable
supervisor_version supervisor-2025.05.3
agent_version 1.7.2
docker_version 28.0.4
disk_total 916.9 GB
disk_used 11.0 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board yellow
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.17.0), Studio Code Server (5.19.3), Silicon Labs Multiprotocol (2.4.5), Matter Server (8.0.0), Home Assistant Google Drive Backup (0.112.1), Tailscale (0.25.0), Duck DNS (1.19.0), ESPHome Device Builder (2025.5.1)
Dashboards
dashboards 6
resources 3
views 5
mode storage
Network Configuration
adapters lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vetha6288ea (disabled), veth75f614a (disabled), vethad3cfc6 (disabled), veth155289a (disabled), vethba146c6 (disabled), vetha91e64a (disabled), vetha77c612 (disabled), vethf5e0fc8 (disabled), wpan0 (disabled), vethbec1ca0 (disabled), veth963f3d3 (disabled)
ipv4_addresses lo (127.0.0.1/8), end0 (192.168.68.51/22), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vetha6288ea (), veth75f614a (), vethad3cfc6 (), veth155289a (), vethba146c6 (), vetha91e64a (), vetha77c612 (), vethf5e0fc8 (), wpan0 (), vethbec1ca0 (), veth963f3d3 ()
ipv6_addresses lo (::1/128), end0 (fd62:46c2:cb31:6c64:e6e5:24b9:4f2b:9e19/64, fe80::e857:aa27:52dd:269b/64), hassio (fe80::1c21:b4ff:fe34:98de/64), docker0 (fe80::5499:6cff:fe04:4f7d/64), vetha6288ea (fe80::488d:5ff:fe4e:9fe2/64), veth75f614a (fe80::20a4:bbff:feb9:4f00/64), vethad3cfc6 (fe80::1c54:ecff:fe19:e0bb/64), veth155289a (fe80::80fc:2aff:fe83:7a01/64), vethba146c6 (fe80::988d:a7ff:fe12:6714/64), vetha91e64a (fe80::9059:4dff:fec2:ca2a/64), vetha77c612 (fe80::e0da:afff:fe49:c482/64), vethf5e0fc8 (fe80::44c4:50ff:fe24:100f/64), wpan0 (fdf9:c62b:dc8d:fa3c:0:ff:fe00:fc11/64, fd97:f55b:41df:1:3d7a:df52:bb9c:f2bc/64, fdf9:c62b:dc8d:fa3c:0:ff:fe00:fc10/64, fdf9:c62b:dc8d:fa3c:0:ff:fe00:fc38/64, fdf9:c62b:dc8d:fa3c:0:ff:fe00:fc00/64, fdf9:c62b:dc8d:fa3c:0:ff:fe00:bc00/64, fdf9:c62b:dc8d:fa3c:4a44:d85:5fa0:9540/64, fe80::d48b:72e0:9b5c:f3eb/64), vethbec1ca0 (fe80::bc06:54ff:fe9b:db79/64), veth963f3d3 (fe80::2402:9aff:fedb:6959/64)
announce_addresses 192.168.68.51, fd62:46c2:cb31:6c64:e6e5:24b9:4f2b:9e19, fe80::e857:aa27:52dd:269b
Recorder
oldest_recorder_run May 21, 2025 at 11:16 PM
current_recorder_run May 24, 2025 at 10:44 AM
estimated_db_size 1342.39 MiB
database_engine sqlite
database_version 3.48.0

mikefrantz avatar May 29 '25 13:05 mikefrantz

Image

mikefrantz avatar May 29 '25 13:05 mikefrantz

Issue: Namespace Appliance.Control.Sensor.LatestX Not Handled/Recognized

Description

The meross_iot library is logging an error indicating that the namespace Appliance.Control.Sensor.LatestX is not currently handled or recognized. This issue appears in HomeAssistant logs and seems to prevent certain push notifications from being dispatched.

Error Details

Logger: meross_iot.model.enums

Source: /usr/local/lib/python3.13/site-packages/meross_iot/model/enums.py:162

Message: Namespace Appliance.Control.Sensor.LatestX is not currently handled/recognized

Occurrences: 301 times

Related Issue: This may be related to a separate HomeAssistant error (TypeError: Recursion limit reached) in config_entries.py, potentially caused by the same Meross integration issue.

Environment

Meross Device: [Replace with your device model, e.g., Meross MSS310 Smart Plug]

Firmware Version: [Replace with firmware version from Meross app]

meross_iot Version: [Replace with version, e.g., pip show meross_iot output]

HomeAssistant Version: [Replace with version, e.g., 2025.5.x]

Python Version: 3.13

Operating System: [Replace with OS, e.g., Linux, Docker, etc.]

Steps to Reproduce

Set up the Meross integration in HomeAssistant.

Operate the Meross device (e.g., toggle power, check sensors).

Monitor HomeAssistant logs for errors related to meross_iot.

Expected Behavior

The meross_iot library should recognize and handle the Appliance.Control.Sensor.LatestX namespace, allowing push notifications to be processed correctly.

Actual Behavior

The library logs the error Namespace Appliance.Control.Sensor.LatestX is not currently handled/recognized, and affected notifications are not dispatched.

Additional Context

This issue may be related to a recent firmware update on the Meross device introducing the LatestX namespace.

Debug logs for meross_iot are not yet enabled but can be provided if needed.

No relevant discussions were found on GitHub or X regarding this namespace.

Request

Can you confirm if Appliance.Control.Sensor.LatestX is a known namespace for newer Meross devices or firmware?

If this is a new namespace, please consider adding support for it in the meross_iot library.

Any guidance on capturing the payload causing this error would be appreciated.

Logs

Logger: meross_iot.model.enums Source: /usr/local/lib/python3.13/site-packages/meross_iot/model/enums.py:162 First occurred: 7:03:56 AM (301 occurrences) Last logged: 9:07:28 AM Namespace Appliance.Control.Sensor.LatestX is not currently handled/recognized.

Please let me know if additional information or debug logs are needed. Thanks for your support!

mikefrantz avatar May 29 '25 13:05 mikefrantz

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jul 28 '25 21:07 stale[bot]