Unable to control light bulb from local MQTT broker about meross HOT 6 CLOSED

I forgot to update this but that did the trick! Thanks again @timnolte!

from meross.

FYI, looks like I was on an old version of mosquitto (v1.5.7) that was using MQTT v3.1.1
I upgraded to mosquitto v2.0.12 which uses MQTT v5.0/v3.1.1/v3.1

I then re-registered the device with the following:

$ ./meross setup --gateway 10.10.10.1 --wifi-ssid myssid --wifi-pass mypass --mqtt mqtts://<BROKER_IP>

Unfortunately that did not fix my issue, but it was probably a good thing to do anyway!

from meross.

@mjrinker I don't have the MSL120 however I have this working with Home Assistant using Mosquitto as my MQTT Broker. The key for me however was that I needed to make sure to have an account created using the Device Credentials in order for the MQTT communication to happen. In my case I am using Home Assistant and so my Mosquitto authentication is connected with Home Assistant where I created the user account based on the Meross Device Credentials. I have been able to confirm that connecting to the MQTT Broker with those credentials I can see the messages going between my Home Assistant and the Meross devices.

Noting that I'm only on version 2.0.11 of Mosquitto.

from meross.

@timnolte This is good info. Looking at the step from the Wiki that you linked, it mentions passing the user and key to the meross setup command. Do I do this when I run that command to setup a device?

from meross.

@mjrinker so what I've been pairing my devices with is 0 as the user and a blank key, so for example the password would looking like 0_<MD5-HASH-DEVICE-MAC-ADDR>. However, if you run the meross info command you should get an output that included the currently configured Username/Password and can simply setup those in your MQTT Broker for authentication.

from meross.

@timnolte Ah okay that makes sense! I'll work on that tomorrow. Thanks!

from meross.