Open yolkhovyy opened 4 hours ago
Hi @yolkhovyy
zigbee2mqtt
is a custom component, which is not maintained by the HA core project. Please report your issue to the maintainer or in the source repository of this custom component.
Thx 👍
This is an exception in home assistant
On Sat, Oct 19, 2024, 22:44 Michael @.***> wrote:
Hi @yolkhovyy https://github.com/yolkhovyy zigbee2mqtt is a custom component, which is not maintained by the HA core project. Please report your issue to the maintainer or in the source repository of this custom component. Thx 👍
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424201806, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5H64OHULQGGJM3K66LZ4LABLAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIYDCOBQGY . You are receiving this because you were mentioned.Message ID: @.***>
All devices on zigbee2mqtt are gone, see the screenshot.
What version of Home Assistant Core has the issue? core-2024.10.3
What was the last working version of Home Assistant Core? No response
based on this, i've to guess that you did not have updated HA right before the issue happens, therefore it is most likely an issue elsewhere, which causes these issues.
It was 2022-something
On Sat, Oct 19, 2024, 23:11 Michael @.***> wrote:
All devices on zigbee2mqtt are gone, see the screenshot.
What version of Home Assistant Core has the issue? core-2024.10.3
What was the last working version of Home Assistant Core? No response
based on this, i've to guess that you did not have updated HA right before the issue happens, therefore it is most likely an issue elsewhere, which causes these issues.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424212619, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5D5HFZ5CPSQEWE2AJDZ4LDHZAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIYTENRRHE . You are receiving this because you were mentioned.Message ID: @.***>
It was 2022-something, then it stopped working, all devices on zigbee2mqtt were gone, then I upgraded to 2024, did not help, observing this exception in HA
If I try 2022 again - the same exception
On Sat, Oct 19, 2024, 23:16 Yuriy Olkhovyy @.***> wrote:
It was 2022-something
On Sat, Oct 19, 2024, 23:11 Michael @.***> wrote:
All devices on zigbee2mqtt are gone, see the screenshot.
What version of Home Assistant Core has the issue? core-2024.10.3
What was the last working version of Home Assistant Core? No response
based on this, i've to guess that you did not have updated HA right before the issue happens, therefore it is most likely an issue elsewhere, which causes these issues.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424212619, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5D5HFZ5CPSQEWE2AJDZ4LDHZAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIYTENRRHE . You are receiving this because you were mentioned.Message ID: @.***>
It was 2022-something
do you really mean an 2 years older release?
If I try 2022 again - the same exception
so maybe the issue is not home-assistant caused?
It's an exception in home assistant, what do you mean with somewhere else?
On Sat, Oct 19, 2024, 23:56 Michael @.***> wrote:
It was 2022-something
do you really mean an 2 years older release?
If I try 2022 again - the same exception
so maybe the issue is not home-assistant caused?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424231135, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5DRKEWAT73SBOI4JMDZ4LIQTAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIZTCMJTGU . You are receiving this because you were mentioned.Message ID: @.***>
Sure, this is an exception, which is raised by HA, but you are using a custom component zigbee2mqtt
which sends data trough the mqtt
integration into HA - so if these data has changed or are malformed or what else, it might cause HA to raise this exceptions. Based on the error message string value is None for dictionary value @ data['name']
i strongly guess, these send data are malformed or incomplete.
Since we still did not finally clarify, if this behavior is directly related to any HA core update or an update of this custom component, everything here is just guessing, which is not conducive.
I tried older versions of zigbee2mqtt, all the way to 1.30.2 - the same exception
If this of any help - things broke when I enabled one of hidden entities in a ZigBee device.
On Sun, Oct 20, 2024, 00:10 Michael @.***> wrote:
Sure, this is an exception, which is raised by HA, but you are using a custom component zigbee2mqtt which sends data trough the mqtt integration into HA - so if these data has changed or are malformed or what else, it might cause HA to raise this exceptions. Based on the error message string value is None for dictionary value @ data['name'] i strongly guess, these send data are malformed or incomplete. Since we still did not finally clarify, if this behavior is directly related to any HA core update or an update of this custom component, everything here is just guessing, which is not conducive.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424235180, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5DPB5U6FN3DIUXZGLTZ4LKENAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIZTKMJYGA . You are receiving this because you were mentioned.Message ID: @.***>
I tried older versions of zigbee2mqtt, all the way to 1.30.2 - the same exception
ok, so the issue is not related to an HA core update?
hings broke when I enabled one of hidden entities in a ZigBee device.
please elaborate this much more detailed - what device exactly?
Sorry, clarification - not 1.30.2, but 1.39.0
On Sun, Oct 20, 2024, 00:19 Yuriy Olkhovyy @.***> wrote:
I tried older versions of zigbee2mqtt, all the way to 1.30.2 - the same exception
If this of any help - things broke when I enabled one of hidden entities in a ZigBee device.
On Sun, Oct 20, 2024, 00:10 Michael @.***> wrote:
Sure, this is an exception, which is raised by HA, but you are using a custom component zigbee2mqtt which sends data trough the mqtt integration into HA - so if these data has changed or are malformed or what else, it might cause HA to raise this exceptions. Based on the error message string value is None for dictionary value @ data['name'] i strongly guess, these send data are malformed or incomplete. Since we still did not finally clarify, if this behavior is directly related to any HA core update or an update of this custom component, everything here is just guessing, which is not conducive.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424235180, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5DPB5U6FN3DIUXZGLTZ4LKENAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGIZTKMJYGA . You are receiving this because you were mentioned.Message ID: @.***>
at the moment, i'm still on the point as already stated in https://github.com/home-assistant/core/issues/128802#issuecomment-2424201806 - you've to report this issue to the maintainers/project/repository of zigbee2mqtt
could you please elaborate what issue is supposed to be reported to zigbee2mqtt?
On Sun, Oct 20, 2024, 00:28 Michael @.***> wrote:
at the moment, i'm still on the point as already stated in #128802 (comment) https://github.com/home-assistant/core/issues/128802#issuecomment-2424201806
- you've to report this issue to the maintainers/project/repository of zigbee2mqtt
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424247788, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5CWOSP62HRT5X5UJ4TZ4LMHBAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGI2DONZYHA . You are receiving this because you were mentioned.Message ID: @.***>
If this helps, please see attachment
On Sun, Oct 20, 2024, 00:41 Yuriy Olkhovyy @.***> wrote:
could you please elaborate what issue is supposed to be reported to zigbee2mqtt?
On Sun, Oct 20, 2024, 00:28 Michael @.***> wrote:
at the moment, i'm still on the point as already stated in #128802 (comment) https://github.com/home-assistant/core/issues/128802#issuecomment-2424201806
- you've to report this issue to the maintainers/project/repository of zigbee2mqtt
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128802#issuecomment-2424247788, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUR5CWOSP62HRT5X5UJ4TZ4LMHBAVCNFSM6AAAAABQHYSJTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGI2DONZYHA . You are receiving this because you were mentioned.Message ID: @.***>
The problem
All devices on zigbee2mqtt are gone, see the screenshot.
Log, when renaming a device in zigbee2mqtt (1.40.2):
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
MQTT
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
All devices on zigbee2mqtt are gone, reinstalling MQTT integration did not help