Unsupported Device registration creates "NULL"

[brientim]

Does the issue really belong here?

• [x] I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this? No

• [x] I have searched the existing issues and there is none for the bug at hand

Describe the bug

When registering a new devices or devices with incomplete Device Definition Files (DDF), the defaulted value is "Null" and this was partly addressed in #8198 .

Since release 2.30_00 other issues have been discovered and this has impacted on 3rd party integration and a number of devices as detailed in #8187 and #8202.

This issue is also encountered when registering new unsupported devices and other attributes, "lastannounced", "ddf_hash", "swversion" and "zonetype" as per the example below.

{
        "capabilities": {
            "sleeper": true
        },
        "config": {
            "battery": 100,
            "on": true,
            "reachable": true
        },
        "ddf_hash": null,
        "ddf_policy": "latest_prefer_stable",
        "etag": "60c072f7b7332dee6d9edb972ce0fce2",
        "lastannounced": null,
        "lastseen": "2025-05-04T01:55Z",
        "manufacturername": "_TZE200_n8dljorx",
        "modelid": "TS0601",
        "name": "TS0601 (2)",
        "nwkaddress": 40837,
        "state": {
            "lastupdated": "2025-05-04T01:56:05.405",
            "open": true
        },
        "swversion": null,
        "type": "ZHAOpenClose",
        "uniqueid": "a4:c1:38:53:8c:f6:fb:61-01-ef00",
        "zonetype": null
    }

Steps to reproduce the behavior

Refer previous Issues as detailed in the bug (above)

Expected behavior

The preferred solution would be to change the behaviour to default either "unknown", or an empty string and last announced, last seen defaults the timestamp for the creation time.

Screenshots

No response

Environment

• Host system: All
• Running method: All
• Firmware version: (26550900)
• deCONZ version (not Home assistant Addon version!): (2.30.00)
• Device: (ConBee III )
• Do you use an USB extension cable: (N/A) -- only relevant for ConBee I/II/III

deCONZ Logs

No response

Additional context

No response

[manup]

Could you check with latest stable version? The null values on devices should be solved there.

[brientim]

@manup

There are two attributes as detailed below that creates “nulll” in the latest stable release 2.30.2

"replacesbridgeid": null,

“buttonevent": null,

[manup]

Ah right, the "replacesbridgeid": null is a relict from the Hue API (if memory serves it's null there too). I think we can ditch it since it's never used by deCONZ or clients.

“buttonevent": null this shouldn't happen at least for DDF driven devices. I'll check the legacy code to align to 0 here too.

[brientim]

Excellent as Hue doesn’t use it either. Thank you for the support.

[github-actions[bot]]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[brientim]

@manup still WIP to finalise in later release.

[github-actions[bot]]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions[bot]]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.