Releases: libdyson-wg/ha-dyson
v1.1.0
v1.0.1
What's Changed
Quick explanation of the "camera" thing
Part of the features provided by MyDyson is a live cleaning map view of your 360 Eye robot vacuum (if you're one of the six people who own that device). For Home Assistant, this video feed is created via a "camera" entity. The MyDyson account setup in Home Assistant loads the camera platform to support this possible feature.
Full Changelog: v1.0.0...v1.0.1
Contributors
Assets 2
v1.0.0
"Dyson Cloud" and "Dyson Local" are now just "Dyson"
For more information as to why the projects were merged, check this discussion: #49
This new release keeps the same offline-only core from when it was called "Dyson Local", but now incorporates the cloud functionality under a "MyDyson" entity. The MyDyson account setup is still optional for most devices, the same as the Dyson Cloud from the previously-separate repository entities. This lets us support devices which require a MyDyson account for setup (released in Summer 2021 and later). All communication with your Dyson Devices is still using the same MQTT over LAN. The MyDyson account is just to help with initial device configuration (and to provide the cleaning maps for the 360 Eye vacuum).
With the MyDyson functionality merged into this repository, we may consider adding more cloud-specific functionality to it. But the plan is to always treat MyDyson as an opt-in feature, and be offline-first with all core features.
What's Changed
- Set up hassfest for testing by @dotvezz in #46
- Combine Cloud and Local versions of the Dyson Integration by @dotvezz in #50
- Include relevant links for README badges by @dotvezz in #51
- Moving camera.py to dyson_local so it can be configured by @dotvezz in #52
Full Changelog: v0.22.1...v1.0.0
Contributors
Assets 2
v1.0.0-beta2
"Dyson Cloud" and "Dyson Local" are now just "Dyson"
There is an open discussion about whether to permanently go in this direction: #49
This new release keeps the same offline-only core from when it was called "Dyson Local", but now incorporates the cloud functionality under a "MyDyson" entity. The MyDyson account setup is still optional for most devices, the same as the Dyson Cloud from the previously-separate repository entities. This lets us support devices which require a MyDyson account for setup (released in Summer 2021 and later). All communication with your Dyson Devices is still using the same MQTT over LAN. The MyDyson account is just to help with initial device configuration (and to provide the cleaning maps for the 360 Eye vacuum).
With the MyDyson functionality merged into this repository, we may consider adding more cloud-specific functionality to it. But the plan is to always treat MyDyson as an opt-in feature, and be offline-first with all core features.
What's Changed
- Set up hassfest for testing by @dotvezz in #46
- Combine Cloud and Local versions of the Dyson Integration by @dotvezz in #50
- Include relevant links for README badges by @dotvezz in #51
- Moving camera.py to dyson_local so it can be configured by @dotvezz in #52
Full Changelog: v1.0.0-beta...v1.0.0-beta2
Contributors
Assets 2
v1.0.0-beta
"Dyson Cloud" and "Dyson Local" are now just "Dyson"
There is an open discussion about whether to permanently go in this direction: #49
This new release keeps the same offline-only core from when it was called "Dyson Local", but now incorporates the cloud functionality under a "MyDyson" entity. The MyDyson account setup is still optional for most devices, the same as the Dyson Cloud from the previously-separate repository entities. This lets us support devices which require a MyDyson account for setup (released in Summer 2021 and later). All communication with your Dyson Devices is still using the same MQTT over LAN. The MyDyson account is just to help with initial device configuration (and to provide the cleaning maps for the 360 Eye vacuum).
With the MyDyson functionality merged into this repository, we may consider adding more cloud-specific functionality to it. But the plan is to always treat MyDyson as an opt-in feature, and be offline-first with all core features.
What's Changed
- Set up hassfest for testing by @dotvezz in #46
- Combine Cloud and Local versions of the Dyson Integration by @dotvezz in #50
Full Changelog: v0.22.1...v1.0.0-beta
Contributors
Assets 2
v0.22.1
What's Changed
Special thanks
Thanks to @Anto79-ops for spending so much time helping investigate the HCHO sensors in the devices. His contribution to the effort was beyond significant, and this fix would have been impossible without his patience and diligence. #4 partially documents the insanity we both fell into while trying to figure this out, and it will be my honor to finally mark that issue closed.
A note on the sensor entity name:
If you have any existing Formaldehyde devices, you will notice that this release creates a new sensor entity named "HCHO". There are a few reasons for this:
- For your convenience: your old "Formaldehyde" sensor entity has been collecting data with no recorded unit until now, and conversion to the new mg/m3 unit is impossible.. If we kept it on the same sensor entity, it will cause issues in Home Assistant which would require manual correction on your part.
- To be consistent with Dyson's documentation, Dyson's Mobile App, and your device itself. All of these display "HCHO" as the sensor label, including the LCD screen built into the device itself.
You may choose to keep the dead Formaldehyde sensor entity, or you may also choose to remove it by visiting https://my.home-assistant.io/redirect/developer_statistics/ and searching for "formaldehyde"
Full Changelog: v0.22.0...v0.22.1
Contributors
Assets 2
v0.22.0
What's Changed
- Finally using correct units for Formaldehyde by @dotvezz in #40
- Use HCHO as the Formaldehyde sensor entity name by @dotvezz in #41
Special thanks
Thanks to @Anto79-ops for spending so much time helping investigate the HCHO sensors in the devices. His contribution to the effort was beyond significant, and this fix would have been impossible without his patience and diligence. #4 partially documents the insanity we both fell into while trying to figure this out, and it will be my honor to finally mark that issue closed.
A note on the sensor entity name:
If you have any existing Formaldehyde devices, you will notice that this release creates a new sensor entity named "HCHO". There are a few reasons for this:
- For your convenience: your old "Formaldehyde" sensor entity has been collecting data with no recorded unit until now, and conversion to the new mg/m3 unit is impossible.. If we kept it on the same sensor entity, it will cause issues in Home Assistant which would require manual correction on your part.
- To be consistent with Dyson's documentation, Dyson's Mobile App, and your device itself. All of these display "HCHO" as the sensor label, including the LCD screen built into the device itself.
You may choose to keep the dead Formaldehyde sensor entity, or you may also choose to remove it by visiting https://my.home-assistant.io/redirect/developer_statistics/ and searching for "formaldehyde"
Full Changelog: v0.21.0...v0.22.0
