Closed pbrooks29 closed 6 months ago
It could be the unrecognized entries are due to the devices mac addresses being out of the address ranges configured in meross_lan.
You can check (and eventually edit) the manifest.json
file in meross_lan folder and see that it filters dhcp discoveries by mac address mask(s):
"dhcp": [
{"hostname": "*", "macaddress": "48E1E9*"},
{"hostname": "*", "macaddress": "34298F1*"},
{"registered_devices": true}
],
I've checked a bit of internet and seen that there's a new address range registered to Meross: C4:E7:AE*
so I guess I should add that to the manifest too....
You could rightly check if this is the case by adding the relative entry in manifest.json and reload (restart HA)
I did consider the MAC thing - and checked that all devices have the same MAC prefix (which is one of the prefixes in that table). They are also connected to the same VLAN with IP addresses in the same range. Screenshot from Ubiquiti showing all the MACs and connection parameters to the LAN. Looks like the 4 that are recognised and the 4 that are not are all identical as far as LAN connectivity and MAC ranges are concerned - so I think that isn't the issue.
Well...we should proceed in checking what's the difference between these 4 unrecognized devices and the others. Do they all belong to the same Meross account? (which I guess you've already configured in meross_lan)
In theory meross_lan can detect devices by downloading the list from the Meross account profile (when configured) but also on lan (through DHCP) whatever their Meross account binding.
If none works the reasons might be:
At any rate you could try manually enter a device configuration for the missing devices (just provide the ip address and device key) by hitting 'ADD HUB' from the meross_lan integration page. The device key should be identical to that of the other devices if those are all binded to the same Meross account (and meross_lan would likely already pre-fill this value since it guesses new devices have the same key as other configured)
I have the same problem. I had to setup my homeassistant from scratch and now only four devices (out of about 20) are recognized. I have about 16 mss710 in the network, and they do work perfectly in Homekit or Alexa. They also worked in Homeassistant before. The system drive failed, so I replaced the drive ans stated from scratch.
Four different devices where detected right away, but that's it, nothing else. (Two of them are 710, one 120b and one 110) I kept the system running for a day, but still no devices discovered.
I will try to setup manually.
Seems like I am able to add the devices manually by IP address. This is ok so I can ho on with the HA setup, but would be interesting to see, why the auto discovery failes. Maybe too many devices :-)
Additional Hint: After adding a few plugs manually, some devices where discovered automatically. I have now all the devices setup, a little bumpy road, but it works, so many thnks for the integration and the work behind it.
This is very hard to track down...I know HA DHCP component has a lot of caching/optimizations so it might get fooled somehow, meross_lan too might be buggy for the matter but, if it receives a DHCP discovery from HA core it should:
Version of the custom_component
"meross_lan": { "version": "5.0.4", "requirements": [] }
Configuration
config_entry.yaml attached. Note there are 8 x MSS310 smart-plug devices detected in the "store" section (and 1 lamp, which it correctly detects) which I presume is downloaded from the meross app/server
Screenshot of HA Ubiquiti DHCP table showing 8 Meross smartplugs - 4 recognised by Meross integration, and 4 which are not Screenshot of HA device list, showing 4 plus recgnisd by Ubiquiti and Meross, and 4 others only recognised by Uniquiti.
Describe the bug
I have 8 MSS310 smart-plugs on the network, but no matter how many times I power off or clear and re-pair the last 4, the integration only recognises the first 4. When I cleared all data in the integration, deleted all the devices, deleted the hub and started again, it also auto-recognised the first four from the LAN, and stopped after 4. Seems there is a problem recognising more then 4 MSS310 devices.
Debug log
Attached debug log - includes turning one of the missing devices off, then on again 10 - 15 seconds later, to see if there are any events detected from the missing devices