-
Notifications
You must be signed in to change notification settings - Fork 21
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
Even after deleting Zigbee end point I can see the Temperature and Humidity sensor in z2mqtt expose tab. #13
Comments
If you want to change the endpoint/cluster config, you need at least to remove the device from z2m and join again. |
Thanks for your prompt reply and apologies for my limited knowledge in this area. I have remove the temp sensor and deleted the zigbee endpoint/cluster for Temperature sensor, removed the device from zigbee2mqtt, restarted zigbee2mqtt, deployed the new Yaml to esp32 c6 board and added the device again to zigbee2mqtt. Still I can see the Temperature and Humidity entry in zigbee2Mqtt. Please find the snap shot and Yaml config below.
Thanks in advance for you help and time. |
Some ideas (didn't try):
|
After couple of restarts and removing and adding device for at least 10 times it worked :) I could alter the cluster but now I am getting other error
This is my yaml
Just trying to publish cpu frequency. |
No idea about CPU freq, but if you just want to report something you could for example report free heap size with the debug component: https://esphome.io/components/debug |
|
Hi,
No matter what I do, I cannot remove the temperature sensor from zigbee2mqtt expose tab.
I deleted "device_type: TEMPERATURE_SENSOR" from the zigbee attribute but nothing changes at ZIgbee2MQTT coordinator.
My ZIgbee2MQTT coordinator version is 1.37.1.
I am trying to add mmwave sensor LD2450 but no success. I can't even add the ESP CPU speed attribute at zigbee. Please find the sensor config and zigbee config below. Also, I tried to use device type as TEMPERATURE_SENSOR itself. Please suggest what am I doing wrong.
Thanks for your help.
The text was updated successfully, but these errors were encountered: