Open vaclavIII opened 4 days ago
azuwis
commented
4 days ago The error message does not come from this lovelace custom card.
I tried to search it and did not find anything useful, can't help without further information.
In fact there is a template Issue: Bug report in https://github.com/azuwis/zigbee2mqtt-networkmap/issues.
vaclavIII
commented
3 days ago Thanks for your quick reply. I'll try to write the details: My hardware is Home Assistant Green, OS Core 2024.9.3., OS 13.1 I installed zigbee2mqtt-networkmap addon via HACS repository, then I wrote the backend definition to "configuration.yaml" by copy + paste from the instructions published on https://github.com/azuwis/zigbee2mqtt-networkmap. Then I defined the frontend by creating a javascript module in the dashboard resources. After restarting HA, the zigbee2mqtt-networkmap add-on behaved normally, it did not report any error. I have now manually created a dashboard tab, and defined a type and entity for it (again, following the instructions). I was a bit puzzled that I couldn't find the "sensor.zigbee2mqtt_networkmap" sensor name (recommended in the instructions) in the HA entity list, however the form for the card doesn't protest in any way and doesn't say that the entity is not defined - it can be saved normally. The resulting tab is empty, and when I try to refresh I get the aforementioned message "The mqtt publish action was not found".
Is this the correct procedure? Should a sensor defined in configuration.yaml as: `mqtt: sensor:
state_topic: zigbee2mqtt/bridge/response/networkmap value_template: >- {{ now().strftime('%Y-%m-%d %H:%M:%S') }}
json_attributes_topic: zigbee2mqtt/bridge/response/networkmap json_attributes_template: "{{ value_json.data.value | tojson }}"` also appear in the HA entity list? If yes, what will be its name? Isn't my incorrect naming of the sensor the cause of the problem? (Sorry for the possibly naive questions - I'm an enthusiastic amateur, and I don't have much experience with programming ...) Thanks for your patience!
azuwis
commented
2 days ago There should be a entity with id sensor.zigbee2mqtt_networkmap like the screenshot bellow:
If not, then your backend setup is not correct, or your whole home-assistant mqtt integration is not setup correctly.
How do you setup zigbee2mqtt for home-assistant?
Check home-assistant.log like mentioned in the issue template, if something is wrong, the log will catch it.
Please create a new issue, read and fill the bug report issue template carefully.
vaclavIII
commented
2 days ago Oh, it's clear! I had no idea that "mqtt" was a separate integration, I assumed it was a native OS feature of Home Assistant. Sorry for the unnecessary query and thank you for your patience!
Best regard
Václav Vaniš
čt 26. 9. 2024 v 11:44 odesílatel Zhong Jianxin @.***> napsal:
There should be a entity with id sensor.zigbee2mqtt_networkmap like the screenshot bellow: Screenshot.2024-09-26.at.17.34.05.png (view on web) https://github.com/user-attachments/assets/60fa2e8e-e2c0-48d8-b853-c29ab0bf3829
If not, then your backend setup https://github.com/azuwis/zigbee2mqtt-networkmap?tab=readme-ov-file#backend-setup is not correct, or your whole home-assistant mqtt integration https://www.home-assistant.io/integrations/mqtt/ is not setup correctly.
How do you setup zigbee2mqtt for home-assistant?
— Reply to this email directly, view it on GitHub https://github.com/azuwis/zigbee2mqtt-networkmap/issues/68#issuecomment-2376464809, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMPCS7X5YAS4QFADB7VB23ZYPJRHAVCNFSM6AAAAABOY3VZTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGQ3DIOBQHE . You are receiving this because you authored the thread.Message ID: @.***>
vaclavIII
commented
1 day ago Hello again,
(and probably for the last time - I don't want to bother you with my ignorance ...). I installed the mqtt integration - I chose the "broker" modus (is that correct?), leaving the default settings completely when installing. I don't dare to change the mqtt settings, as I don't understand the individual parameters at all - I understand only approximately that the broker listens to some traffic and publishes the data somewhere.
The entity "sensor.zigbee2mqtt_networkmap" " has already been registered by Home Assistant - it can be displayed in the entity list. After manually creating the dashboard card, Home Assistant no longer protests, so I judge that it is already addressing the mqtt service somehow. However, the card is still empty and in the "Refreshing" state ...
Any idea what to do? If you have an idea how to diagnose the problem, I would be happy to send you a copy of the settings (perhaps it can be found in some *.yaml file? I am also able to run midnight commander in OS Home Assistant and possibly copy some configuration files ...
Sincerely (and with apologies)
Václav Vaniš
čt 26. 9. 2024 v 11:44 odesílatel Zhong Jianxin @.***> napsal:
There should be a entity with id sensor.zigbee2mqtt_networkmap like the screenshot bellow: Screenshot.2024-09-26.at.17.34.05.png (view on web) https://github.com/user-attachments/assets/60fa2e8e-e2c0-48d8-b853-c29ab0bf3829
If not, then your backend setup https://github.com/azuwis/zigbee2mqtt-networkmap?tab=readme-ov-file#backend-setup is not correct, or your whole home-assistant mqtt integration https://www.home-assistant.io/integrations/mqtt/ is not setup correctly.
How do you setup zigbee2mqtt for home-assistant?
— Reply to this email directly, view it on GitHub https://github.com/azuwis/zigbee2mqtt-networkmap/issues/68#issuecomment-2376464809, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMPCS7X5YAS4QFADB7VB23ZYPJRHAVCNFSM6AAAAABOY3VZTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGQ3DIOBQHE . You are receiving this because you authored the thread.Message ID: @.***>
Card for zigbee2mqtt-networkmap is empty. When I try to refresh I get: "The mqtt publish action was not found". Otherwise everything seems to be set up correctly: in config.yaml I used your default text, when I manually add the Home Assistant tab it does not report a non-existent entity. What is wrong? Thanks for the answer!