Would very much appreciate whatever information you are willing to provide once those arrive. 6 buttons plus some limited status LED capability (RBW... really Ubiquiti? RGBW would have hurt?).
Ubiquiti really likes their blue and white.
It may well be RGBW and they are only listing the colors they are using for the Ux. It may not matter. Do they expose the LEDs in any of the other integrations?
I can control on/off of the LEDs of most things in my Unifi Network drivers. Before they did the cost reduction of switching to white/blue they used to have RGBW. On those devices (like my U6 access points) the drivers can control the full color range.
Since the costs of such things have become more reasonable again post-pandemic (which is when they switched away from RGBW due to supply issues supposedly) one would have hoped they would switch back.
Itâs all plastic. It doesnât feel solid or hefty like most of their stuff. Hopefully it is durable enough for normal use.
Six buttons, each with press, double, and long. Easily configurable to trigger Protect or HE (via webhooks).
It does what it is suppose to.
Hum being a keychain type device I hope it holds up well. Iâve noticed that even some of the newer car key fobs donât hold up like they used to which is unfortunate.
Ubiquiti has an odd mix of devices, where some are wonderfully constructed seeming AND reasonably priced, most are well constructed but expensive, and a few that just seem shoddy (the newer rack-mount UPS fits in that for me).
The key fob seems like it would have been a good opportunity for a higher-end feel at least, since (in theory) people would be dealing with it very frequently.
I'm using the official Hubitat Protect plugin for my superlink sensors but I noticed that my USL-Environmental are detected as "Component Illuminance Sensor" and Hubitat driver doesn't expose capability for water detection.
Tagging @bertabcd1234 as I believe he is familiar with the official Hubitat Protect integration.
Did you ever figure out how to get sensors from the unifi alarm hub into Hubitat? I have it working in Home Assistant, but want to get these incorporated to HSM as well; the native unifi protect app isn't getting these senosrs in there; it only sees my unifi protect cameras.
The built-in integration was originally written only for cameras (and camera events specifically; RTSP would be the solution for video now, also relatively new). Support for the UP-Sense was added later, and it's likely to also work for sensors that report similar events. Others, like the fob/button, are completely unsupported. I'm not sure how the alarm sensors work. If you enable all debug logging for the app and Protect "console" driver, especially during discovery and actual device events (e.g., motion or glass break or whatever), there might be some data in there that would be helpful in determining if or how these can be supported if anyone is interested.
The fact that most of the others require a proprietary, non-cheap SuperLink gateway and there are lots of similar devices that could work directly with Hubitat instead may or may not be one of the reasons for this being the way it is, but I digress... 
I created drivers for the HE side and use MakerAPI for the events. Works great.
I have all of the different Unifi sensors, fobs, sirens, speakers, and smoke/CO working. So it can be done. It just takes a little knowledge and effort.
I use it with the G6 Entry Pro and Level locks for auto unlocking.
And, I use Protect to trigger presence, which works amazingly well.
I prefer this setup over the built-in one.
The new API (that the built-in integration uses) does (finally) support sensors directly, but that capability would need to be added to the built-in method to be able to use them.
Other community drivers also provide sensor data. For my drivers, I have been working with one person to make sure the new Air Quality sensor is supported nicely (and am awaiting some data for the key fob, but I already have most other sensors). I will note that we have discovered the Air Quality sensor is EXTREMELY chatty on WebSockets... to the point it causes noticeable load. This is even after we reduced the events a lot by rounding the values (they publish most of them in hundredths, but the sensor quality is +-5%, so what is the point in a value that says 0.01%). The parent still has to process all the WebSocket data coming in even if it ends up getting ignored.
The sensors I use are non-branded hard-wired alarm sensors that were part of my home's former ADT system. I ended up getting them imported to home assistant via a HACS app, then used the Hubitat "HADB" package to port them into Hubitat. All is working well, though I decided against adopting them natively into Hubitat.