-
-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2021.11.0 #58994
Conversation
frenck
commented
Nov 3, 2021
•
edited
Loading
edited
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: Franck Nijhof <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
Co-authored-by: epenet <[email protected]>
* Update PyVicare to 2.x With PyViCare 2.8.1 a breaking change was introduced which required changes on sensor and binary_sensor platforms: - Circuit, Burner and Compressor have been separated out from the "main" device - Multiple circuits and burners allow "duplicate sensors". We add the circuit or burner number as suffix now At the same time the sensors are now created only when available: During entity creation we can check if the value is provided for the user's device. Sensors are not created by heating type anymore but instead the new API structure is reflected, providing device, burner or circuit sensors. For details of breaking changes from PyViCare 1.x to 2.x please see https://github.com/somm15/PyViCare#breaking-changes-in-version-2x * Integrate review comments * variables cleanup * Update unique ids The unique ids shall not depend on the name but on the entity description key (which should not change) and the id of the circuit, burner or device.
* Use DeviceInfo in mqtt * Updates for mypy Co-authored-by: epenet <[email protected]>
* Allow extra keys in MQTT discovery messages * Remove extra keys
Co-authored-by: epenet <[email protected]>
Hi @GitHub-Action, It seems you haven't yet signed a CLA. Please do so here. Once you do that we will be able to review and accept this pull request. Thanks! |
Hey there @bieniu, mind taking a look at this pull request as it has been labeled with an integration ( |
Hey there @atmurray, mind taking a look at this pull request as it has been labeled with an integration ( |
Hey there @Bre77, mind taking a look at this pull request as it has been labeled with an integration ( |
Hey there @Danielhiversen, mind taking a look at this pull request as it has been labeled with an integration ( |
Hey there @shred86, mind taking a look at this pull request as it has been labeled with an integration ( |