* Only replace a node if the mfgr id / prod id / prod type differ
* Prefer original device name for unready node
* move register_node_in_dev_reg into async_setup_entry
* simplify get_device_id_ext
* Don't need hex ids
* Revert "move register_node_in_dev_reg into async_setup_entry"
This reverts commit f900e5fb0c67cc81657a1452b51c313bccb6f9e1.
* Revert Callable change
* Revert device backup name
* Add test fixtures
* Update existing not ready test with new fixture data
* Check device properties after node added event
* Add entity check
* Check for extended device id
* better device info checks
* Use receive_event to properly setup components
* Cleanup tests
* improve test_replace_different_node
* improve test_replace_same_node
* add test test_node_model_change
* Clean up long comments and strings
* Format
* Reload integration to detect node device config changes
* update assertions
* Disable entities on "value removed" event
* Disable node status sensor on node replacement
* Add test for disabling entities on remove value event
* Add test for disabling node status sensor on node replacement
* disable entity -> remove entity
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
- Fixes RGB/WW/CW controller operating mode not being detected after
a factory reset.
- When the device is factory reset or setup for the first time the operating
mode is reported as 0 and its expected the user will set it in the
Magic Home app. If they skip that step Home Assistant will never be able
to figure out which operating mode the device is using and the CW and WW
channels will not work.
- Changelog: https://github.com/Danielhiversen/flux_led/compare/0.27.41...0.27.42
* add default mode 'auto' for tradfri starkvind air purifier on turn on
This commits fixes the behaviour described in #60122 (purifier couldn't be
started via toggle switch). It adds 'auto' as default mode/fallback for
turning on the starkvind air purifier. This is now the same behaviour the
original app provides.
* Refactor code that set 'auto' as default value for tradfri starkvind on
turn on
* Ensure selected entity is pre-selected in homekit options flow
- We recently adjusted the flow to exclude entities that had
been deleted from breaking the UI validation. We need to include
single entities in the set of all supported entities since
accessory mode has no domain filter
* tweak
* Additional fixes
* small tweak to speed up building the set
* merged fixed version for test branch
Paulus Schoutsen