failed to open json #7845

MSL-DA · 2024-07-19T19:19:30Z

Does the issue really belong here?

I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

I have searched the existing issues and there is none for the bug at hand

Describe the bug

When I try to open a custom ddf I get this error: faild to open /opt/deCONZ/devices/test.json

Steps to reproduce the behavior

Open deCONZ GUI, select node, edit ddf, open /opt/deCONZ/devices/...json

Expected behavior

open and load test.json

Environment

- Host system: (Raspberry Pi)
- Running method: (deconz-docker container)
- Firmware version: (26530900)
- deCONZ version (2.27.5)
- Device: (ConBee III)
- Do you use an USB extension cable: (yes)
- Is there any other USB or serial devices connected to the host system? No

Additional context

No problems with deconz/stable (v2.26.3)

The text was updated successfully, but these errors were encountered:

MSL-DA · 2024-07-21T20:08:17Z

Custom .ddf is not preferred...no matter what I do, .ddf is selected from /usr/share/deCONZ/devices, not /opt/deCONZ/devices

Mimiix · 2024-07-21T20:14:59Z

Can you share the DDF your trying to load?

MSL-DA · 2024-07-21T20:24:05Z

It's not just one DDF, it applies to all of them, just as no custom DDF in /opt/deCONZ/devices is used

but here is an example

{
  "schema": "devcap1.schema.json",
  "uuid": "d9e2a290-e2b4-42de-bd95-4b46b4f0a142",
  "manufacturername": "$MF_LUMI",
  "modelid": "lumi.switch.n0agl1",
  "vendor": "Xiaomi",
  "product": "Aqara T1 single rocker switch (with neutral wire) SSM-U01",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion",
          "parse": {
            "at": "0x00f7",
            "ep": 1,
            "fn": "xiaomi:special",
            "idx": "0x08",
            "script": "xiaomi_swversion.js"
          },
          "read": {
            "fn": "none"
          }
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/alert"
        },
        {
          "name": "state/on",
          "refresh.interval": 300
        },
        {
          "name": "state/reachable"
        }
      ]
    },
     {
      "type": "$TYPE_POWER_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x15",
        "0x000C"
      ],
      "fingerprint": {
        "profile": "0x0104",
        "device": "0x0100",
        "endpoint": "0x15",
        "in": [
          "0x000C"
        ]
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion",
          "parse": {
            "at": "0x00f7",
            "ep": 1,
            "fn": "xiaomi:special",
            "idx": "0x08",
            "script": "xiaomi_swversion.js"
          },
          "read": {
            "fn": "none"
          }
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/current",
          "parse": {
            "at": "0x00F7",
            "eval": "Item.val = Math.round(Attr.val);",
            "fn": "xiaomi:special",
            "idx": "0x97"
          },
          "read": {
            "fn": "none"
          }
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/power",
          "refresh.interval": 10,
          "read": {
            "at": "0x0055",
            "cl": "0x000C",
            "ep": 21,
            "fn": "zcl:attr"
          },
          "parse": {
            "at": "0x0055",
            "cl": "0x000C",
            "ep": 21,
            "eval": "Item.val = Math.round(Attr.val);"
          }
        },
        {
          "name": "state/voltage",
          "parse": {
            "at": "0x00F7",
            "eval": "Item.val = Math.round(Attr.val / 10);",
            "fn": "xiaomi:special",
            "idx": "0x96"
          },
          "read": {
            "fn": "none"
          }
        }
      ]
    },
    {
      "type": "$TYPE_CONSUMPTION_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x1F",
        "0x000C"
      ],
      "fingerprint": {
        "profile": "0x0104",
        "device": "0x0100",
        "endpoint": "0x1F",
        "in": [
          "0x000C"
        ]
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion",
          "parse": {
            "at": "0x00f7",
            "ep": 1,
            "fn": "xiaomi:special",
            "idx": "0x08",
            "script": "xiaomi_swversion.js"
          },
          "read": {
            "fn": "none"
          }
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/consumption",
          "refresh.interval": 300,
          "read": {
            "at": "0x0055",
            "cl": "0x000C",
            "ep": 31,
            "fn": "zcl:attr"
          },
          "parse": {
            "at": "0x0055",
            "cl": "0x000C",
            "ep": 31,
            "eval": "Item.val = Math.round(Attr.val * 1000);"
          }
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ]
}

MSL-DA · 2024-07-21T20:27:42Z

https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/xiaomi/xiaomi_ssm-u01_t1_switch.json

SwoopX · 2024-07-21T20:34:50Z

I can confirm this. Doesn't matter if it's a correct or erroneous DDF

MSL-DA · 2024-07-21T21:37:12Z

I experienced the problem before version 2.27.5, so it's not a new bug. But I know it is after version 2.26.3

Mimiix · 2024-07-22T04:57:46Z

