-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
[unifi] Fix PoE bug with combination of other data/ports #14060
Conversation
Hilbrand
commented
Dec 24, 2022
- It seems to throw an exception when updating internal cache. It can happen if you have a switch that has both PoE ports and other PoE ports or data in the port override.
- Fixed logout, should be POST instead of GET.
- Fixed typo in channel-type.config.unifi.poeEnable.mode.option.pasv24 should be without appending v.
- Removed compiler warnings.
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.
Thanks for the fixes! Is this related to https://community.openhab.org/t/unifi-oh-3-4-not-working-any-more/142260? If this is a regression from 3.4, should it be cherry-picked into the 3.4 hotfix branch after being merged?
...binding.unifi/src/main/java/org/openhab/binding/unifi/internal/api/dto/UniFiSwitchPorts.java
Outdated
Show resolved
Hide resolved
- It seems to throw an exception when updating internal cache. It can happen if you have a switch that has both PoE ports and other PoE ports or data in the port override. - Fixed logout, should be POST instead of GET. - Fixed typo in channel-type.config.unifi.poeEnable.mode.option.pasv24 should be without appending v. - Removed compiler warnings. Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
a1ed0b1
to
1882fec
Compare
@jlaur It's not a regression specific for 3.4.0. The 3.3.0 version didn't work correctly for PoE in some cases. There was a fix in 3.4.0, but that turned out not to fix all cases. This fix should fix that. |
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.
Thanks!
- It seems to throw an exception when updating internal cache. It can happen if you have a switch that has both PoE ports and other PoE ports or data in the port override. - Fixed logout, should be POST instead of GET. - Fixed typo in channel-type.config.unifi.poeEnable.mode.option.pasv24 should be without appending v. - Removed compiler warnings. Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
- It seems to throw an exception when updating internal cache. It can happen if you have a switch that has both PoE ports and other PoE ports or data in the port override. - Fixed logout, should be POST instead of GET. - Fixed typo in channel-type.config.unifi.poeEnable.mode.option.pasv24 should be without appending v. - Removed compiler warnings. Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
- It seems to throw an exception when updating internal cache. It can happen if you have a switch that has both PoE ports and other PoE ports or data in the port override. - Fixed logout, should be POST instead of GET. - Fixed typo in channel-type.config.unifi.poeEnable.mode.option.pasv24 should be without appending v. - Removed compiler warnings. Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>