Aqara cube T1 pro (again)

Phoscon App General Support
1

Hi,
I read all the postings from last year regarding Aqara cube T1 pro, but no news from 2023.
So, let´s ask again what the status is.

I try to connect the cube with the help of the Phoscon app. What happens?

  • the switch is detected as “lumi.remote.cagl02”. Seems to be correct.
  • I cannot configure a cube, I can only configure a normal switch.

Under /user/share/deCONZ/devices/xiaomi I find this file “xiaomi_mfkzq12lm_t1_pro_cube.json”. So, I assume it should work.

This is the configuration under “API information”

{
“config”: {
“battery”: 0,
“devicemode”: “action”,
“on”: true,
“reachable”: true
},
“ep”: 3,
“etag”: “f70031997e6ef8634d283f4bc4414804”,
“lastannounced”: null,
“lastseen”: “2023-11-19T16:49Z”,
“manufacturername”: “LUMI”,
“mode”: 1,
“modelid”: “lumi.remote.cagl02”,
“name”: “lumi.remote.cagl02”,
“state”: {
“buttonevent”: null,
“gesture”: null,
“lastupdated”: “none”
},
“type”: “ZHASwitch”,
“uniqueid”: “54:ef:44:10:00:7a:27:55-03-000c”
}

{
“config”: {
“battery”: 0,
“devicemode”: “action”,
“on”: true,
“reachable”: true
},
“ep”: 2,
“etag”: “9b8772a8ae3d60f7695a07ba8accc630”,
“lastannounced”: null,
“lastseen”: “2023-11-19T16:49Z”,
“manufacturername”: “LUMI”,
“mode”: 1,
“modelid”: “lumi.remote.cagl02”,
“name”: “lumi.remote.cagl02”,
“state”: {
“buttonevent”: 7000,
“gesture”: 0,
“lastupdated”: “2023-11-19T16:49:08.355”
},
“type”: “ZHASwitch”,
“uniqueid”: “54:ef:44:10:00:7a:27:55-02-0012”
}

DDF
[
“00:21:2e:ff:ff:09:aa:c1”,
“d0:cf:5e:ff:fe:13:c6:08”,
“90:fd:9f:ff:fe:d8:92:99”,
“d0:cf:5e:ff:fe:07:fe:5e”,
“90:fd:9f:ff:fe:20:db:84”,
“54:ef:44:10:00:7a:27:55”
]

What should I do to us the cube T1 pro configuration as described under devices?

My configuration

  • RasPi
  • Conbee II
  • Gateway version 2.24.1
  • Firmware 26720700

Best regards,
Stephan

2

I’m afraid I cannot follow you. Do you want to say the cube doesn’t work with deconz? It actually does and that’s also the reason why there’s not further communication around it in Github.

3

This is exactly my point. It doesn´t work.
The device was detected (lumi.remote.cagl02) but not as cube (simple switch)

4

In Phoscon you mean?

5

Yes in Phoscon App

Today, I received my Black Friday delivery. Aqara smart switch, vibration sensor, motion sensor.
All integrated in no time. Perfect.

Only the cube doesn´t work.

Any idea?

6

@de_employees has to answer that.

7

I was not aware of that new modelid of the cube. Because I see in the Phoscon App is only the last version of the cube with modelid “…cagl01”.

So the cube is just recognized as some general zigbee switch. Which does not work for the cube because it is something special with all that buttonevents and rotary events.

So I will add it to the Phoscon App and hope nothing more changed so it will just work in the App as the other cubes.

8

Thats why we have changelogs in deCONZ :wink:

9

Thanks Christian,
What does it mean for me? How and when will I receive the update?
Best regards,
Stephan

10

@ChrisHae You might want to also consider the other Cube versions/models out there, we got a few by now :slight_smile:

11

Yeah, I guess I have to take a look what models are out there and I think I will order a T1 Pro cube to see what it does.

@Rudi I think the update will be in the next Android and iOS Phoscon App update next week. And for PC perhaps in the next beta version of deCONZ.

12

… it would be great if you could give us a hint once the update is available …

13

Due to illness of our android/ios developer the release of these versions will probably postponed until next week.

The next deCONZ beta release is scheduled for end of this week or next week.

I will update you when they are released.

14

The new Update for Phoscon App for Android and iOS is available in their stores.

The new deCONZ version 2.25.0 is releasing next week then the Phoscon App update is also in there if you want to use the Phoscon App in your Browser.

I have integrated the T1 Pro Cube and other missing cube versions in the App and you can also use it in the switch editor (only action mode is supported though).

I just had some problems pairing the cube with deCONZ with version 2.24.2. Manup said it could be a bug and should be fixed in the 2.25.0 version. So we have to check this out when it comes out.

15

Thank you soo much @ChrisHae
On the Dresden Firmware Update Server, I see a new version for Conbee III (3) from 8.12. but nothing for Conbee II (2). Should I wait or can I use the version for Conbee III (3)?

16

The version Chris mentions has nothing to do with firmware.

17

I see. 2.25.0 is deCONZ the Gateway version. Thanks.
Anyhow, can I use the firmware from Conbee 3 for my Conbee 2?

18

You can not.

19

Hi @ChrisHae,
sorry. It doesn´t work. I try to pair the cube with the new Phoscon App. The app still recognise the switch as lumi.remote.cagl02. The latest deCONZ version is 2.24.2 (from 18.12.) and it doesn´t work either. Same here.
I hope it works once the 2.25.0 version is available. Any release date?

I wish you merry x-mas and all the best for 2024. Thanks a lot for your support and all the effort you put into the development.

20

I can confirm the T1 Pro cube can now be fully used in Phoscon :+1:

The latest deCONZ version is 2.24.2 (from 18.12.)

That is version 2.25.0. It has been forgotten to bump the version.