这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@markus7017
Copy link
Contributor

@markus7017 markus7017 commented Jul 13, 2025

Also thing type shellsplushtg3 was renamed to shellyplusht
relates to openhab-addons PR 18943

Also thing type shellsplushtg3 was renamed to shellyplusht


Signed-off-by: Markus Michels <markus7017@gmail.com>
@markus7017 markus7017 requested a review from a team as a code owner July 13, 2025 19:10
@markus7017 markus7017 self-assigned this Jul 13, 2025
@markus7017 markus7017 requested a review from wborn July 13, 2025 19:11
@lsiepel
Copy link
Contributor

lsiepel commented Jul 19, 2025

Please merge before release.

Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
@holgerfriedrich
Copy link
Member

@markus7017 @lsiepel the corresponding PR is not merged, not sure if I understood all the discussions correctly.
So how to proceed here?

@lsiepel
Copy link
Contributor

lsiepel commented Jul 19, 2025

Thankfullly you noticed the corresponding PR was net merged yet. Sorry, no it should not be merged, it was postponed. This notice will need to be adapted to 5.1 section @markus7017

@holgerfriedrich holgerfriedrich added the awaiting other PR Depends on another PR label Jul 19, 2025
@jlaur
Copy link
Contributor

jlaur commented Jul 26, 2025

openhab/openhab-addons#18943 is now merged and will be included in 5.1.

@jlaur jlaur removed the awaiting other PR Depends on another PR label Jul 26, 2025
Copy link
Contributor

@jlaur jlaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added note about needed adaptation.

ALERT;MQTT Binding (Home Assistant): All scene components on a device are now exposed as a single String channel, with the scene name or object ID as its value. Existing Items and rules will need to be re-worked.
ALERT;MQTT Binding (Home Assistant): Devices that use custom payloads or states now have that abstracted, so users should only use the default payloads. Rules and UIs may need to be updated for some devices.
ALERT;Shelly Binding: Thing type shellypro2-relay was renamed to shellypro2. Delete the existing thing and re-discover the device.
ALERT;Shelly Binding: Thing type shellypro2-relay was renamed to shellypro2, shellyplushtg3 to shellyplusht. Delete the existing things and re-discover the devices.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must be reverted and a new alert specifically for shellyplushtg3 created in a new 5.1 section.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase, then the 5.1 section will show up below and the text should be added there. Thanks!

@markus7017 markus7017 changed the title [shelly] Update breaking changes for 5.0 [shelly] Update breaking changes for 5.1 Aug 25, 2025
Signed-off-by: Markus Michels <markus7017@gmail.com>
Copy link
Contributor

@jlaur jlaur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see my comments.

ALERT;MQTT Binding (Home Assistant): Thing types and channel IDs for things created prior to 4.3.0 have been significantly restructured and simplified. Items will need to be re-linked. Delete and re-create your Things to also have a simplified Thing Type ID in your Thing IDs.
ALERT;MQTT Binding (Home Assistant): All scene components on a device are now exposed as a single String channel, with the scene name or object ID as its value. Existing Items and rules will need to be re-worked.
ALERT;MQTT Binding (Home Assistant): Devices that use custom payloads or states now have that abstracted, so users should only use the default payloads. Rules and UIs may need to be updated for some devices.
ALERT;Shelly Binding: Thing type shellypro2-relay was renamed to shellypro2. Delete the existing thing and re-discover the device.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not remove existing entry for 5.0.

ALERT;Tibber Binding: All channels have been renamed and restructured into groups. All items will need to be relinked to the new channel IDs.

[5.1.0]
ALERT;Shelly Binding: Thing type shellypro2-relay was renamed to shellypro2, shellyplushtg3 to shellyplusht. Delete the existing things and re-discover the devices.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shellypro2-relay was a breaking change in 5.0, not 5.1.

Suggested change
ALERT;Shelly Binding: Thing type shellypro2-relay was renamed to shellypro2, shellyplushtg3 to shellyplusht. Delete the existing things and re-discover the devices.
ALERT;Shelly Binding: Thing type shellyplushtg3 was renamed to shellyplusht. Delete the existing things and re-discover the devices.

ALERT;Teslascope Binding: The Teslascope binding was refactored in order to support discovery. You now need a bridge device for the Teslascope binding to work.
ALERT;Tibber Binding: All channels have been renamed and restructured into groups. All items will need to be relinked to the new channel IDs.

[5.1.0]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase, this section should not appear as new:

[5.1.0]
ALERT;Automower Binding: Implementation of Automower WebSocket API causes several channels to be removed, changed or added. New channels will need to be linked, existing items need to be adjusted.
ALERT;evcc Binding: Restructured to modular things with auto-discovery of datapoints. You must reconfigure settings, recreate Things, and adjust Items as previous configurations are incompatible.
ALERT;Freebox Binding: The binding has been removed from the distribution. You should consider migrating to the FreeboxOS binding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants