dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.9k stars 498 forks source link

Unable to discover Namron Zigbee Touch thermostat 16A 2.0 (modelid 4512752) #7728

Closed isaksengeir closed 5 months ago

isaksengeir commented 5 months ago

Does the issue really belong here?

Is there already an existing issue for this?

Describe the bug

I am running home assistant with a raspbee2 and deconz add-on. It is unable to discover the New Namron Zigbee Touch thermostat 16A 2.0 (modelid 4512752). I have updated to latest firmware. I believe the issue is related to ddf. Going into /usr/share/deCONZ/devices/namron I see 4512737_thermostat.json that supports modelid 4512737 and 4512738 (https://www.elektroimportoren.no/docs/lib/4512737-FDV-1.pdf). The namron thermostats I recently purchased are quite new and have modelid 4512752 (https://www.elektroimportoren.no/docs/lib/4512752-FDV-1.pdf). I attempted to create a copy of 4512737_thermostat.json and renmed it to 4512752_thermostat.json and changed the and updated the modelid field to 4512752. The rest of the ddf I kept the same. I restarted the gateway and home assistant. But still not able to find the thermostat.

Steps to reproduce the behavior

Purchase the New Namron Zigbee Touch thermostat 16A 2.0 (modelid 4512752). Install home assistant OS on a raspberry pi with a raspbee 2 zigbee gateway and install the deCONZ add-on. Put thermostat in discover mode and follow the instructions from the "add thermostat" in Phoscon.

Expected behavior

Nothing will happen. It will not discover the thermostat.

Screenshots

No response

Environment

deCONZ Logs

No response

Additional context

No response

isaksengeir commented 5 months ago

Sorry, I typed a wrong digit in the model id here when reporting. The correct is 4512752

isaksengeir commented 5 months ago

I just realised that making a new ddf or editing existing ddf inside the container will not survive restarting deCONZ and the container. Thus, the request is probably an update to the container rather than a bug. But, I could be wrong.

Mimiix commented 5 months ago

Hi,

Is it showing in the deconz Gui as hex number?

Can you share a screenshot of your full deconz Gui?

If a device is not supported, it shows as hex number.

isaksengeir commented 5 months ago

Screenshot 2024-04-27 at 12 14 28

Mimiix commented 5 months ago

Screenshot 2024-04-27 at 12 14 28

I see 2 hex named devices on the left top. Can you read the basic clusters and share the screenshots?

isaksengeir commented 5 months ago

Screenshot 2024-04-27 at 16 18 30

isaksengeir commented 5 months ago

Screenshot 2024-04-27 at 16 18 52

Mimiix commented 5 months ago

Hi this is the node info, not basic cluster. In the Wiki of this GitHub is a go-to on how to do it.

isaksengeir commented 5 months ago

Sorry about that. Here are the basic cluster for the two: Screenshot 2024-04-27 at 20 49 20 Screenshot 2024-04-27 at 20 49 55

Mimiix commented 5 months ago

Can you please read them? These are not read. You need to click the read button. It helps if you click the button on the device to wake it up.

isaksengeir commented 5 months ago

@Mimiix they only blink red, so I think it is a dead end. I also believe that these two were there before I purchased the namron zigbee thermostats. Thus, they are simply not showing up here (I think).

Mimiix commented 5 months ago

@Mimiix they only blink red, so I think it is a dead end. I also believe that these two were there before I purchased the namron zigbee thermostats. Thus, they are simply not showing up here (I think).

Are those the same type?

isaksengeir commented 5 months ago

I am not sure what you refer to with same type here. I have purchase a total of 6 namron zigbee thermostats and none of them shows up in phoscon/deconz. My guess would be that they are simply not supported yet and that that this should be an easy fix since the two previous zigbee tech thermostat version integrates well.

Mimiix commented 5 months ago

I am not sure what you refer to with same type here. I have purchase a total of 6 namron zigbee thermostats and none of them shows up in phoscon/deconz. My guess would be that they are simply not supported yet and that that this should be an easy fix since the two previous zigbee tech thermostat version integrates well.

If they are all 6 the same, and you are saying those 2 are the same type you tried to pair: there is no bug here and indeed they are not supported and there is not issue so far.

You need to file a device request with screenshots.

If you can't pair them, you need to ask on the forums for that.

Closing as this is not a bug as described in #5113

isaksengeir commented 5 months ago

First of all, I am grateful for your replies, but I do not understand why you close this issue. I do not think you have understood the problem either. The 2 grey boxes with hex you refer to has nothing to do with this, they were there from before.

The issue is that the newest namron zigbee touch thermostats are not discovered by deconz/phoscon. I thought this was a simple DDF fix, but I have not managed to mace deconz discover the by editing ddf either. Anyway, thank you for taking the time. I hope someone will release a fix for this.

Mimiix commented 5 months ago

First of all, I am grateful for your replies, but I do not understand why you close this issue. I do not think you have understood the problem either. The 2 grey boxes with hex you refer to has nothing to do with this, they were there from before.

The issue is that the newest namron zigbee touch thermostats are not discovered by deconz/phoscon. I thought this was a simple DDF fix, but I have not managed to mace deconz discover the by editing ddf either. Anyway, thank you for taking the time. I hope someone will release a fix for this.

Hi,

If they are not discoverable, it either has something to do with the firmware of the device or with your network. Devices should always show up in deCONZ regardless deCONZ containing support. A DDF can only be used when it is connected to the network.

To find out if its your network or the firmware, i recommend posting on the forums as that is not covered on this github.