Zigbee2mqtt: Aqara Cube | modelID not recognized with Firmware 20180815

[AnhDuc85]

Just flashed firmware 20180815 to my CC2531 and the cube doesn't work anymore. The cube worked fine under 20180705 no matter which docker images has been used. How can it be?

db entry of the paired and previous working cube under firmware 20180705: https://pastebin.com/raw/xRPQYxTc

db entry of the paired and previous working cube under firmware 20180815: https://pastebin.com/raw/EUNYTe4t

[ben423423n32j14e]

You know it's necessary to re-pair a device after updating the firmware?

[AnhDuc85]

sure, I repaired all my devices, that's why I'm so confused as my cube is not working anymore

[AnhDuc85]

seems like the modelID can not be recognized with new firmware.
When I edit devices.js and replace modelID 'lumi.sensor_cube' with "0x656275635f726f736e65732e696d756c" the cube is working as before.

[aptonline]

@AnhDuc85 In relation to this I just received my Aqara cube (ordered an Xiaomi but I'm guessing they are the same) but I cannot get the tap function to work. All other functions are being seen in terminal except this.

Any ideas?

Also how can you update the firmware of the cube without an original hub and Xiaomi app? It is possible?

[AnhDuc85]

@aptonline tap is working out of the box, some samples:
payload: '{"battery":"98.33","voltage":2995,"linkquality":105,"action":"tap","side":0}'
payload: '{"battery":"98.33","voltage":2995,"linkquality":107,"action":"tap","side":5}'

As far as I know, there is no other way to update the cube firmware except via xiaomi hub and app.

[aptonline]

No for me @AnhDuc85, I've double checked and not getting any tap payload exposed in terminal. All other functions are there. Running [email protected]

[AnhDuc85]

do you get the "tap" via Mi Home app?

[wilfredsmit]

seems like the modelID can not be recognized with new firmware.
When I edit devices.js and replace modelID 'lumi.sensor_cube' with "0x656275635f726f736e65732e696d756c" the cube is working as before.

Here the same. As a workaround it's fine, but I hope it will be fixed.

I have the Mi cube.

[Koenkk]

@wilfredsmit @AnhDuc85 are you sure this is because of the firmware update and not because a zigbee2mqtt update?

(when you revert to the old firmware, does it work again?)

[AnhDuc85]

It stopped working after I updated my firmware and re-paired the cube. Also, I tried with old zigbee2mqtt image but still same.

Within the next days, I will get another CC2531, will flash old firmware and double check. Don't want to use my current stick and re-pair the devices again :-)

[wilfredsmit]

The same for me. I updated my firmware and re-paired the cube. Btw I use the docker image.

[AnhDuc85]

@Koenkk
Firmware 20180507: https://pastebin.com/raw/iiQW0K5d
Firmware 20180815: https://pastebin.com/raw/ZwdPtEeV
Now it's 100%, there is an issue with the firmware

[Koenkk]

@AnhDuc85 could you trigger some actions when running both firwmare?

You 20180815 has some more events:

  zigbee2mqtt:debug 2018-9-25 19:25:06 Recieved zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"modelId":"lumi.sensor_cube.aqgl01"}}' of device '0x656275635f726f736e65732e696d756c' (0x00158d0002791e60)
  zigbee2mqtt:warn 2018-9-25 19:25:06 Device with modelID '0x656275635f726f736e65732e696d756c' is not supported.
  zigbee2mqtt:warn 2018-9-25 19:25:06 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
  zigbee2mqtt:debug 2018-9-25 19:25:07 Recieved zigbee message of type 'devInterview' with data '"0x00158d0002791e60"'

[AnhDuc85]

same with all events (tap, rotate, flip, ...). Only the presentValues changes: https://pastebin.com/raw/QefxNYT3

[Koenkk]

And how does it look like when running with the 20180507 firmware? (with the same cube)

[AnhDuc85]

Seems like I mixed up something. Problem is not relating to Firmware.
However, it's not possible to pair the cube with stable and latest-dev BUT it's possible to pair with 0.1.3.
Once the cube is paired, switch back to latest-dev or stable and everything seems fine.
@wilfredsmit can you try that?

[JaapBraam]