I can confirm this. Doesn't matter if it's a correct or erroneous DDF

Is this the first report ?!

manup · 2024-07-22T13:38:57Z

Hi sorry my bad, this is a known open item for v2.28.x

Currently the loading via "Open" menu entry in DDF editor isn't implemented/active. This happened due the refactor of the whole loading process a few versions back.

deconz-rest-plugin/device_descriptions.cpp

Lines 1439 to 1445 in 9e46fe3

    
           const DeviceDescription &DeviceDescriptions::load(const QString &path) 
        
           { 
        
               Q_UNUSED(path) 
        
               // TODO(mpi) implement 
        
               Q_D(DeviceDescriptions);

As a workaround if you have a device using the DDF in your network, you can open the DDF by:

Selecting the device node, press Ctrl+E

or via

The node context menu → Edit DDF

For this the DDF needs to be in the right location and loaded on startup.

manup · 2024-07-22T13:42:12Z

But in addition, the load order of the raw JSON needs to be checked too to prefer user directory over system location, I'm on it..

If a system location DDF already existed the user location DDF wasn't picket up correctly. The problem occured only for raw JSON DDFs not bundles. Part of dresden-elektronik#7845

If a system location DDF already existed the user location DDF wasn't picket up correctly. The problem occured only for raw JSON DDFs not bundles. Part of #7845

MSL-DA · 2024-07-22T22:01:54Z

Selecting the device node, press Ctrl+E

or via

The node context menu → Edit DDF

For this the DDF needs to be in the right location and loaded on startup.

This is exactly what I can't do after version 2.26.3. I can open the DDF editor but I get the error when I open a .ddf. I can save a custom DDF, and as I said, it is not selected on restart

Like neither custom DDF nor bundle is preferred from /opt/deCONZ/ it is not only from /opt/deCONZ/devices/ but also /opt/deCONZ/bundles

manup · 2024-07-24T10:45:26Z

Not sure where the /opt path comes from, but by default the user location is in $HOME/.local/share/dresden-elektronik/deCONZ/devices. Perhaps inside the Docker container this is /root/.local/share/dresden-elektronik/deCONZ/devices?

MSL-DA · 2024-07-25T15:50:16Z

Not sure where the /opt path comes from, but by default the user location is in $HOME/.local/share/dresden-elektronik/deCONZ/devices. Perhaps inside the Docker container this is /root/.local/share/dresden-elektronik/deCONZ/devices?

Please ignore #7845 (comment)

MSL-DA · 2024-07-27T11:24:52Z

As a workaround if you have a device using the DDF in your network, you can open the DDF by:

Selecting the device node, press Ctrl+E

or via

The node context menu → Edit DDF

For this the DDF needs to be in the right location and loaded on startup.

I might add that custom DDF is selected as intended with version 2.27.6

Although I can't open a DDF The node context menu → _Edit DDF_ , I close as resolved

MSL-DA added the Bug report label Jul 19, 2024

SwoopX added the Confirmed Bug label Jul 21, 2024

manup mentioned this issue Jul 22, 2024

Fix raw JSON DDF load order for user location #7851

Merged

manup added a commit that referenced this issue Jul 22, 2024

Fix raw JSON DDF load order for user location (#7851)

7945694

If a system location DDF already existed the user location DDF wasn't picket up correctly. The problem occured only for raw JSON DDFs not bundles. Part of #7845

MSL-DA closed this as completed Jul 27, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

failed to open json #7845

failed to open json #7845

MSL-DA commented Jul 19, 2024 •

edited

Loading

MSL-DA commented Jul 21, 2024 •

edited

Loading

Mimiix commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

SwoopX commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

Mimiix commented Jul 22, 2024

manup commented Jul 22, 2024

manup commented Jul 22, 2024

MSL-DA commented Jul 22, 2024

manup commented Jul 24, 2024

MSL-DA commented Jul 25, 2024

MSL-DA commented Jul 27, 2024

failed to open json #7845

failed to open json #7845

Comments

MSL-DA commented Jul 19, 2024 • edited Loading

Does the issue really belong here?

Is there already an existing issue for this?

Describe the bug

Steps to reproduce the behavior

Expected behavior

Environment

Additional context

MSL-DA commented Jul 21, 2024 • edited Loading

Mimiix commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

SwoopX commented Jul 21, 2024

MSL-DA commented Jul 21, 2024

Mimiix commented Jul 22, 2024

manup commented Jul 22, 2024

manup commented Jul 22, 2024

MSL-DA commented Jul 22, 2024

manup commented Jul 24, 2024

MSL-DA commented Jul 25, 2024

MSL-DA commented Jul 27, 2024

MSL-DA commented Jul 19, 2024 •

edited

Loading

MSL-DA commented Jul 21, 2024 •

edited

Loading