v2.0.0b3 #59
Closed
mvdwetering
announced in
Announcements
Replies: 1 comment
-
v2.0.0 has been released, please continue disussion there |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Breaking Changes
media_player
entityRead the changes section below and/or README.md for more details.
Changes
Before this version the functionality of the Philips Hue Play HDMI Sync Box was all exposed through one single mediaplayer entity. Several features of the media_player were abused to control things on the box. E.g. brightness was controlled by the volume slider. While this initially seemed like a good idea (easy controls on the dashboard and only one entity to implement) this turned out to be confusing and quite limiting in the long run. Next to that the way the integration was built did not allow for more entities so it was not possible to extend it.
The 2.0.0 version is a complete rewrite to allow for multiple entities and modernize the integration in general. Having multiple entities should make it clear what the function of the entity is. And because they are standard Home Assistant entities like
switch
,number
,select
andsensor
they are familiar to most users already.With the rewrite several features are added that are nowadays standard for integrations, but did not exists back when this integration was created like select entity, reauth, diagnostics, easy enabling of logging and translations for everything. This rewrite also addresses most open issues and feature requests.
Since the integration is now using the latest and greatest Home Assistant features the minimum Home Assistant Core version is now 2023.8.0.
Note that no functionality is lost. It just moved to a different place.
To start with, the yaml configuration option has been removed. It has not been used in a long time. If you still have the
huesyncbox:
entry inconfiguration.yaml
it should be removed.With the rewrite the existing
media_player
entity has been removed and replaced with several new entities.Below is a table with the new and old situation.
set_brightness
service. Note that the range is now a percentage (1-100%) to match the values in the Hue app. It used to be a range from 0 to 1hdmi1-4_status
attributes of mediaplayerbridge_connection_state
attribute of mediaplayerbridge_unique_id
attribute of mediaplayerWith the transition to the new entities most custom services that were offered became obsolete as native Home Assistant services of the entities can be used now. The table links to the documentation of the standard Home Assistant services that can be used instead.
The service can still be used to set multiple states at once for covenience so you don't have to worry about the order in which to set them.
Full Changelog: v1.23.0...v2.0.0b3
This discussion was created from the release v2.0.0b3.
Beta Was this translation helpful? Give feedback.
All reactions