I’m curious, too. The cube seems like a very versatile switch. In hopes that today’s Gateway update will finally make the Cube functional, I’ve started writing a couple of automations for it:
Step 1: I an input_select in HA, so that cube can do multiple functions: Livingroom Lights ; Livingroom TV ; Spare room Lights ; Spare room TV.
Step 2: First cube action is shake_air. It will move the input_select to the next option, and, hopefully, announce the new selection over Google Home.
The remaining steps will involve defining the other actions for each of my possible settings.
Livingroom lights, I’m thinking: Flip90 = toggle the main lights ; Flip180 = toggle the end table lights. I’d love for rotate to dim or brighten the lights based of direction of rotation, but I don’t think that data is being exposed yet. Move = only one light on. Double tap = all lights off, switch input_select to something else.
Livingroom TV is kind of limited until I get some way to send remote control signals (like a Harmony Hub), but for now it should be able to change apps on the Roku: Flip90 = Netflix ; Flip180 = Hulu ; Move = Youtube. Would love to control volume by rotation, but even if the cube was up to it, I can’t control volume through HA yet. Double tap will hopefully power down the TV and switch the input_select to something else.
Spare room is pretty much the same. Spare room is going to need its own cube, I think.
Thinking also that it could do well to control audio by “casting” a playlist or radio station to a speaker or group of speakers. Some actions could decide the audio source, some the volume, and some could skip tracks. But that may depend on how much Google Cast is controllable by Home Assistant.
Those are my thoughts. Curious what anyone else has in mind.
I’m also having the issue with sensors stuck on “on”. I think pooling should be added, since it makes the system more reliable. You could add a default of about 30 seconds, for example, since that would not cause any congestion on the network, but allow it to be configurable. I’ll probably set it to 10 seconds or less
Also, I think that if HA pools the device X times (5, for example) and the device does not respond (goes offline), sensors should reset to off (or to an assumed state defined on the sensor config).
By the way, lets say there’s motion for 5 minutes. Does the gateway send multiple “on” events? Or only 1?
I’ve checked and the hub keeps sending the “motion” package every minute or so. Unfortunately, HA only updates on the first one. It would be nice to have it update the sensor every time it receives “motion”. This helps with some type of automations, which do not relly on the “off” state.
But I was facing issues enabling the developer mode on the gateway by using the iOS MI Home app.
Kept getting a ‘retrieve failed’ error. The Android app seems to work fine, but I don’t have any Android device at home.
Seems RGB-write (set and turn on\off RGB light on gateway) works too, but little fix needed, send 0 to turn off and int value(for example: 1694440448) to turn on: