Exactly ^^, DDF are future
Just a quick question: Do I need to reset and rejoin all Heiman smoke sensors after installing 2.22.2? Because I updated to this version, but all sensors are still shown as not reachable, even though not greyed out.
Wasnât necessary here for all devices.
Try Test-Alarm button, if you get new data, sensor is still paired with the network. If not - reset repair.
Good luck
I pushed the test button, new data arrives inmediately, but the alarm gets not cleared. So after 30 minutes now it is still shown smoke detected. Pushing the test button should generate an alarm that gets cleared after seconds, or am I wrong?
That is heiman typical.
Has nothing to do with deconz/phoscon.
You have to press test again. Wait and see if state gets cleared. If not wait and press again.
Some devices havenât on/off state, but send a new notification at every detections
Thanks a lot, I will check it (not at home now)
Okay, the state gets cleared after another test alarm and also when reading the zone status after waking up the device.
But the original issue is still in place: after a test alarm, the device status is OK in phoscon GUI. It stays like this for a day or two, and then it goes back to âNot reachableâ. But the devices are still in the network, because another test alert immediately creates the alarm.
The devices are in the network, but for whatever reason phoscon GUI shows them unreachable after few days. A cosmetic issue from my point of view, but maybe fixable 
Are you sure that you have heiman with same model id like mine and you are using DDF?
Perhaps you should post your basic cluster for better help.
By the way - I am still on 22.2.1.
Looks really the same. No clue.
So, back from vacation⌠And I looked @ my phoscon! Phoscon really says ânot reachableâ for all of my heimans.
But I check them with fhem an there they get updated in between 1 and 3 hours. I am watching the timestamp of battery reading!
Just a quick check if this topic is still present for you guys. Some time passed, but my Heiman smoke sensors are still problematic. In general they work fine, alarms are transmitted correctly when pressing the test button, but after a while they appear unreachable in Phoscon, while they are all in the network and alarms are submitted immediately. It also seems the battery state is not processed correctly. All sensors report 100% while they are running 2,5 years now, so 100% left is quite impossible.
I donât found capture from the cluster 0x0001 for this device.
Can you take a look to see if the attribute 0x0021 is working ?
What do you mean with âworkingâ? In my case it has a value of 200 and this value is never changed/updated
Same here.
Phoscon âlostâ sensors again after working for some days, but fire state is always send correctly.
After reading the post from cosmo84, I checked my battery states - same here! Apparently they have a fixed battery value from an older date.
I just compared the DDF of the Heiman smoke sensor with a Heiman carbon monoxide sensor I have too. The battery of the CO sensor gets updated correctly, also pushing the test button gets transmitted correctly. The CO sensor uses this DDF
First thing I noticed is that it is not checked as sleeper, even though it is one. Then there are some differenced in the battery part of the DDFs, but Iâm a beginner in DDFs, I hope someone of you looks at it and says BINGO 
In deconz ? or the API ?
If you double clic on the attribute and press read, it will update the value (the device need to be awaked in same time), it will update too the value in the API in same time, so you can see if it update the status.
Perhaps this attribute is not working on the device, but from what I m reading on Z2M, it need to work like other device.
@cosmo84 the DDF on your capture is not used âDraft statusâ.
This device donât use DDF it use native/legacy code.
I took one sensor and made it awake, then read the battery but it remains at 200. It says âreading doneâ, so it was successful, but without any change to the value. As said, quite impossible for a 2,5 year old battery to be still at 100%.
But itâs from the device itself, else you will have an error message, and this value is updated or grayed, so itâs not a previous memorised one.
When you have done that, it have updated the âlastseenâ for this device in the API ? (for the second issue where devices are marked as unreachable)
No, last seen is also not updated, it says 33 days ago.