InvisOutlet (Aura & Pro) - Hubitat Drivers need to be updated - Feature missing

📢 Feedback Feature Requests
1

@bcopeland @kkossev

So I have the InvisOutlet Aura and the Pro now. I see in a recent update that built in drivers were added, but both are missing things.

Pro Version
They are missing the Upper Button and Lower Button. Let me clarify. The outlets have hidden touch buttons, in the actual InvisOutlet App on my phone, when you go to device settings there is an option called, Touch Control, When turned on, you can touch the outlet on the left side and toggle each outlet (Upper touch button and lower touch button).

However in the app there is also a new option once you toggle Touch Control on, you now get an notion called Magic Touch and when enabled, the touch buttons no longer control the outlet, but have become push buttons, so that you can touch them and trigger things to happen. And they will not be discoverable until this is turned on in the app. I know this because when using the "Matter Advanced Bridge" that kkossev created and work with me some on the Aura version, he help find and expose them. They us the "Matter Generic Component Switch" Driver

But the Built In Driver is nicer as it already labels things correctly. and would be nice if the Upper Button and Lower Button, can be added.

Now I did notice that the Built in Driver finds the Pressure Sensor and the Matter Advanced Bridge did not

Pro Version - Using Built In Driver

invis pro - invis driver
invis pro - invis driver1770×642 105 KB

Pro Version - Using the Matter Advanced Bridge

invis pro - User driver
invis pro - User driver1772×674 104 KB

Aura Version
This is missing 1 more option then the Pro. The Aura also has the same touch buttons and if turned on in the app they also can be discovered using the Matter Advanced Bridge. (And they do function as intended).

The other thing missing that is the RGB Color Light on the bottom. That too can be discovered by the Matter Advanced Bridge. And be aware that the lights are RGB. And it uses the "Generic Component RGB" driver and that works great. (it might auto select the RGBW, so manually change it)

Aura Version - Using Built In Driver

invis Aura - invis driver
invis Aura - invis driver1764×256 39.2 KB

Aura Version - Using Matter Advanced Bridge Driver

invis Aura - User driver
invis Aura - User driver1760×427 65.3 KB

Let me know what you need from me to help get this done.

2 Likes
2

Here is what happens when I press one of the buttons on the Aura Outlet (Using the Matter Advanced Bridge Driver / Matter Generic Component Button) That use to work, but now does not!