I am experiencing the same error.
Maybe there is a clue here: 0x656275635f726f736e65732e696d756c in ascii spells ebuc_rosnes.imul (lumi.sensor_cube reversed...)

[wilfredsmit]

@AnhDuc85 I'm afraid I don't have the time to test this the coming days, as I'm not at home.

[Koenkk]

So then it seems to be a problem of the new zigbee2mqtt version.

[apeeters]

I just paired 2 brand new cubes (with newer firmware, I guess). These are not recognised: "Device with modelID '0x656275635f726f736e65732e696d756c' is not supported.". Older cubes still work, so I'm not sure the problem is caused by zigbee2mqtt.

As @JaapBraam mentioned before, when decoding this modelID hex string, we get the normal model id but reversed...?

[apeeters]

For the record: the old (working) cubes are Mi branded whereas the new ones are Aqara branded.

[Koenkk]

Probably the issue is due to a recent change in https://github.com/Koenkk/zcl-packet or https://github.com/Koenkk/zigbee-shepherd. Will investigate...

[Koenkk]

If found out this is due to: https://github.com/Koenkk/zcl-packet/commit/800a492c004cabac5b7f4421c8254d1803849f1a

@dzungpv could you take a look at this?

[Koenkk]

Fixed in the dev branch, thanks for reporting (don't forget to repair)

[lolorc]

@Koenkk could you reopen https://github.com/Koenkk/zigbee2mqtt/issues/373 then ? :-)

[ABeumer525]

Why is this closed? Still a problem in 0.1.6

[Koenkk]

@ABeumer525 can you check the dev branch?

[wilfredsmit]

It is still a problem in 0.1.7

[HA-TB303]

yup, having the same issue here. The cube was working fine before.

[Koenkk]

@wilfredsmit have you done a rm -rf node_modules && npm install?

[wilfredsmit]

@Koenkk No. I use docker. So as far as I know this should not be necessary. But correct me if I'm wrong.

[Koenkk]

@wilfredsmit before pairing it again, did you remove all entries of this device from database.db? (and then restart zigbee2mqtt)

[wilfredsmit]

No, I have not done this. Do you mean I have to remove the cube entry by entering the MQTT command zigbee2mqtt/bridge/config/remove with the cube device address as the payload? And then reset the cube and pair it again?

[Koenkk]

Try:

• Stop zigbee2mqtt
• Remove all entries of the cube (by searching on ieeAddress) from database.db
• Start zigbee2mqtt
• Pair cube

[maartendamen]

I am also experiencing this issue with a brand new wxkg12lm straight from the box. Paired the same model succesfully several times before. I get these errors in the logs (I am on dev branch):

Device with modelID '0x746977735f726f736e65732e696d756c' is not supported.

Steps I took to switch to dev branch:

git checkout -b dev origin/dev
git pull (already up-to-date)

rm -rf node_modules
npm install

Edit: my bad, removing entries from database.db fixed the problem.

[wilfredsmit]

@Koenkk Hi Koen,
Still no success. This is my log.

  zigbee2mqtt:info 2018-10-19 16:50:30 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-10-19 16:50:54 New device with address 0x00158d0001041de0 connected!
  zigbee2mqtt:info 2018-10-19 16:50:54 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"device_connected","message":"0x00158d0001041de0"}'
  zigbee2mqtt:warn 2018-10-19 16:50:57 Device with modelID 'lumi.sensor_cube' is not supported.
  zigbee2mqtt:warn 2018-10-19 16:50:57 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
  zigbee2mqtt:warn 2018-10-19 16:50:58 Device with modelID 'lumi.sensor_cube' is not supported.
  zigbee2mqtt:warn 2018-10-19 16:50:58 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
  zigbee2mqtt:warn 2018-10-19 16:51:00 Device with modelID 'lumi.sensor_cube' is not supported.

edit: Success! I reinstalled the docker image also and finally, everything works as it should.

[Ciubas]

Whre is file database.db in Home Assistant with Supervisor in Docker and Zigbee2MQTT as Supervised addon?

I just used the Zigbee2MQTT Assitant dont help but a lot of click to the button (inside cube) helps to change unsupported to discovered! :)