Skip to content
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

[openwebnet] fixed generic_device thing-type, improved refresh at boot #12489

Merged
merged 1 commit into from
Mar 20, 2022

Conversation

mvalla
Copy link
Contributor

@mvalla mvalla commented Mar 18, 2022

Fixed generic_device thing-type (used when a BTicino device cannot be recognized) and added a time limit to devices refresh at boot/reconnect.

…evices refresh at boot

Signed-off-by: Massimo Valla <mvcode00@gmail.com>
@mvalla mvalla added the bug An unexpected problem or unintended behavior of an add-on label Mar 18, 2022
@mvalla mvalla requested a review from lolodomo March 18, 2022 13:52
@lolodomo
Copy link
Contributor

Changing a thing type is a breaking change for any user that already defined these things. Do you really want to change that? In this case, a specific notr in the 3.3 release notes would be expected.

@mvalla
Copy link
Contributor Author

mvalla commented Mar 19, 2022

Changing a thing type is a breaking change for any user that already defined these things.

actually this is a thing-type never used practically: it’s just used to highlight not recognized devices during discovery (where the right name generic_device was already correctly set programmatically when creating the inbox entry for a unrecognized device).

Formally is a breaking change, but practically no one should have never used (and will never use) this thing-type as it’s useless from manual configuration perspective. It's also not documented in the README supported Things section.

Should one user have used it in file configuration, it would not work anyway as current name is not aligned with the rest of the code, so practically it’s a bug.

However if you prefer I can put a breaking change Notice.

Copy link
Contributor

@lolodomo lolodomo left a comment

Choose a reason for hiding this comment

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

LGTM

@lolodomo
Copy link
Contributor

However if you prefer I can put a breaking change Notice.

Not necessary if you think it adds no value for the final user.

@lolodomo
Copy link
Contributor

Before I merge, I read that in your description:

Removed a line from README.

What I see is no line removed but a blank line added.
I am not sure it is necessary to mention it.

@mvalla
Copy link
Contributor Author

mvalla commented Mar 20, 2022

ok so no breaking change notice (should the label be removed then?). I removed the (wrong) mention to the README. Thanks!

@lolodomo lolodomo merged commit 5f9096b into openhab:main Mar 20, 2022
@lolodomo lolodomo added this to the 3.3 milestone Mar 20, 2022
@lolodomo
Copy link
Contributor

ok so no breaking change notice (should the label be removed then?)

I think we can keep the label. As you said: "Formally is a breaking change".

@mvalla mvalla deleted the openwebnet-3.3-refresh branch March 20, 2022 15:57
NickWaterton pushed a commit to NickWaterton/openhab-addons that referenced this pull request Apr 27, 2022
…evices refresh at boot (openhab#12489)

Signed-off-by: Massimo Valla <mvcode00@gmail.com>
Signed-off-by: Nick Waterton <n.waterton@outlook.com>
andan67 pushed a commit to andan67/openhab-addons that referenced this pull request Nov 6, 2022
…evices refresh at boot (openhab#12489)

Signed-off-by: Massimo Valla <mvcode00@gmail.com>
andrasU pushed a commit to andrasU/openhab-addons that referenced this pull request Nov 12, 2022
…evices refresh at boot (openhab#12489)

Signed-off-by: Massimo Valla <mvcode00@gmail.com>
Signed-off-by: Andras Uhrin <andras.uhrin@gmail.com>
psmedley pushed a commit to psmedley/openhab-addons that referenced this pull request Feb 23, 2023
…evices refresh at boot (openhab#12489)

Signed-off-by: Massimo Valla <mvcode00@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on (potentially) not backward compatible
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants