This is happening quite a lot. Does anyone know why this would happen and what it means / how to rectify it?Cannot create vDev based on: 23-0-113: Error: Too many bindings to one dataholder
Error: Too many bindings to one dataholder
-
- Posts: 18
- Joined: 29 Nov 2015 15:47
Error: Too many bindings to one dataholder
I'm seeing an error in my zway events log (/smarthome/#/events):
Re: Error: Too many bindings to one dataholder
This means there are too many subscribers to some value. Is it the last v2.2.0? We have rised this value compared to previous 2.1.1
-
- Posts: 18
- Joined: 29 Nov 2015 15:47
Re: Error: Too many bindings to one dataholder
Hey, yes I'm running 2.2.0. It seems to happen just after setting the light dimmer to 99 or 0 when the motion sensor activates.
- Attachments
-
- Screen Shot 2015-12-14 at 10.25.41.png (325.53 KiB) Viewed 15458 times
-
- Posts: 18
- Joined: 29 Nov 2015 15:47
Re: Error: Too many bindings to one dataholder
FYI In my network, device 35 is an Aeon Labs Multisensor 6. The light it is switching on and off (via scenes) is an Aeon Labs RGB Bulb.
Re: Error: Too many bindings to one dataholder
Hi,
I am having the same error. Every 10 minutes the error is repeated 12 times.
22:30 | Cannot create vDev based on: 12-0-113: Error: Too many bindings to one dataholder
I started seeing it after an upgrade to v2.2.0. Device 12 for me is a Fibaro dimmer 2.
Is this max subscriber value that was increased in version v2.2.0 a setting that we can lower ourselves or does it require a new version? If we can change it ourselves where can we find it and what was the previous version set to?
PS great product I have started to install this in my house about 2 months ago and it is working great.
Best regards,
SjaakvE
I am having the same error. Every 10 minutes the error is repeated 12 times.
22:30 | Cannot create vDev based on: 12-0-113: Error: Too many bindings to one dataholder
I started seeing it after an upgrade to v2.2.0. Device 12 for me is a Fibaro dimmer 2.
Is this max subscriber value that was increased in version v2.2.0 a setting that we can lower ourselves or does it require a new version? If we can change it ourselves where can we find it and what was the previous version set to?
PS great product I have started to install this in my house about 2 months ago and it is working great.
Best regards,
SjaakvE
Re: Error: Too many bindings to one dataholder
Hey,
I also have this same problem. I think it's linked to the Aeon Multisensor 6... I don't have many z-wave devices yet.
I'm using the latest z-way version v2.2.0
I've played around with the apps but as far as I'm aware I haven't linked the Aeon Multisensor 6 to anything. For now it just spits out Temp, Humidity, Lux, Battery etc
I also have this same problem. I think it's linked to the Aeon Multisensor 6... I don't have many z-wave devices yet.
Sorry for my stupidity, but what does ^ actually mean?This means there are too many subscribers to some value. Is it the last v2.2.0? We have rised this value compared to previous 2.1.1
I'm using the latest z-way version v2.2.0
I've played around with the apps but as far as I'm aware I haven't linked the Aeon Multisensor 6 to anything. For now it just spits out Temp, Humidity, Lux, Battery etc
Code: Select all
[2015-12-18 07:44:34.110] [I] [core] Notification: device-info (device-OnOff): {"dev":"Aeon Labs Burglar (5.0.113.7.8) Alarm","l":"off"}
[2015-12-18 07:44:34.522] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:34.536] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
[2015-12-18 07:44:48.043] [D] [zway] RECEIVED: ( 01 09 00 04 00 05 03 20 01 FF 2A )
[2015-12-18 07:44:48.043] [D] [zway] SENT ACK
[2015-12-18 07:44:48.043] [D] [zway] SETDATA devices.5.data.lastReceived = 0 (0x00000000)
[2015-12-18 07:44:48.044] [D] [zway] SETDATA devices.1.instances.0.commandClasses.32.data.srcNodeId = 5 (0x00000005)
[2015-12-18 07:44:48.044] [D] [zway] SETDATA devices.1.instances.0.commandClasses.32.data.srcInstanceId = 0 (0x00000000)
[2015-12-18 07:44:48.044] [D] [zway] SETDATA devices.1.instances.0.commandClasses.32.data.level = 255 (0x000000ff)
[2015-12-18 07:44:48.054] [I] [core] Notification: device-info (device-OnOff): {"dev":" (5.0.0) Button","l":"on"}
[2015-12-18 07:44:48.339] [D] [zway] RECEIVED: ( 01 10 00 04 00 05 0A 71 05 00 00 00 FF 07 08 00 00 60 )
[2015-12-18 07:44:48.339] [D] [zway] SENT ACK
[2015-12-18 07:44:48.339] [D] [zway] SETDATA devices.5.data.lastReceived = 0 (0x00000000)
[2015-12-18 07:44:48.340] [D] [zway] SETDATA devices.5.instances.0.commandClasses.113.data.7.eventParameters = byte[0]
[2015-12-18 07:44:48.340] [D] [zway] ( zero-length buffer )
[2015-12-18 07:44:48.340] [D] [zway] SETDATA devices.5.instances.0.commandClasses.113.data.7.event = 8 (0x00000008)
[2015-12-18 07:44:48.366] [D] [zway] SETDATA devices.5.instances.0.commandClasses.113.data.7.eventString = "Motion detected, location unknown"
[2015-12-18 07:44:48.367] [D] [zway] SETDATA devices.5.instances.0.commandClasses.113.data.7.status = 255 (0x000000ff)
[2015-12-18 07:44:48.367] [D] [zway] SETDATA devices.5.instances.0.commandClasses.113.data.7 = Empty
[2015-12-18 07:44:48.380] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:48.393] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
[2015-12-18 07:44:48.523] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:48.535] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
[2015-12-18 07:44:48.549] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:48.561] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
[2015-12-18 07:44:48.575] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:48.587] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
[2015-12-18 07:44:48.594] [I] [core] Notification: device-info (device-OnOff): {"dev":"Aeon Labs Burglar (5.0.113.7.8) Alarm","l":"on"}
[2015-12-18 07:44:48.625] [I] [core] Notification: error (core): Cannot create vDev based on: 5-0-113: Error: Too many bindings to one dataholder
[2015-12-18 07:44:48.638] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)
-
- Posts: 18
- Joined: 29 Nov 2015 15:47
Re: Error: Too many bindings to one dataholder
It's interesting that the function 113 is where the errors are occurring in all our logs.
Re: Error: Too many bindings to one dataholder
I have this error as well.
Would be nice to get rid of it in the log.
"21:59 | Cannot create vDev based on: 2-0-113: Error: Too many bindings to one dataholder"
Aeon multisensor
Would be nice to get rid of it in the log.
"21:59 | Cannot create vDev based on: 2-0-113: Error: Too many bindings to one dataholder"
Aeon multisensor
Re: Error: Too many bindings to one dataholder
Hi,
i have this error as well.
A lot off.....
More than 25 errors per device, roughly every hour!
V2.2.0
Fibaro FGSD-002
i have this error as well.
A lot off.....
More than 25 errors per device, roughly every hour!
V2.2.0
Fibaro FGSD-002
Re: Error: Too many bindings to one dataholder
Hi,
same error with the latest z-way version v2.2.0 and the Aeon Multisensor 6.
same error with the latest z-way version v2.2.0 and the Aeon Multisensor 6.
Code: Select all
[2016-01-04 10:11:00.429] [I] [core] Notification: error (core): Cannot create vDev based on: 3-0-113: Error: Too many bindings to one dataholder
[2016-01-04 10:11:00.432] [I] [core] Error: Too many bindings to one dataholder
at Error (native)
at ZWave.dataBind (automation/modules/ZWave/index.js:1081:18)
at automation/modules/ZWave/index.js:2217:12
at Array.forEach (native)
at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:2120:25)
at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:2297:12)