v0.4.14

This release adds initial support for security keypads and alarms / sirens.

Security keypads will end up as one or more entities in Home Assistant. At the very least there will be an alarm control panel, and there may also be other sensors (battery, temperature, etc.).

Standalone sirens, and keypads that also support the Alarm capability, will have an associated switch device to turn the alarm on and off.

Security keypads, like locks, provide services to set and delete codes, and to set the code length.

Alarms provide services to turn on the the strobe and siren separately (if the alarm supports both functions). Turning an alarm "on" will activate both the strobe and light, while turning it off will disable both the strobe and siren.

v0.4.13

This release updates the hubitatmaker dependency, which is required for the updated lock support in v0.4.12.

v0.4.12

This release improves support for locks. Lock entities will now emit an event when unlocked with a code, with the event's "value" attribute set to the name of the code used:

{
    "event_type": "hubitat_event",
    "data": {
        "device_id": "2086",
        "device_name": "Virtual Lock",
        "attribute": "code_name",
        "value": "Family",
        "description": "Virtual Lock was unlocked by Family"
    }
}

The get_code service has been removed. Instead, all codes are available through the codes state attribute on a lock.

v0.4.11

This release fixes an issue with "cover" devices (door openers and window shades) where multiple duplicative cover entities could be created for the same physical device.

v0.4.10

This release adds support for fans, courtesy of @spectre3ooo (#23).

The code has also been cleaned up (typing and linking issues), and some additional dev tooling has been added to make future contributions easier (thanks to @spectre3ooo for discovering several holes in the existing build process).

v0.4.9

This release allows temperature units to be specified for an instance of the integration, ensuring that the integration will properly interpret temperature sensor data from Hubitat. The units specified for the integration should be set to the same units used by the Hubitat hub. The integration defaults to Fahrenheit.

v0.4.8

This release adds initial support for locks. It's "initial" because I don't own any locks, any my only testing has been against a Hubitat virtual lock. 😁

Lock entities support the basic lock and unlock functions.

User code management is handled through 4 new services:

• clear_code -- delete the user code at a given position
• get_code -- get the user code at a specific position
• set_code -- set the code at a specific position to a given value, and with an optional name
• set_code_length -- set the allowable length of user codes

You can try out the services in the Developer Tools page in Home Assistant.

v0.4.7

This release adds support for a couple new device types:

• Presence sensors
• Cover devices (doors, garage doors, and window shades)

It also includes a workaround for button controllers that don't advertise how many buttons they have.

v0.4.6

This release fixes a regression introduced in 0.4.5 that prevented the integration from installing properly.

v0.4.5

This release fixes an issue where devices weren't being created in Home Assistant for Hubitat devices that were only event emitters. (#14)