Hubitat
Some of you may know that I am into home auotmation. In particular I now use the Hubitat. They are constantly improving the experience, both for new and advanced users. It is hugely powerful. Everything it controls it does LOCALLY. No relying on some company cloud to deal with. If you have issues with your Internet connection, the Hubitat will still happily work away.
This does not mean it must be isolated from the Internet though. Probably the most amazing thing to me is that Hubitat makes it very easy for ANYONE to write their own drivers for devices (ZigBee, Z-Wave, or anything it can reach over your network). You can also create APPS that run on it as well. Those drivers and apps do not need to rely on data just from your network. They can check outside resources, websites, and whatever else you want to create one for. In many cases people have already created a driver or app you might be interested in. Just check their very active Community.
To give you an idea of how easy this is... I have written a bunch drivers already in Groovy. The most important ones I will just link to their project pages in the Hubitat Community. That way you can get the most up-to-date information for using them, latest versions, and in general the best experience. Not everything has a project but it is my standard going forward to try to post them as such. There are additional "works in progress" or requests for drivers people have made from me so the best spot to find them is in the Hubitat Community.
The first two projects are for Ubiquiti's Unifi controllers. I have drivers that can poll both their Network API and their Protect API and provide a lot of information to the Hubitat. The Network one in particular has a lot of functionality and covers many of their devices.
Unifi Network - This driver can access the Unifi Network API running on pretty much any Ubiquiti controller at this point. It allows the user to get a wide range of data for every device present in the Network as well as control many functions including ports on switches as well as the outlets on plugs and such.
Unifi Protect - This driver can access the Unifi Protect API running on pretty much any Ubiquiti controller at this point. Much like the Network API it provides a lot of information to the user but has more limited control capabilities. It also connects to the WebSocket provided for the Protect devices so users can get immediate notifications about events such as motion.
Next are a few weather-related projects. I started with the Ambient that I had originally so I could shut off Christmas inflatables if it got too windy. Then I expanded from there to an Ecowitt Gateway for more direct access. Then some people asked if I could make a WeatherFlow driver, so I did. These are kept pretty well updated with whatever the companies add such as local connections. I also created some more general projects to provide people forecasts for many other locations.
AmbientEcowittWeather - This allows you to get the data from Ambient or Ecowitt weather stations you may already have. It can connect to the Ambient API or allow the Hubitat to receive the data directly from the stations themselves.
WeatherFlow - This driver polls the WeatherFlow API so that users of that weather station can obtain the data that their Tempest (or other WeatherFlow device) is providing.
Weather Service Monitor 4 Hubitat - This driver can poll a variety of weather services such as for the US, UK, Australia, and more... so that users have a variety of options to obtain weather information. It is mostly geared towards providing forecast data.
Now we are into some projects for accessing devices bought and on a home network or ones that have an API (public or not, such as the Blink one).
Neptune Systems Apex - Polls your Neptune Systems Apex aquarium controller for it's status.json and parses it for the current state of your aquarium. Also can allow for manual control of ports and such.
Blink API - Polls the Blink camera API so you can arm/disarm and otherwise control or get status information on your Blink cameras.
Neuri/PWRView - Polls a Neurio (now owned by Generac and renamed PWRView) that you own and provides the energy monitoring data to your Hubitat system.
Tesla Driver - This polls the local (on network) API that Tesla Powerwall devices provide. I do not HAVE one of these but a couple people were interested and with their help I managed to write a working driver that provides them with all the information they want to know about their Powerwall installations.
The last projects (at this time) are drivers for specific devices that are ZigBee or Z-Wave based that connect directly to the Hubitat. I have just a few of these projects.
WADWAZ-1 Contact Sensor - Driver for the very handy WADWAZ-1 Contact Sensor. This Z-Wave sensor has good range and a tamper switch but most importantly has 2 contact switches. The normal internal one every contact switch has but also a set of screw terminals for another external contact switch. Typically meant for wide windows that open site/side (as opposed to the typical up/down) but it can be used for just about anything.
SecurifiSensors - Provides a driver that handles just about every type of ZigBee sensor that Securifi currently has available.
Tuya ZigBee Air Sensor - I really cannot recommend buying one of these. I did, I wrote a driver for it which works... but the device itself is not very high quality, not very controllable, and just loves to spam the Hubitat with excessive data.
Finally, there are some that do not have full projects that are not as updated or in demand anymore (mostly due to the manufacturers not making them) I will still provide direct links for. These devices still work and so will the drivers, but there are probably newer alternatives you might want to look into.
OSRAM's Lightify 4 Button Switch - Handles this very reasonably priced 4 button switch.
Securifi's Almond Click - Handles the Almond Click button that Securifi made.
Securifi KeyFob - Handles the Keyfob. As a note, the "*" button does not report normally like the other 3. So this driver has a workaround to detect it indirectly. If NO button (including *) is pressed for ~10 seconds, then the * is pressed, the driver can detect it.
