search

Smanar / Domoticz-deCONZ

deCONZ plugin for Domoticz (Zigbee application)
GNU General Public License v3.0
36 stars 27 forks source link

Errors in Domoticz log : How to identify unit numbers #141

Closed Patricen1 closed 1 year ago

Patricen1 commented 1 year ago

Hello, Everything is in the title... I do have the following errors within Domoticz log, but I'm inable to loidentify which unit corresponds to which device. Help appreciated !

2022-11-18 21:10:54.549 Error: Zigbee Deconz: Can't Update Unit > 24 (lights) : {'nValue': 1, 'sValue': 'on'} 2022-11-18 21:10:54.753 Error: Zigbee Deconz: Can't Update Unit > 72 (sensors) : {'nValue': 0, 'sValue': '0', 'voltage': 234, 'current': 0} 2022-11-18 21:10:54.856 Error: Zigbee Deconz: Can't Update Unit > 72 (sensors) : {'nValue': 0, 'sValue': '0', 'voltage': 234, 'current': 0} 2022-11-18 21:10:55.008 Error: Zigbee Deconz: Can't Update Unit > 72 (sensors) : {'nValue': 0, 'sValue': '0', 'voltage': 236, 'current': 0}

Smanar commented 1 year ago

Hello

2022-11-18 21:10:54.856 Error: Zigbee Deconz: Can't Update Unit > 72 (sensors) : {'nValue': 0, 'sValue': '0', 'voltage': 234, 'current': 0}

You have this error when domoticz receive information to update a device and when it is not able to find it in the plugin database (it use the type and id to reconize them)

You haven't this error just before ?

Websocket error, unknown device >................

When deconz found a new device in the API it ask information to add it (or you can too restart the plugin using setting/hardware/deconz/update, but you need to not have disabled the option in domoticz to add new device. (or you have it only at start ?)

If you restart domoticz you will see at start a listing to identify the device with enabling log "debug info only".

Else the easy way

Can't Update Unit > 24 (lights)

Just use Phoscon/help/API Information/light/24

For me it's the same device, a plug with the on/off in light/24 and the consumption on sensors/72

Smanar commented 1 year ago

@Patricen1 do you have found more information ?

Patricen1 commented 1 year ago

Just tried and this works perfectly, the only remaining error that appears is: 2022-11-22 20:51:39.341 Error: Zigbee Deconz: This device doesn't support action

Thanks!

Smanar commented 1 year ago

This error can happen on passive widget, domoticz use same for active and passive device, so if you try to ask for an action to a passive device you will have this error (for exemple a battery switch)

Patricen1 commented 1 year ago

Hello, IOMZB-110 I've found out the root cause, it looks like it is coming from IOMZB-110 device we discussed some time ago, this device is equipped with relays that are controlled using Zigbee. They do appear as light/switch type, switch subtype on Domoticz devices panel, and it might be necessary to configure them as light subtype as they are outputs.

Smanar commented 1 year ago

Ha ? I m reading the DDF, they need to create :

I think the problem is from the DDF.

@Patricen1 can you try edit the DDF

    {
      "type": "$TYPE_SWITCH",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x74",
        "0x000f"
      ],

Here you need to have "0x73" instead of "0x74", can be corrected using the editor.

And you probably need to delete your device and re-include it, idk if deconz will remove the bad entry (need to convert a "sensor" to a "light". not sure the "hot reload" will work.

Patricen1 commented 1 year ago

Hello,

Not sure to understand which line to correct, please find attached ddf file

Le sam. 26 nov. 2022 à 10:52, Smanar @.***> a écrit :

Ha ? I m reading the DDF, they need to create :

  • A "light" TYPE_ON_OFF_OUTPUT 0x74
  • A "light" TYPE_ON_OFF_OUTPUT 0x75
  • A "sensor" ZHASwitch 0x70
  • A "sensor" ZHASwitch 0x71
  • A "sensor" ZHASwitch 0x72
  • A "sensor" ZHASwitch 0x73 << missing in the DDF ^^
  • A "sensor" ZHASwitch 0x74 << wrong number, make confict with the "light"

I think the problem is from the DDF.

@Patricen1 https://github.com/Patricen1 can you try edit the DDF

{
  "type": "$TYPE_SWITCH",
  "restapi": "/sensors",
  "uuid": [
    "$address.ext",
    "0x74",
    "0x000f"
  ],

Here you need to have "0x73" instead of "0x74"

And you probably need to delete your device and re-include it, idk if deconz will remove the bad entry (need to convert a "sensor" to a "light".

— Reply to this email directly, view it on GitHub https://github.com/Smanar/Domoticz-deCONZ/issues/141#issuecomment-1328016374, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIGMUYGUF2NURJBFSE2H2G3WKHMWVANCNFSM6AAAAAASE27KJA . You are receiving this because you were mentioned.Message ID: @.***>

{ "schema": "devcap1.schema.json", "manufacturername": "Develco Products A/S", "modelid": "IOMZB-110", "product": "IOMZB-110", "sleeper": false, "status": "Draft", "subdevices": [ { "type": "$TYPE_ON_OFF_OUTPUT", "restapi": "/lights", "uuid": [ "$address.ext", "0x74" ], "items": [ { "name": "attr/id" }, { "name": "attr/lastannounced" }, { "name": "attr/lastseen" }, { "name": "attr/manufacturername" }, { "name": "attr/modelid" }, { "name": "attr/name" }, { "name": "attr/swversion" }, { "name": "attr/type" }, { "name": "attr/uniqueid" }, { "name": "state/alert", "description": "The currently active alert effect.", "default": "none" }, { "name": "state/on", "description": "True when device is on; false when off.", "refresh.interval": 5 }, { "name": "state/reachable" } ] }, { "type": "$TYPE_ON_OFF_OUTPUT", "restapi": "/lights", "uuid": [ "$address.ext", "0x75" ], "items": [ { "name": "attr/id" }, { "name": "attr/lastannounced" }, { "name": "attr/lastseen" }, { "name": "attr/manufacturername" }, { "name": "attr/modelid" }, { "name": "attr/name" }, { "name": "attr/swversion" }, { "name": "attr/type" }, { "name": "attr/uniqueid" }, { "name": "state/alert", "description": "The currently active alert effect.", "default": "none" }, { "name": "state/on", "description": "True when device is on; false when off.", "refresh.interval": 5 }, { "name": "state/reachable" } ] } ], "bindings": [ { "bind": "unicast", "src.ep": 116, "dst.ep": 1, "cl": "0x0006", "report": [ { "at": "0x0000", "dt": "0x10", "min": 1, "max": 300 } ] }, { "bind": "unicast", "src.ep": 117, "dst.ep": 1, "cl": "0x0006", "report": [ { "at": "0x0000", "dt": "0x10", "min": 1, "max": 300 } ] } ] }

Smanar commented 1 year ago

Ha ? Lol, you don't remember we have already made a DDF for this DDF, and the PR was valided now. What is your deconz version ? On the last one the file is "devices/develco/iomzb-110_switch_module.json" cf https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/develco/iomzb-110_switch_module.json

And BTW why deconz haven't selected it ? The one on your post is an autogenerated DDF, incomplete and whith "Draft" status. You have removed the one we have make for tests, or use an intermediate deconz version ?

On the offcial DDF it's the line 270

Patricen1 commented 1 year ago

Sure I remember :) Deconz version is 2.19.1. I'm going to copy iomzb110_switch_module.json.

Edit : found out the reason why the json file was not used by deCONZ, for an unknown reason (probably the user as myself) the jsonfile was not the expected DDF code but something else... Shame on me!