0.0.6

What's Changed

• Edit activity by @pathofleastresistor in #12
• fix duplicate entity by @pathofleastresistor in #13
• Support datetime format coming from the client by @pathofleastresistor in #14

Full Changelog: 0.0.5...0.0.6

0.0.6b3

Improve support for new features and activity manager card

0.0.6b2

Fixing an issue where duplicate entities were being created.

0.0.6b1

BREAKING CHANGE

• Anyone relying on service calls to update and remove entities will need to update to using entity_id instead of the previous {name, category}. This change make this component more consistent with the rest of HA.
• Anyone calling "activity_manager.update_activity" will need to explicitly set now: true to update the last_completed to now. This was added to allow other fields of an activity to be updated without changing the last_completed value.

Features:

• Set last_completed when adding an entity through a service_call
• Set last_completed, category, frequency, icon of an activity when updating it.

Sensor Entities! Breaking changes

PLEASE READ before upgrading. There are major breaking changes with 0.0.5.

• Entities are now associated to the integration. This does mean the entity domain moves from activity_manager to sensor. If you are doing any templating, automation, etc., you will need to update them.

Example:
If you have a condition for an automation to check if something is due, you previously would have done:
{{ states.activity_manager | selectattr('attributes.category', 'equalto', 'Workout') | map(attribute='state') | map('as_datetime') | reject(">", now()) | list | count > 0 }}

Now you would do:
{{ states.sensor | selectattr('attributes.integration', 'eq', 'activity_manager') | selectattr('attributes.category', 'equalto', 'Workout') | map(attribute='state') | map('as_datetime') | reject(">", now()) | list | count > 0 }}

What's Changed

• Frequency ms by @pathofleastresistor in #7
• Migrate to sensor entities by @pathofleastresistor in #10

New Contributors

• @pathofleastresistor made their first contribution in #7

Full Changelog: 0.0.4...0.0.5

Moving to Sensor Entities

Another breaking change! The component is removing the "activity_manager.*" entities and moving to sensor entities. With this change, the entities are now associated to the integration. The state and attributes should remain as-is.

Supporting more granular frequencies

You can have frequencies less than a day.

(Beta) Moving to freqency_ms

Moving to frequency_ms that would allow frequencies more precise than just day.

Add support for proper timezone reporting

0.0.3

Add timezones to date time objects

0.0.2

Full Changelog: 0.0.1...0.0.2