Error: Too many bindings to one dataholder

[mkruse]

Hi, after some days I have the same issue. But these errors are with Fibaro FGSD-002. It's started on a smoke detector and then I have it on all devices.

15:30 | vDev konnte mit den folgenden Daten nicht erstellt werden: 24-0-113: Error: Too many bindings to one dataholder
core 15:30 | vDev konnte mit den folgenden Daten nicht erstellt werden: 24-0-113: Error: Too many bindings to one dataholder
core 15:30 | vDev konnte mit den folgenden Daten nicht erstellt werden: 24-0-113: Error: Too many bindings to one dataholder
core 15:30 | vDev konnte mit den folgenden Daten nicht erstellt werden: 24-0-113: Error: Too many bindings to one dataholder

[Raptor2k1]

Hi!

I have the same error with a Aeotec Multisensor6. But not always! I thought that the interval (in witch the device is sending data) is associated with the problem. But after plug the device off and back on (with same interval), i got no more error messages Some hours after i got the errors again and since yesterday there was no more error in z-way log

Z-Way 2.1.2 > Windows 7 Prof. x64

Greets
Chris

[PoltoS]

This problem means too many bindings are made to the same data holder. What are you doing specifically?

[Raptor2k1]

The last time i had these errors > all vars of "aeontec multisensor 6" would be updated - but not 9.0.7.8 (tamper protection). Each time i forced this alarm i got "too many bindings to one dataholder".
But the next days, with NO config changes - the Errors are gone I´m actually only testing some things with Z-Way and my other smarthome system, so i often include/exclude/Service restart/...

Maybe it happens, when the time-interval between the alarms is to short?! Or the report-send-interval is to short?! Or when z-way service comes up and in the first seconds to many events came in? The "Aeontec Multisensor 6" sends 3 types of alarms, sometimes in the same microsecond > 0.7 // 0.7.3 // 0.7.8 This could case the errors too?!

Greets
Chris

[coolbloke1324]

This problem means too many bindings are made to the same data holder. What are you doing specifically?

I have an If... Then... on the sensor so if there is movement it turns on a light.

This is the only thing I have reacting to that sensor. Many others here are experiencing the same issue. I think this is much more likely to be a bug in the code than anything a user has done.

Is your code open-source? I suspect many of us are programmers and would be happy to help track down the issue.

[PoltoS]

This error message occurs only if one dataholder is binded more than 500 times (not sure about exact number, but > 100 for sure). These bindings are done in JavaScript code (it is open). I suppose some bug in JS is producing more bindings than needed. That's why I ask for specific user experience - not everyone have this. Once we get more data we can understand where to look on.

[S.Kluth]

Today I got the first time errors like

vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder

There are only 3 devices in my network:
Thermostat StellaZ
Thermostat Danfoss Living Connect Z
aeon labs multisensor 6

at 7:45 this morning there was also a "little bit" cold temperature reported from StellaZ

device-temperature 07:45 | Thermostat StellaZ 1 ist -620.5 °C

Code: Select all

core 	08:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	08:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	08:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	08:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
device-OnOff 	08:35 | (3.0.0) Button ist on 	
device-temperature 	08:33 | Thermostat StellaZ 1 ist 20 °C 	
device-temperature 	08:20 | Aeon Labs Temperature (3.0.49.1) ist 22 °C 	
device-temperature 	07:51 | Thermostat StellaZ 1 ist 19.5 °C 	
device-humidity 	07:46 | Aeon Labs Humidity (3.0.49.5) ist 35 % 	
device-temperature 	07:46 | Aeon Labs Temperature (3.0.49.1) ist 22.1 °C 	
device-temperature 	07:45 | Thermostat StellaZ 1 ist -620.5 °C 	
device-temperature 	07:40 | Aeon Labs Temperature (3.0.49.1) ist 22.2 °C 	
core 	07:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
device-OnOff 	07:35 | Aeon Labs Burglar 2 Alarm (3.0.113.7.8) ist off 	
core 	07:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	07:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	07:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
core 	07:35 | vDev konnte mit den folgenden Daten nicht erstellt werden: 3-0-113: Error: Too many bindings to one dataholder 	
device-OnOff 	07:35 | (3.0.0) Button ist off 	
device-temperature 	07:33 | Thermostat StellaZ 1 ist 19.5 °C

I attach a log file witch shows the system start after cleaning the previous log, as stated in qour faq.

z-way-server.log.bak2.gz

clean log

(42.12 KiB) Downloaded 516 times

The original log ist to large to upload here, even if compressed. So I cuted just a part of it that you'l find in the 2nd attachement.

z-way-server.log-cuted.gz

Long log cut

(13.94 KiB) Downloaded 516 times

I'll detach the aeon labs multisensor 6 now and may provide further log information if you'll ask for it.

[Sparkacus]

I'm getting this issue non-stop now.

All my Aeon sensor does at that moment is update z-way with temp, lux, humidity etc, it doesn't action anything based on specific results.

Code: Select all

2016-01-13 08:30:53.330] [I] [core] Notification: error (core): Cannot create vDev based on: 14-0-113: Error: Too many bindings to one dataholder
[2016-01-13 08:30:53.349] [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)
[2016-01-13 08:30:53.607] [I] [core] Notification: error (core): Cannot create vDev based on: 14-0-113: Error: Too many bindings to one dataholder
[2016-01-13 08:30:53.621] [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)
[2016-01-13 08:30:53.634] [I] [core] Notification: error (core): Cannot create vDev based on: 14-0-113: Error: Too many bindings to one dataholder
[2016-01-13 08:30:53.647] [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)
[2016-01-13 08:30:53.660] [I] [core] Notification: error (core): Cannot create vDev based on: 14-0-113: Error: Too many bindings to one dataholder
[2016-01-13 08:30:53.673] [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)
[2016-01-13 08:30:53.732] [I] [core] Notification: device-info (device-OnOff): {"dev":"Aeon Labs Motion (14.0.113.7.8) Alarm","l":"off"}
[2016-01-13 08:30:53.766] [I] [core] Notification: error (core): Cannot create vDev based on: 14-0-113: Error: Too many bindings to one dataholder
[2016-01-13 08:30:53.779] [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)
[2016-01-13 08:31:06.808] [D] [zway] Job 0x13: deleted from queue

[ridewithstyle]

Hi there,

I have the same error with v2.2.1 RC3 and a Devolo Thermostat.

Regards, rws

[mrnmukkas]

I also have this problem with v2.2.1-rc3. I have three Fibaro Dimmer 2 (FGD-212) and they all create a bunch of these warnings. I've been able to alleviate it for a few hours by restarting the server.
I thought I had fixed it yesterday by changing the Device Description in Expert UI, but after a few hours it came back again.
I've noticed that the number of errors match the number of alarms (or every x-0-113-... id) on the device, ten in my case:

• Alarm Heat 10-0-113-4-2 Fibar Group
• Alarm Power Management 10-0-113-8-4 Fibar Group
• Alarm Power Management 10-0-113-8-5 Fibar Group
• Alarm Power Management 10-0-113-8-6 Fibar Group
• Alarm Power Management 10-0-113-8-8 Fibar Group
• Alarm Power Management 10-0-113-8-9 Fibar Group
• Alarm System 10-0-113-9-1 Fibar Group
• Fibar Group Heat Alarm (10.0.113.4.254)
• Fibar Group Power Management Alarm (10.0.113.8.254)
• Fibar Group System Alarm (10.0.113.9.254)

I know that the FGD-212 have some issues, but this is new in 2.2.1-rc3.