NAMRON Thermostat 16A 4512758 failing to register in Phoscon

Phoscon App General Support
1

I Installed a new NAMRON thermostat and am trying to integrate it into Home Assistant running on a Raspberry Pi5 with Rasbee II.

Using Phoscon I tried to pair the device. The thermostat is now on the Zigbee network but did not show up as a device in Phoscon.

When I select deCONZ from Home Assistant I see a new unit with the name 0xB370. I am able to execute commands from deCONZ to the thermostat, like remotely turning the thermostat on and off.

But the thermostat does not show up in Phoscon, and I am not able to see it in Home Assistant.

image
image502×542 79.6 KB

Any advice?

2

As namrom thermostat I m seing in the DDF only model

  "modelid": [
    "4512737",
    "4512738"
  ],

Can try with adding yours

3

Thank you.

I am new to this, but trying to learn. I assume I add my model to that file and somehow upload it to the home assistant operating system. I am not running home assistant in a docker, but the home assistant operation system directly on the PI.

And what should I do if I manage to get the file on the system?

4

I tried to remove the thermostat from the network and add it again. Then something seems to have gone wrong. The manufactorers name has changed and model number.

I did not change these fields manually.

After it changed I went to DDF-editor to change it back. I enter the old name and number and press save with status GOLD. A file called thermostat.json is saved on the raspberry. No error message. I do a hot restart, no error message but it says it restarts a device HZC / RR: Buffer to short… In the log files it seems that all DDF-files on the system are parsed since it lists hundreds of products I don’t have.

When I close DDF-editor no changes have applied to my thermostat.

If I try to open the file I just created I get error message failed to open /data/local/shared…/thermostat.json

I also managed to put your definition file in the same directory, and I get error message “Failed to open” if I try to open it in DDF editor.

image
image502×502 80.7 KB

5

Ok so the manufacture name and the model ID can’t change.
Your issue like more than a c++ buffer overflow issue (it’s a complete string in model identifier), I will share your picture on devs channel.
What is your deconz version ?

You can delete all you have done previously, for HA there is 2 methods

To Create a bundle

  • copy the DDF above to the clipboard
  • paste it into Deconz Toolbox
  • save the generated DDB file
  • use Phoscon’s Device integration page to upload the DDB file to Phoscon
  • re-include the device.

To make the DDF, can use the previous one and add the couple “Manufacture name” + “Model ID” in the good order.

6

My deconz version is 8.5.0.

And I think I already have tried both your suggested ways to get back to normal.

I will try again, first with bundle since I just a few minutes ago deleted the thermostat, added DDF, rebooted and added the thermostat again. Only change was now there is a different hex number as identifier.

7

Can you select the node
Right clic
Edit DDF
Check if you have exactly same model ID/ Manufacture name than on your DDF

  "manufacturername": [
    "NAMRON AS",
    "NAMRON AS",
    "NAMRON AS"
  ],
  "modelid": [
    "4512737",
    "4512738",
    "4512758"
  ],

Or if you have the “magic” issue again ?

8

This is the directory I put the DDF in, but I think it should be another place?
image

9

It does not have a DDF connected with it. So if I edit DDF it is still the same text, no manufacturer og model number.

I will now try to remove it from the network once again, and now create a bundle (last time I tried to copy the DDF).

10

This is what i see when trying to edit DDF.

image
image936×623 88.2 KB

11

I have now tried both methods and the result is the same. There is no DDF and the manifacturer and model is scrambled.

In fact, when the manufactorer first disappeared, was after I tried to upload a bundle one day ago.

12

I can communicate also via REST API from Home Assistant.

image
image1895×292 26.1 KB

13

There is definitively a problem, with your device or with deconz.
Deconz use the model ID and the manufacture name to reconise device, and this is broken ATM on your machine.

I you try to ask just for thoses value, same issue ?

If yes can you share logs when asking for thoses 2 attributes with flags “info”+“info_l2”+“APS” + “APS_l2”

14

Is the log saved somewhere? Then I can copy the text. But here is screenshot. The device now has adress 0x171E so I guess this is where it starts.

image
image795×548 148 KB

image
image792×550 136 KB

image
image792×545 154 KB

image
image791×543 150 KB

15

Yes, I work with copy/paste, so picture …
But it seem fine
aatribute

  • Indication mean from the device
  • Cluster 0x0000
  • CMD = 0x01 = Read attribute response
  • There is the attribute in the request. even I can’t be sure.

So I think it have worked and during this test you had the good Model Identifier ?

16

No. Always the same wrong one.

17

Are manufacturer and model number write protected by hardware? Or is it possible that something har triggered a re-write of these data on the bus and they are now permanently written to the device?

And are there any way to re-write them by me?

18

Nope ^^, they are Read only.

But if you have the issue can you copy/paste thoses 2 lines ?
The “asdu” is long, and I realy need all value to decode it.

19

I managed to make a log. I pressed the read button at around 20:27:31. The adress is 0x171E.

Do you have all debug info you need, or do I have to add other settings for logging?

20

In the first pastebin I clicked the read on the whole card. I made another log where I clicked read a few times on Manufacturer line, and also a few times on Model line.

I started around 21:00 and the adress is 0x171E.