bytespider / Meross

Investigating the Meross/Refoss MSS310 Smart Plug and getting these devices to communicate with our private MQTT brokers
113 stars 19 forks source link

mss210 contents to wifi and mqtt but doesn't push changes to mqtt [un rtl8710cf (hardware:6.0.0 firmware:6.2.3) ] #83

Closed colinfitzpatrick closed 7 months ago

colinfitzpatrick commented 7 months ago

Hi,

I've a new Meross mss210 and an existing Mqtt broker working with other Meross devices.

When I run the command to set the device, everything appears to go well. It connects to WiFi and the MQTT server.

However, the only messages the device publishes are

    "namespace": "Appliance.Control.Bind",
    "method": "SET"

and

    "namespace": "Appliance.System.Report",
    "method": "PUSH",

Pressing the switch doesn't publish anything to the broker; the device doesn't respond to anything they're subscribed to, and the green light continues to flash.

The device has an internet connection.

If I had to guess, it looks like the device is expecting a new acknowledgement before it starts to work.

colinfitzpatrick commented 7 months ago
────────────────────┬────────────────────────────────────────────────────────────────────────┐
│Device              │mss210 un rtl8710cf (hardware:6.0.0 firmware:6.2.3)                     │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│UUID                │2102015451288651300248e1e94a0b5e                                        │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│Mac address         │48:e1:e9:4a:0b:5e                                                       │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│IP address          │192.168.1.216                                                           │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│Current MQTT broker │192.168.1.200:8883                                                      │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│Credentials         │User: 48:e1:e9:4a:0b:5e                                                 │
│                    │Password: 0_ba1f97114ccc46e7901c2d01a7ee0277                            │
├────────────────────┼────────────────────────────────────────────────────────────────────────┤
│MQTT topics         │Publishes to: /appliance/2102015451288651300248e1e94a0b5e/publish       │
│                    │Subscribes to: /appliance/2102015451288651300248e1e94a0b5e/subscribe    │
└────────────────────┴────────────────────────────────────────────────────────────────────────┘
colinfitzpatrick commented 7 months ago

A Verbose info reveals:

 header: {
    messageId: 'acba636d9afbd3593d45f1991c181d23',
    namespace: 'Appliance.System.All',
    method: 'GETACK',
    payloadVersion: 1,
    from: '/appliance/2102015451288651300248e1e94a0b5e/publish',
    uuid: '2102015451288651300248e1e94a0b5e',
    timestamp: 1712137847,
    timestampMs: 815,
    sign: '41c6fa7a2dde7bf62acb6ccac533e0cb'
  },
  payload: {
    all: {
      system: {
        hardware: {
          type: 'mss210',
          subType: 'un',
          version: '6.0.0',
          chipType: 'rtl8710cf',
          uuid: '2102015451288651300248e1e94a0b5e',
          macAddress: '48:e1:e9:4a:0b:5e'
        },
        firmware: {
          version: '6.2.3',
          compileTime: '2021/10/22-11:13:43',
          encrypt: 1,
          wifiMac: '78:45:58:9f:56:75',
          innerIp: '192.168.1.216',
          server: '192.168.1.200',
          port: 8883,
          userId: 0
        },
        time: { timestamp: 1712137847, timezone: '', timeRule: [] },
        online: { status: 0 }
      },
      digest: {
        togglex: [ { channel: 0, onoff: 0, lmTime: 1712137086 } ],
        triggerx: [],
        timerx: []
      }
    }
  }
}

online: { status: 0 } is this significant?

lechercheur123 commented 7 months ago

Hello, Did you try that ? https://github.com/bytespider/Meross/issues/57#issuecomment-1416789185

colinfitzpatrick commented 7 months ago

My apologies for missing that.

lechercheur123 commented 7 months ago

My apologies for missing that.

No problem ;)

bytespider commented 7 months ago

Thank you @lechercheur123. I thought this message was implemented in MerossLAN these days but perhaps I misunderstood perhaps you're not using it @colinfitzpatrick?

colinfitzpatrick commented 7 months ago

Hi, to confirm, I don't use MerossLAN.