Maximum number of hooks

[Ap15e]

Is there a limit to the number of variables that can simultaneously be watched via [tt]variable_watch[/tt]? MAX_CALLBACKS? If there is a limit, [tt]luup.variable_watch[/tt] should return an error code.

I’m asking because I’m trying to watch all HaDevice1 variables for all my devices, but I think that some variables (e.g., battery reports (BatteryDate)) are missing from my logfile.

[mcvflorin]

Theoretically you should be able to watch an unlimited number of variables. Check the logs to see if those variables are really monitored: look for luup_variable_watch added hook to device.

[Ap15e]

Found a bug in GDL V0.7:
GDL V0.7 doesn’t support device category 1, but HSM100s are ComboDevice1s with device category 1 and the battery variables are components of the HSM100 parent devices …

I’ll report back after fixing GDL.

[Ap15e]

Update:

GDL V0.8 (available soon) with support for device category 1 does report the battery variables:

Sep  2 01:18:19 192.168.x.y GDL_18_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314919099 FL_Bewegungsmelder 1314919099
Sep  2 02:27:24 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314923241 B__3-in-1 1314923240
Sep  2 02:36:45 192.168.x.y GDL_16695_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314923804 SZ_3-in-1 1314923804
Sep  2 02:42:09 192.168.x.y GDL_16677_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314924129 AZ_3-in-1_ 1314924129
Sep  2 04:22:25 192.168.x.y GDL_18_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314930145 FL_Bewegungsmelder 1314930145
Sep  2 05:32:23 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314934343 B__3-in-1 1314934343
Sep  2 05:32:23 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryLevel: 1314934343 B__3-in-1 87
Sep  2 05:37:59 192.168.x.y GDL_16830_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314934679 WZ_3-in-1 1314934679
Sep  2 05:45:08 192.168.x.y GDL_16695_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314935108 SZ_3-in-1 1314935107
Sep  2 07:26:32 192.168.x.y GDL_18_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314941192 FL_Bewegungsmelder 1314941192
Sep  2 08:43:32 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314945812 B__3-in-1 1314945812
Sep  2 08:54:03 192.168.x.y GDL_16709_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314946443 K__3-in-1 1314946443
Sep  2 08:54:03 192.168.x.y GDL_16709_urn:micasaverde-com:serviceId:HaDevice1/BatteryLevel: 1314946443 K__3-in-1 96
Sep  2 10:04:07 192.168.x.y GDL_16695_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314950647 SZ_3-in-1 1314950647
Sep  2 10:30:41 192.168.x.y GDL_18_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314952241 FL_Bewegungsmelder 1314952241
Sep  2 12:00:57 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314957657 B__3-in-1 1314957657
Sep  2 12:10:00 192.168.x.y GDL_16709_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314958200 K__3-in-1 1314958200
Sep  2 13:11:00 192.168.x.y GDL_16695_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314961860 SZ_3-in-1 1314961860
Sep  2 14:36:00 192.168.x.y GDL_18_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314966960 FL_Bewegungsmelder 1314966960
Sep  2 15:08:16 192.168.x.y GDL_16751_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314968896 B__3-in-1 1314968896
Sep  2 15:11:33 192.168.x.y GDL_16677_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314969093 AZ_3-in-1_ 1314969093
Sep  2 16:46:20 192.168.x.y GDL_16695_urn:micasaverde-com:serviceId:HaDevice1/BatteryDate: 1314974780 SZ_3-in-1 1314974780

The distance between the 3-in-1 HSM100 sensors and Vera is minimal for the AZ_3-in-1 HSM100, but the AZ_3-in-1 is the device with the least frequent battery report. Strange.