This was a short press
dev:20832026-02-20 01:10:16.939 PM debug Button shortRelease event processed
dev:20832026-02-20 01:10:16.938 PM debug Button handleUnprocessed: {"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":3,"timestamp":1047982,"timestampType":0,"priority":1,"eventSerial":65620,"data":{"3:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}
dev:20832026-02-20 01:10:16.936 PM debug Button [[name:unprocessed, value:{"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":3,"timestamp":1047982,"timestampType":0,"priority":1,"eventSerial":65620,"data":{"3:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}, descriptionText:Button unprocessed cluster 003B event 3 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:10:16.899 PM debug Button currentPosition changed to 0
dev:20832026-02-20 01:10:16.898 PM debug Button handleUnprocessed: {"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":0},"value":0,"cluster":"003B","endpoint":"0C","attrId":"0001"}
dev:20832026-02-20 01:10:16.896 PM debug Button [[name:unprocessed, value:{"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":0},"value":0,"cluster":"003B","endpoint":"0C","attrId":"0001"}, descriptionText:Button unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:10:15.917 PM debug Button initialPress event processed
dev:20832026-02-20 01:10:15.915 PM debug Button handleUnprocessed: {"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":1,"timestamp":1047912,"timestampType":0,"priority":1,"eventSerial":65619,"data":{"1:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}
dev:20832026-02-20 01:10:15.913 PM debug Button [[name:unprocessed, value:{"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":1,"timestamp":1047912,"timestampType":0,"priority":1,"eventSerial":65619,"data":{"1:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}, descriptionText:Button unprocessed cluster 003B event 1 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:10:15.894 PM debug Button currentPosition changed to 1
dev:20832026-02-20 01:10:15.892 PM debug Button handleUnprocessed: {"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":1},"value":1,"cluster":"003B","endpoint":"0C","attrId":"0001"}
dev:20832026-02-20 01:10:15.891 PM debug Button [[name:unprocessed, value:{"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":1},"value":1,"cluster":"003B","endpoint":"0C","attrId":"0001"}, descriptionText:Button unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]

This was from a Long Press
dev:20832026-02-20 01:10:02.184 PM debug Button ignored longRelease for button 1 (not held)
dev:20832026-02-20 01:10:02.182 PM debug Button handleUnprocessed: {"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":4,"timestamp":1034112,"timestampType":0,"priority":1,"eventSerial":65618,"data":{"4:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}
dev:20832026-02-20 01:10:02.180 PM debug Button [[name:unprocessed, value:{"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":4,"timestamp":1034112,"timestampType":0,"priority":1,"eventSerial":65618,"data":{"4:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}, descriptionText:Button unprocessed cluster 003B event 4 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:10:02.127 PM debug Button currentPosition changed to 0
dev:20832026-02-20 01:10:02.125 PM debug Button handleUnprocessed: {"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":0},"value":0,"cluster":"003B","endpoint":"0C","attrId":"0001"}
dev:20832026-02-20 01:10:02.122 PM debug Button [[name:unprocessed, value:{"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":0},"value":0,"cluster":"003B","endpoint":"0C","attrId":"0001"}, descriptionText:Button unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:09:55.185 PM debug Button initialPress event processed
dev:20832026-02-20 01:09:55.184 PM debug Button handleUnprocessed: {"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":1,"timestamp":1027161,"timestampType":0,"priority":1,"eventSerial":65617,"data":{"1:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}
dev:20832026-02-20 01:09:55.182 PM debug Button [[name:unprocessed, value:{"callbackType":"Event","endpointInt":12,"clusterInt":59,"evtId":1,"timestamp":1027161,"timestampType":0,"priority":1,"eventSerial":65617,"data":{"1:STRUCT":{"0:UINT":1}},"value":{"0":1},"cluster":"003B","endpoint":"0C"}, descriptionText:Button unprocessed cluster 003B event 1 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:20832026-02-20 01:09:55.163 PM debug Button currentPosition changed to 1
dev:20832026-02-20 01:09:55.162 PM debug Button handleUnprocessed: {"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":1},"value":1,"cluster":"003B","endpoint":"0C","attrId":"0001"}
dev:20832026-02-20 01:09:55.160 PM debug Button [[name:unprocessed, value:{"callbackType":"Report","endpointInt":12,"clusterInt":59,"attrInt":1,"data":{"1:UINT":1},"value":1,"cluster":"003B","endpoint":"0C","attrId":"0001"}, descriptionText:Button unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
3

Not my driver.. But I passed it along to who does maintain that one..

1 Like
4

Turns out my InvisOutlet is still sitting on my desk and joined, I'll see what I can add to the new driver, thanks!

2 Likes
5

Thank you. Let me know if there is anything you want from me, I have both of them and also noticed it has a presence sensor also can can detect about how far away. but did not see a drive, hopefully they expos that as its in the app.

Willing to help in any way I can, even beta testing as I have them on my desk also, both have been updated to the most recent firmware as of today

6

These look cool. Wish they weren't wifi. Do they have power monitoring? Would be cool to tie power to rgb.

7

They do not have power monitoring. There is a few misses they did, but hopefully in the future they make upgraded versions. I get why they went Thread over Wifi as there is no hub needed and the pro was targeted towards Airbnb rentals. The Aura is a basic dumb down version. I wish they would have combined them in one and added power monitoring. Also the wifi in them could use a better antenna. my pro likes to drop off from the phone app