@Nayelyz When paired with the smartthings hub, sometimes the driver does not appear and even so it controls the entire house without even having created scenes or routines. Even in pairing mode it does this and several times it doesn’t show up, which is weird. The Driver already appeared the driver of the aqara cube of the veon, however the cube never stabilized. It still has problems, I’ve had it for 6 months and they’ve never fixed the problem. I have never used DHT for this device.
@nayelyz can you also check the above question with your team Zigbee experts, please?
most likely you need to do
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
await endpoint.write('aqaraOpple', {'mode': 1}, {manufacturerCode: 0x115f});
await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff','genPowerCfg','genMultistateInput']);
},
or
I don’t have T1 Pro in my possession, so I can’t test the code.
I have never seen any official announcement that states the cube is certified to work with Smarthings Hub.
I am not affiliated with Aqara. The driver published on my channel is not more than my old hobby project and is not supposed to be used by normal(non-developer) users. Any use beyond education and curiosity is not intended and likely will cause unstable behavior of your systems.
Moreover, the T1 Pro fingerprint is banned from the driver association list, so you should not be able to pair the driver from my channel with this device. (I did my best not to be mentioned in that context.)
@norberto_bcn Please contact Amazon to return the cube device. Or buy the official Aqara Hub to get a full support.
Sorry, probably my question wasn’t clear.
My question was not about how to properly configure the Aqara Cube T1 Pro device so that it doesn’t send On/Off/Toggle broadcasts (I have it working on the 'other platform’), but in general - is there a known way to prevent all Zigbee devices to be turned on/off by cluster 0x0006 broadcasts by any other device (not the cube in particular) ?
The same problem can happen (and happens) when OSRAM or IKEA or probably other remotes are joined to a Zigbee network without a proper initialization.
never seen such behavior with Ikea, as they use randomized group numbers ( touch link
)
You are right, I meant OSRAM and some other Aqara devices (Aqara H1 Double Rocker, for example).
Seems like such a scenario (an unsupported device joins a Zigbee network) is not considered at all in the Zigbee standards…
Thanks for answering @veonua . It makes a lot of sense for this device not to work properly with smartthings. Another question will the Aqara Cube T1 Pro be exposed by Matter through the Aqara HUBS, will the device appear on Smartthings? I have the Aqara E1 USB HUB, so far the cube has not appeared on smartthings via Matter. In aqara’s zigbee device list, it is listed. I already put the Hub’s Matter code on smartthings , so far it hasn’t appeared.
As far as I know, there is only small subset of device types supported in Matter. I don’t expect all the cube capabilities will be available outside Aqara. Maybe it can be exposed as a set of “buttons” , at least Ive seen something like this in Home Kit.
Got it, thanks for the explanation. The way is to wait for matter some function of the cube.
I recently pick up the Aqara Cube T1 Pro and just paired it with the Aqara hub. Set up a trigger for each of the six sides to run Alexa and ST routines using T Austin’s virtual device generator. Works great. Fun little device.
What do you mean with “T Austin’s virtual device generator” ? Where i can find this generator?
Greetz
Mibblitz
Thanks for the link ![]()
can i ask something else? namely what is better to connect the hub to the lan or wlan?
Thanks for you info
Connect your hib to the Lan
Thanks for the info
The latest update from January 6th V1.4 of the Cube Driver is causing me some issues. The driver is no longer updating the face of the cube. It is stuck on the “BACK”. It is showing the correct actions like flip 90 or flip 180. Any thoughts on resolving this issue?
Thanks
Chris
I have been experimenting with the T1 Cube driver that was released in December. Although it has a “pick-and-hold” action, it lacks the “slide”, “flip 90”, and “flip 180” actions. Moreover, the driver doesn’t specify the rotation direction or angle, “rotate” is the only available action.
The faces of the cube are numbered 1-6, possibly representing the number of dots printed on each face. There is a new icon for the device, but unfortunately, it is associated with the device profile and available actions.
Sorry for the inconvenience the driver v1.5 with fixed face event is published.
