-
-
Notifications
You must be signed in to change notification settings - Fork 400
[shelly] Update breaking changes for 5.1 #1767
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
base: main
Are you sure you want to change the base?
Conversation
Also thing type shellsplushtg3 was renamed to shellyplusht Signed-off-by: Markus Michels <markus7017@gmail.com>
|
Please merge before release. |
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
|
@markus7017 @lsiepel the corresponding PR is not merged, not sure if I understood all the discussions correctly. |
|
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 |
|
openhab/openhab-addons#18943 is now merged and will be included in 5.1. |
jlaur
left a comment
There was a problem hiding this 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
Signed-off-by: Markus Michels <markus7017@gmail.com>
jlaur
left a comment
There was a problem hiding this 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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
| 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] |
There was a problem hiding this comment.
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:
openhab-distro/distributions/openhab/src/main/resources/bin/update.lst
Lines 177 to 180 in 2122c97
| [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. |
Also thing type shellsplushtg3 was renamed to shellyplusht
relates to openhab-addons PR 18943