v1.8.3

Bug Fixes

• fix subscription for 2022.3.0b* versions (be1900e), closes #39
  only 2022.3.0b* version of Home Assistant is affected by #39, so this release marked as beta too.

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.8.2

Bug Fixes

• adapt to new topic subscription mechanism in HA 2022.3 (7796cd7)
  HA will change subscription functions signature in 2022.3, so we should be ready for this update.
  With this release the integration for HA versions below 2022.3 will use old way of subscription and switch to new way after HA update.

  You must upgrade the integration if you are going to use HA 2022.3.
  The integration may be updated at any time: before HA upgrade this release will use old mechanism, after upgrade -- will switch to new way automatically.

  Support of HA versions below 2022.3 will be dropped in future.

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.8.1

Don't use this release with HA versions below 2022.3. Check version in wiki for details.

Bug Fixes

• Fix topic subscription for Home Assistant 2022.3.0 (1a8d1e1), closes #38

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.8.0

Bug Fixes

• preload current options in settings dialogue (26be4ce, closes #33)
• reload integration after settings update without Home Assistant restart (fd0b706, closes #33)

Translations

• Polish translation by @Antoni-Czaplicki (d1bc75a, closes #36, 9149619, closes #35)
• Russian translation by @IATkachenko (12d649c, 312af3e)

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.7.0

Features

• set additional attributes for sensor from MQTT event by @IATkachenko (0c7cbd7), closes #30
  Sensor now have additional attributes:

  • timestamp -- value1 from application event. It is usually timestamp of something. Meaning is depended on event. Please check Sleep As Android events documentation for mor details;
  • label -- value2 from application event. It is usually alarm label. You can use this attribute to tell one alarm from another.

  If event have no value<N> field, then attribute will be set to unknown.

• fire events independent on state change by @IATkachenko (95d371f)
  There was no second event if we got two events of same type one after other.
  But it could be, for example, two alarms events with different labels (value2).
  So we should fire HA event for every event from MQTT.

Bug Fixes

• sensor: don't set RAW state if we have JSONDecodeError while processing MQTT message payload by @IATkachenko (dd6f744)

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.7.0-b.0

Features

• set additional attributes for sensor from MQTT event by @IATkachenko (0c7cbd7), closes #30
  Sensor have additional attributes:

  • timestamp -- value1 from application event. It is usually timestamp of something. Meaning is depended on event. Please check Sleep As Android events documentation for mor details;
  • label -- value2 from application event. It is usually alarm label. You can use this attribute to tell one alarm from another.

  If event have no value<N> field, then attribute will be set to unknown.

• fire events independent on state change by @IATkachenko (95d371f)
  There was no second event if we got two events of same type one after other.
  But it could be, for example, two alarms events with different labels (value2).
  So we should fire HA event for every event from MQTT.

Bug Fixes

• sensor: don't set RAW state if we have JSONDecodeError while processing MQTT message payload by @IATkachenko (dd6f744)

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.6.0

Features

• use cache for properties and methods by @IATkachenko (61d9ca8)
• sensor: restore sensor state after HomeAssistant restart by @IATkachenko (49b46ce)

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.5.0

Features

• add show_skip_next_alarm and before_alarm trigger events by @patrickhilker (bcf92a4)

---

Like this integration? Please send us feedback in any suitable way:
emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.4.0

Features

• blueprint: added generator (7d13074)

Blueprint is available now. It allows you configure all actions related to sleep tracking in one automation (I had 6 before). More information is in "Usage" part of README and HomeAssistnat blueprints doc.
If you need some additional features in this blueprint -- please open feature request issue!

drop legacy support

• drop support of HA before 2021.7 (05940a8)
• remove update routine for 1.2.4->1.3.0 (37d2edb)

There is no actions required if you updating HomeAssistant and integration in time. For other cases please check Wiki for additional info.

---

Like this integration? Please send us feedback in any suitable way: emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.

v1.3.1

Bug Fixes

• instance: correctly get device name without %%%device%%% macro (28d73c7), closes #17

---

Do you like this integration? Please send us feedback in any suitable way: emoji at release page, starring project at GitHub , support at or , or just
It will let me know that things that I make is helping other people.