Add version to manifest

In this release

Manifest

• Add version (now required by home assistant)

Energy usage entities

In this release

Integration

Entities

• Fix issue where dimming a Crownstone results in an error (fixes #7)
• Add support for energy usage entities (closes #2)

Learn more about the behaviour of the energy usage entities here!

Just like the power usage entities, energy usage entities require a Crownstone USB Dongle to work. If you want to get hold of one, contact us!

Note

It is recommended to remove the integration and re-add it after updating, to avoid any problems with previous data.

Add support for Crownstone firmware 5.4.0

In this release

crownstone-uart

• Update to version 1.0.0, fixes #6

Fixed bug where some devices would not show up

Integration

Devices

• Changed device identifier to use the cloud ID which is generally unique. All devices should now be created.

Note

It is recommended to delete the integration and re-add it after updating to avoid getting duplicate items. All cards on the dashboard will stay and should be functional again after doing this, so it is safe!

If you have any problems with the integration, removing it and re-adding will initialize all data from the cloud again so everything should be up-to-date!

Updated unique ID generation

Integration

Entities

• Changed Unique ID's of entities to prevent them from changing in startup

Note

After getting some feedback from an other Home Assistant developer, the unique ID's of the entities are now changed again. The previous version did work well, but could run into problems with the integration didn't create the entities in the exact same order. The ID's should now be fully correct, without any further changes necessary in the future.

For this update it is recommended again to remove the integration and re-add it, otherwise there will be new entities added (with _2 suffix) because the ID's are not the same.

Fixed unique ID bug in entitites

Integration

Configuration

• When trying to setup the Crownstone integration again after it has already been setup once, setup will be aborted with message "there can be only 1 Sphere in a house"

Entities

• Fixed a bug where unique ID's were not correctly generated, which caused that some power usage entities could not be created

Important!

• It is recommended to remove the integration and re-add it after updating, because new ID's are generated for all entities.

Power usage entities & dynamic data updating

The big update for the Crownstone Home Assistant integration is finally here!

Dependency updates

crownstone-lib-python-cloud (1.2.1 -> 1.4.3)

• Added support for multiple logins
• Improved switch command for more consistent switching of multiple Crownstones using the cloud
• Bumped aiohttp to version 3.6.2
• Bug fixes & structure improvements

crownstone-lib-python-sse (1.2.0 -> 1.2.5)

• Updated ping event that caused previous version to break
• Added support for coroutines in the event bus
• Updated command event to now receive events to switch multiple Crownstones
• Bumped aiohttp to version 3.6.2
• Code improvements & bug fixes

crownstone-lib-python-uart (0.7.5 -> 0.7.7)

• Updated crownstone-lib-python-core dependency to 0.5.8, small bug fixes

Integration

Structure

• All data update callbacks are now located in a separate file
• Created devices file with base classes for the devices

Entities

• All entities now have an update callback to update their attributes
• Power usage entities are now added to all Crownstone devices

Crownstone entities

• Removed assumed state property, entities will show switches instead of lightning bolt buttons
• All Crownstone entities now have device state attributes showing the switch method & which abilities are enabled or disabled

Data updating

• Added state reporting. When switching from the app, the new state will be updated in Home Assistant. When using Switchcraft the state will only be updated in Home Assistant when using the Crownstone USB Dongle.
• Fixed bug where users would still remain in their last room when leaving the Sphere (house)
• Fixed bug where the config entry was reloaded for all abilities. It now only reloads when changing the dimming ability
• Added functionality to automatically add or remove Crownstones/Locations from Home Assistant when they were added or removed from the Crownstone app. This will happen instantly and not require a restart or reload
• Added functionality to instantly update Crownstone/Location/User names in Home Assistant when they were updated in the Crownstone app
• Added power usage streaming. There will be new values for each Crownstone every minute

Device triggers

• Made sure presence triggers are only displayed for presence sensors

Known issues

• Creating multiple config entries for Crownstone is not possible yet for now. There are some challenges around unique id creation and the usage of the Crownstone USB, which can only support one config entry at the time

Device triggers now functional

Fixed an issue where device triggers were not loaded. Also added error messages in case the DeviceAutomationConfig is invalid.

The option to create triggers via yaml is removed from the readme. When creating device triggers, a device_id is mandatory. This device_id can only be retrieved through the HA device registry, which is coded in the backend, and will be executed when creating automations via the UI.

Again, if there are any issues, we'd love to hear! Enjoy using your Crownstone presence in HA!

Device trigger config validation

Updated device trigger config validation.

First release of the Crownstone integration for HACS

This is the first release of the Crownstone integration for HACS!

This release contains more functionality than currently in PR to Home Assistant Core.
This functionality is still in beta, and includes:

• Presence detection sensor
• Presence device triggers

Have fun testing, and if there's anything off let us know!