After Connecting Cloud Method - Devices Don't Show Up

[tiztrain]

Connected successfully via cloud method but nothing show up even after a restart and a manual power cycle and 10 sec wait. Attached files for debugging

Installation method
Home Assistant OS
Core
2026.8.2
Supervisor
2026.07.5
Operating System
18.2
Frontend
20260729.7

2026-08-20_13-53-36_profile_@0.csv
config_entry-meross_lan-01M0EEBXNTS1H1H2CQ4S1KAXM7.json

[tiztrain]

Update: garage opener has shown up after a day but mss305 smart plug has not

[krahabb]

Hello @tiztrain,
In order to allow automatic detection through the cloud account you'd have to enable 'allow MQTT publish' option in the cloud entry configuration else the component is prevented from querying the device over cloud MQTT.
In your scenario, devices, even though the cloud configuration is correct and shows both of them (stored in the logs you provided) can only be detected over LAN when devices themselves trigger a DHCP subscription on your router so that the software can detect the address where to find them. This likely happened for the garage door but not (yet) for the mss305.
At any rate, enabling MQTT publishing should fix the discovery issue. After that, you could disable the option again and everything will keep working locally as far as the IP address of devices doesnt suddenly change.
If you're scared of 'cloud publishing' consider, unless you force MQTT protocol in a device configuration, meross_lan will always prefer (local) HTTP communication and only eventually fallback to (cloud) MQTT when HTTP doesn't work.

[tiztrain]

Hey @***@***.***>, The plug ended up appearing on it's own too so it sorted itself out now but good to know for future Meross items. Thanks for getting back to me. Adam From: krahabb ***@***.***> Sent: Tuesday, 25 August 2026 3:28 AM To: krahabb/meross_lan ***@***.***> Cc: Adam Tolo ***@***.***>; Mention ***@***.***> Subject: Re: [krahabb/meross_lan] After Connecting Cloud Method - Devices Don't Show Up (Issue #667) [https://avatars.githubusercontent.com/u/13969600?s=20&v=4]krahabb left a comment (krahabb/meross_lan#667)<#667 (comment)> Hello @tiztrain<https://github.com/tiztrain>, In order to allow automatic detection through the cloud account you'd have to enable 'allow MQTT publish' option in the cloud entry configuration else the component is prevented from querying the device over cloud MQTT. In your scenario, devices, even though the cloud configuration is correct and shows both of them (stored in the logs you provided) can only be detected over LAN when devices themselves trigger a DHCP subscription on your router so that the software can detect the address where to find them. This likely happened for the garage door but not (yet) for the mss305. At any rate, enabling MQTT publishing should fix the discovery issue. After that, you could disable the option again and everything will keep working locally as far as the IP address of devices doesnt suddenly change. If you're scared of 'cloud publishing' consider, unless you force MQTT protocol in a device configuration, meross_lan will always prefer (local) HTTP communication and only eventually fallback to (cloud) MQTT when HTTP doesn't work. - Reply to this email directly, view it on GitHub<#667?email_source=notifications&email_token=AHEB5DICVNL6BZTWPLXMOJD5LR3JBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZZHA4DOOJTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5398879353>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHEB5DOBVR22YSRTQFGWIW35LR3JBAVCNFSNUABFKJSXA33TNF2G64TZHMZTIMJVGAYDCMRWHNEXG43VMU5TKMJZHE2TENJUHEYKC5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AHEB5DLO6TAOQSPTTEJYJWD5LR3JBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZZHA4DOOJTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AHEB5DMFE5IBBZGFBB57CED5LR3JBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZZHA4DOOJTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>