* Fix time to arrival
* Update snapshot
* Freeze time for snapshot
* Fix docstring
* Add available_fn
* Update snapshot
* Dont use variance for full charge
* Remove unrelated changes
* Revert snapshot
* Rename hours_to_datetime
* Enable Bosch Outdoor Siren and Bosch Twinguard QR Codes
These devices contain inside their QR code device specific link keys instead of installation codes. Normally, the link key is generated from the installation code, but in this case we can directly pass the provided link key from QR code to zigpy application controller.
* Replace ZHA deprecated permit_with_key by permit_with_link_key
Convert installation code directly to link key
* Update tests
* formatting
* Add readable state for tesla wall connector
* Add test
* Display raw sensor by default
* Use none instead of unknown
* Remove old state from tests
* Rename raw state to status code
* Test unknown
* Update homeassistant/components/tesla_wall_connector/strings.json
Co-authored-by: Franck Nijhof <git@frenck.dev>
---------
Co-authored-by: Franck Nijhof <git@frenck.dev>
* bump python-matter-server to version 5.3.0
* Add all node related websocket services
* remove open_commissioning_window service
as it wasnt working anyways
* use device id instead of node id
* tests
* add decorator to get node
* add some tests for invalid device id
* add test for unknown node
* add explicit exception
* adjust test
* move exceptions
* remove the additional config entry check for now
to be picked up in follow up pR
* add config flow
* fix tests
* adjust and fix tests
* fix tests
* config_zones as fixture
* add config flow tests
* use coordinator.async_config_entry_first_refresh
* use entry.entry_id for hass.data
* fix doc string
* remove unused unit_of_measurement string key
* don't store friendly_name, just use self.name
* abort on matching entiry
* break out legacy setup into seperate function
* make tracked entites required
* move _asnyc_setup_legacy to module level
* use zone name as config entry title
* add entity_used_in helper
* check entry source if imported
* create repair issue for removed tracked entities
* separate state change from registry change event handling
* migrate unique ids after tracked entity renamed
* use full words for the variable names
* use defaultdict
* add test
* remove unnecessary if not in check
* use unique_id of tracked entity
* use the entity registry entry id
* Apply suggestions from code review
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
---------
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
* stub out zha update entity
* update matcher
* updates based on assumptions / conversation
* hook into current installed version
* post rebase cleanup
* incorporate zigpy changes
* fix async_setup_entry
* fix sw_version
* make ota work with config diagnostic match
* fix version format
* sync up with latest Zigpy changes
* fix name attribute
* disable ota providers for tests
* update device list
* review comment
* add current_file_version to Ota ZCL_INIT_ATTRS
* updates to update and start tests
* get installed version from restore data
* better version handling
* remove done todo notes
* reorganize test
* move image notify to cluster handler
* add test for manual update check
* firmware update success test
* coverage
* use zigpy defs
* clean up after rebase
* bump Zigpy
* cleanup from review comments
* fix busted F string
* fix empty error
* move inside check
* guard zigbee network from bulk check for updates
* Correct handling of power_factor ElectricalMeasurement attribute
The Zigbee Cluster Library defines PowerFactor as an int8 with value supported from -100 to 100.
Currently the zha sensor handler attempts to apply the ac_power_divisor and ac_power_multiplier formatters against the attribute value, the spec outlines that this should not be the case.
The impact of the current code is that quirks not using the default values of 1 are multiplying/dividing
power and power factor values prior to updating the cluster attribute.
This results in either a non-conformant power_factor e.g. the value was multiplied by 10 so that an ac_power_divider of 10 could be used, or the power readings sacrificing a point of measurement for lower readings.
Two quirks currently use this workaround:
* ts0601_din_power.py
* ts0601_rcbo.py
* Update ZHA Metering formatter to perform None check on _div_mul_prefix
To address feedback:
https://github.com/home-assistant/core/pull/107641#discussion_r1447547054
* _div_mul_prefix needs self reference
* Simplify None check for _div_mul_prefix
Co-authored-by: Joakim Plate <elupus@ecce.se>
* Updates to formatting and CI test typing fix
* Use ' | ' in place of Union
* Add tests for power_factor sensor
---------
Co-authored-by: Joakim Plate <elupus@ecce.se>
J. Nick Koston
TheJulianJES
Ernst Klamer
Joost Lekkerkerker
Raman Gupta
Brett Adams
Erik Montnemery
Tucker Kern
G Johansson
Steven B
Bram Kragten
Jan Rieger
Joakim Sørensen
Paul Strawder
Paul BotteinandFranck Nijhof
Robert Resch
Jeroen van Ingen Schenau
Jan-Philipp Benecke
Marcel van der Veldt
Simone Chemelli
Jan Bouwhuis
MichaelandMartin Hjelmare
Brandon Rothweiler
Mandar PatilandJoost Lekkerkerker
Christopher FennerandRobert Resch
Josh Pettersen
David F. Mulcahey
Caius-Bonus
Duco Sebel
JackandJoakim Plate