Old MSS110s are discovered and added, but the devices are unavailable to HA #15
Comments
|
Hello @midnightgrue , Basically, even tho my component recognizes the switch it does so by a 'best effort' approach so, in the end, it guesses there is a switch out there but the payload structure for these MSS110 is too different from what it is expecting so it can't really correctly parse the plug response. I'm just curious as why these MSS110 are working for @nao-pon (see #6 (comment)). If you don't mind and would like to beta-test :) I would prefer you don't update them so we can check the new release is 'resilient' to older firmwares |
I always had the problem of the plugs being offline after being renamed. Since I could force the state by switching them off and on manually I always assumed that there is no MQTT heartbeat being sent (and never actually checked). But it may be the case you describe. Let me know if you want to have the tests done on my MSS110. |
|
Wow, thanks for the speedy response!
I don't actually think I can upgrade them. They were an Amazon special deal from several years ago, and were probably old even then -- but they've worked fine for me (until I shifted to a local control setup, of course). If I can get these working, I'll be perfectly happy to keep using them for another few years. Recently as part of my troubleshooting, I joined one or two of them to the Meross cloud, which indeed triggered a software update -- from 1.27 to 1.28 :) So I can easily test those two firmwares for you. Let me know if you need any more info! |
|
Thank you! |
|
I've pushed a bit of fixes to 'dev' but I want to wait to test the MSL120 bulb (tomorrow I guess) before releasing in public. |
|
Again, thank you for responding so quickly! I'm always blown away when a developer just waves a hand and fixes problems like this literally overnight :) I just quickly installed your dev branch code, and I can confirm it sort of works for my MSS110s running firmware 1.28 and 1.27. In both cases, I'm able to add the switch, rename it, and toggle it on and off (yay!). However, when I open the device in HA, it seems to be flipping itself back and forth between an unavailable status and reporting the actual switch state, about every ninety seconds. Here's the output produced by your newly verbose debug log: Here's what the swtich looks like in the lovelace info pane:
As I said, I'm not too familiar with MQTT, but it doesn't seem like this is normal behavior? If it is, well, I guess I'll have to turn the debug logging off to save my poor log files :) But this is definitely progress. I very much appreciate your help! |
|
Shame on me! Thank you |
|
I am very happy to report that the updated code works wonderfully! Full functionality, easy integration, even a functioning heartbeat that doesn't slow down my poor little database with gazillions of state changes ;) Just for your own confirmation, here's my debug log from a few days ago showing things ticking along with two MSS100s, one with firmware 1.27 and the other with 1.28: Thank you SO much for your work on this. I now have six more locally controlled smart plugs to work with -- and they were the last holdouts, too, so I am now officially free of dodgy cloud services. I'll close the issue. Thanks again! |
|
Thank you |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have some old MSS110 plugs that I have FINALLY (many thanks to @bytespider who made an update to his awesome utility in order to make it work) managed to successfully join to my local wifi and connect to my MQTT Add-on in Home Assistant.
Unfortunately, I now have a new problem... Your awesome utility is installed and running, but it only partially works. When I configure a new plug (or when I toggle the switch manually after re-installing), the meross-lan integration discovers it just fine and presents me with a configure screen. I click submit, and the new sub-integration appears to be successfully created -- but the associated devices all show status unavailable in lovelace, right from the get-go :(
I have tried creating Home Assistant users using the mac addresses as described in bytespider's wiki, and I've also tried putting the mac address logins in the configuration of the MQTT add-on itself. In both cases the result is the same: the connection appears successfully in the MQTT log, the integration discovers the new plug, but the device is unavailable to HA, and I can't interact with it in any way.
Here's the output of bytespider's verbose info command (it seems to gather the same info you want, and I'm afraid I don't quite understand MQTT well enough to figure out how to publish things manually, so hopefully this will give you what you need):
Here's the (trimmed) debug log, showing lines mentioning the meross_lan integration:
(That last line is repeated in my log every thirty seconds forever.)
(At this point only one of the devices was powered up, so that's why only the one shows online.)
I'm pretty new to MQTT and probably only know just enough to be dangerous at this point, so it's quite likely I'm doing something wrong. I'd be grateful for any troubleshooting suggestions. Please let me know if there's any further info you need.
Thank you so much in advance for any help!
The text was updated successfully, but these errors were encountered: