-
-
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
[mqtt.homeassistant] handle null component name #15427
[mqtt.homeassistant] handle null component name #15427
Conversation
d3d46d7
to
0681d6b
Compare
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 fix the conflict, otherwise LGTM
channels from such components will not have a group. this is now done by zigbee2mqtt for the "default" component of a device, such as the light. HASS encourages this as of release 2023.8 Signed-off-by: Cody Cutrer <[email protected]>
Signed-off-by: Cody Cutrer <[email protected]>
Signed-off-by: Cody Cutrer <[email protected]>
a4667fe
to
87d119e
Compare
rebased and merge conflict resolved |
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 fix! Looking at the call stack of #15634 it seems to be fixed with this PR. If you are able to confirm this, can you link the issue?
...c/main/java/org/openhab/binding/mqtt/homeassistant/internal/component/AbstractComponent.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Cody Cutrer <[email protected]>
Is there something holding up this PR? I was just trying openhab with zigbee2mqtt and this problem prevents any of the lights from functioning. In the meantime, I've downgraded zigbee2mqtt to 1.32.2. For the uninitiated on openhabian:
|
LGTM |
@jlaur: it looks like you already reviewed this PR ? |
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.
LGTM
Due to openhab#15427 and openhab#14839 being developed independently, but merged to main successively Signed-off-by: Cody Cutrer <[email protected]>
Due to #15427 and #14839 being developed independently, but merged to main successively Signed-off-by: Cody Cutrer <[email protected]>
Signed-off-by: Cody Cutrer <[email protected]>
Follow on to openhab#15427 ring-mqtt sends `"name": ""`, not `"name": null` or simply omitting it, so be sure to handle that way as well Signed-off-by: Cody Cutrer <[email protected]>
Follow on to #15427 ring-mqtt sends `"name": ""`, not `"name": null` or simply omitting it, so be sure to handle that way as well Signed-off-by: Cody Cutrer <[email protected]>
This component is fairly non-standard - it doesn't add any channels. Instead, it provides several properties to the thing, and also adds a thing configuration allowing you to trigger an OTA update on a Home Assistant device from MainUI. Signed-off-by: Cody Cutrer <[email protected]> fix compilation problems now that we're rebased on top of openhab#15427 Signed-off-by: Cody Cutrer <[email protected]>
This component is fairly non-standard - it doesn't add any channels. Instead, it provides several properties to the thing, and also adds a thing configuration allowing you to trigger an OTA update on a Home Assistant device from MainUI. Signed-off-by: Cody Cutrer <[email protected]> fix compilation problems now that we're rebased on top of openhab#15427 Signed-off-by: Cody Cutrer <[email protected]>
This component is fairly non-standard - it doesn't add any channels. Instead, it provides several properties to the thing, and also adds a thing configuration allowing you to trigger an OTA update on a Home Assistant device from MainUI. Signed-off-by: Cody Cutrer <[email protected]> fix compilation problems now that we're rebased on top of openhab#15427 Signed-off-by: Cody Cutrer <[email protected]>
* [mqtt.homeassistant] handle null component name channels from such components will not have a group. this is now done by zigbee2mqtt for the "default" component of a device, such as the light. HASS encourages this as of release 2023.8 Signed-off-by: Cody Cutrer <[email protected]>
Due to openhab#15427 and openhab#14839 being developed independently, but merged to main successively Signed-off-by: Cody Cutrer <[email protected]>
Follow on to openhab#15427 ring-mqtt sends `"name": ""`, not `"name": null` or simply omitting it, so be sure to handle that way as well Signed-off-by: Cody Cutrer <[email protected]>
This component is fairly non-standard - it doesn't add any channels. Instead, it provides several properties to the thing, and also adds a thing configuration allowing you to trigger an OTA update on a Home Assistant device from MainUI. Signed-off-by: Cody Cutrer <[email protected]> fix compilation problems now that we're rebased on top of openhab#15427 Signed-off-by: Cody Cutrer <[email protected]>
This component is fairly non-standard - it doesn't add any channels. Instead, it provides several properties to the thing, and also adds a thing configuration allowing you to trigger an OTA update on a Home Assistant device from MainUI. Signed-off-by: Cody Cutrer <[email protected]> fix compilation problems now that we're rebased on top of openhab#15427 Signed-off-by: Cody Cutrer <[email protected]>
* [mqtt.homeassistant] handle null component name channels from such components will not have a group. this is now done by zigbee2mqtt for the "default" component of a device, such as the light. HASS encourages this as of release 2023.8 Signed-off-by: Cody Cutrer <[email protected]> Signed-off-by: Jørgen Austvik <[email protected]>
Due to openhab#15427 and openhab#14839 being developed independently, but merged to main successively Signed-off-by: Cody Cutrer <[email protected]> Signed-off-by: Jørgen Austvik <[email protected]>
Follow on to openhab#15427 ring-mqtt sends `"name": ""`, not `"name": null` or simply omitting it, so be sure to handle that way as well Signed-off-by: Cody Cutrer <[email protected]> Signed-off-by: Jørgen Austvik <[email protected]>
Channels from such components will not have a group. this is now done by zigbee2mqtt for the "default" component of a device, such as the light. HASS encourages this as of release 2023.8
Fixes #15634