Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - davegravy

Pages: 1 2 [3] 4 5 ... 35
31
Users / Re: Doorbell - Double event trigger
« on: January 18, 2014, 10:30:09 pm »
In case you're wondering about the 3:2 device, that's the chime which I toggle on doorbell press and release... but I don't THINK that's relevant to my problem.

EDIT: I removed the chime command to be sure, and the GC100 still seems to report each state change twice.

32
Users / Doorbell - Double event trigger
« on: January 18, 2014, 10:18:58 pm »
I have a doorbell connected to my GC-100 on input module 4, sensor 1 (shows as 4:1 in the log)

I've created a respond-to event which fires when the sensor is tripped and sends my phone a notification. For some reason, each doorbell push triggers this event twice - creating a double notification - and i'd like to stop this from happening. Here's a log of a single button press and release:

Code: [Select]
10 01/18/14 16:02:23.138 Reply received from GC100: statechange,4:1,1 <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply interpreted as module: 4:1 change to 1 <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: found module of type SENSOR, 1 <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: matches exactly in m:s format <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.139 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 1) default state:  <0xb5f62b70>
21 01/18/14 16:02:23.139 lock(0x9ea41a4) (>956) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.139 acquired(0x9ea41a4) #0 (>956) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.139 unlock(0x9ea41a4) #0 (>956) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.139 removed from map (0x9ea41a4) #1 (>956) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
21 01/18/14 16:02:23.139 lock(0x9ea41a4) (>957) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.139 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:23.149 unlock(0x9ea41a4) #0 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:23.149 Socket::SendMessage type 2 id 9 from 234 to 0 <0xb7765b70>
21 01/18/14 16:02:23.149 acquired(0x9ea41a4) #0 (>957) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.150 unlock(0x9ea41a4) #0 (>957) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.150 removed from map (0x9ea41a4) #0 (>957) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
10 01/18/14 16:02:23.150 Sending command getstate,4:1
 <0xb5f62b70>
21 01/18/14 16:02:23.150 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:23.150 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.150 acquired(0x9ea41a4) #0 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.150 unlock(0x9ea41a4) #0 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:23.150 Socket::SendMessage type 2 id 9 from 240 to 0 <0xb7765b70>
21 01/18/14 16:02:23.150 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:23.150 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.150 acquired(0x9ea41a4) #0 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.150 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
10 01/18/14 16:02:23.219 Receive string: MESSAGE 77             <0xb6f64b70>
10 01/18/14 16:02:23.219 Received MESSAGE 77             0x9ea4058 device: 230 <0xb6f64b70>
10 01/18/14 16:02:23.219 Received Message type 1 ID 192 from 12 to 232 (device: 230) resp 0 <0xb6f64b70>
10 01/18/14 16:02:23.219 Message for Generic Relays RELAY 3:2 passed to Relay <0xb6f64b70>
10 01/18/14 16:02:23.219 Relay Pwr.: target device is 232 <0xb6f64b70>
10 01/18/14 16:02:23.219 gc100::GetPinDeviceID got pin 3:2 device 232 <0xb6f64b70>
10 01/18/14 16:02:23.219 Relay Pwr.: This device is 232 <0xb6f64b70>
21 01/18/14 16:02:23.219 lock(0x9ea4408) (>983) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:23.219 acquired(0x9ea4408) #0 (>983) gc100 gc100.cpp:1198  <0xb6f64b70>
10 01/18/14 16:02:23.219 Relay Pwr.: Found 3:2 in module map <0xb6f64b70>
10 01/18/14 16:02:23.219 Relay Pwr.: Regardless, module ID is 3:2 <0xb6f64b70>
10 01/18/14 16:02:23.219 Sending command setstate,3:2,1
 <0xb6f64b70>
10 01/18/14 16:02:23.300 EventThread <0xb5f62b70>
10 01/18/14 16:02:23.300 Reply received from GC100: state,4:1,1 <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply interpreted as module: 4:1 change to 1 <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: found module of type SENSOR, 1 <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: matches exactly in m:s format <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.300 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 1) default state:  <0xb5f62b70>
21 01/18/14 16:02:23.300 lock(0x9ea41a4) (>984) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.300 acquired(0x9ea41a4) #0 (>984) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.300 unlock(0x9ea41a4) #0 (>984) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.301 removed from map (0x9ea41a4) #0 (>984) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
21 01/18/14 16:02:23.301 lock(0x9ea41a4) (>985) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.301 acquired(0x9ea41a4) #0 (>985) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.301 unlock(0x9ea41a4) #0 (>985) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:23.301 removed from map (0x9ea41a4) #0 (>985) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
21 01/18/14 16:02:23.301 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:23.301 unlock(0x9ea41a4) #0 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:23.301 Socket::SendMessage type 2 id 9 from 234 to 0 <0xb7765b70>
10 01/18/14 16:02:23.301 Socket::SendMessage type 2 id 9 from 240 to 0 <0xb7765b70>
21 01/18/14 16:02:23.301 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:23.301 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.301 acquired(0x9ea41a4) #0 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:23.301 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:23.320 unlock(0x9ea4408) #0 (>983) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:23.320 removed from map (0x9ea4408) #0 (>983) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6f64b70>
10 01/18/14 16:02:23.338 Receive string: MESSAGE 77             <0xb6f64b70>
10 01/18/14 16:02:23.338 Received MESSAGE 77             0x9ea4058 device: 230 <0xb6f64b70>
10 01/18/14 16:02:23.338 Received Message type 1 ID 192 from 12 to 232 (device: 230) resp 0 <0xb6f64b70>
10 01/18/14 16:02:23.338 Message for Generic Relays RELAY 3:2 passed to Relay <0xb6f64b70>
10 01/18/14 16:02:23.338 Relay Pwr.: target device is 232 <0xb6f64b70>
10 01/18/14 16:02:23.338 gc100::GetPinDeviceID got pin 3:2 device 232 <0xb6f64b70>
10 01/18/14 16:02:23.338 Relay Pwr.: This device is 232 <0xb6f64b70>
21 01/18/14 16:02:23.338 lock(0x9ea4408) (>1012) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:23.338 acquired(0x9ea4408) #0 (>1012) gc100 gc100.cpp:1198  <0xb6f64b70>
10 01/18/14 16:02:23.338 Relay Pwr.: Found 3:2 in module map <0xb6f64b70>
10 01/18/14 16:02:23.338 Relay Pwr.: Regardless, module ID is 3:2 <0xb6f64b70>
10 01/18/14 16:02:23.338 Sending command setstate,3:2,1
 <0xb6f64b70>
10 01/18/14 16:02:23.351 EventThread <0xb5f62b70>
10 01/18/14 16:02:23.351 Reply received from GC100: state,3:2,1 <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply interpreted as module: 3:2 change to 1 <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: found module of type RELAY, 2 <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.351 statechange Reply: no exact match in m:s format, trying global pin number <0xb5f62b70>
05 01/18/14 16:02:23.351 statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb5f62b70>
10 01/18/14 16:02:23.404 EventThread <0xb5f62b70>
10 01/18/14 16:02:23.405 Reply received from GC100: state,3:2,1 <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply interpreted as module: 3:2 change to 1 <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: found module of type RELAY, 2 <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 1) default state:  <0xb5f62b70>
10 01/18/14 16:02:23.405 statechange Reply: no exact match in m:s format, trying global pin number <0xb5f62b70>
05 01/18/14 16:02:23.405 statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb5f62b70>
21 01/18/14 16:02:23.438 unlock(0x9ea4408) #0 (>1012) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:23.439 removed from map (0x9ea4408) #0 (>1012) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6f64b70>
10 01/18/14 16:02:23.455 EventThread <0xb5f62b70>
10 01/18/14 16:02:24.569 Reply received from GC100: statechange,4:1,0 <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply interpreted as module: 4:1 change to 0 <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: found module of type SENSOR, 1 <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: matches exactly in m:s format <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.570 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 0) default state:  <0xb5f62b70>
21 01/18/14 16:02:24.570 lock(0x9ea41a4) (>1014) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.570 acquired(0x9ea41a4) #0 (>1014) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.570 unlock(0x9ea41a4) #0 (>1014) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.570 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.570 unlock(0x9ea41a4) #0 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:24.570 Socket::SendMessage type 2 id 9 from 234 to 0 <0xb7765b70>
21 01/18/14 16:02:24.571 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:24.571 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.571 acquired(0x9ea41a4) #0 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.571 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.570 removed from map (0x9ea41a4) #1 (>1014) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
21 01/18/14 16:02:24.580 lock(0x9ea41a4) (>1016) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.581 acquired(0x9ea41a4) #0 (>1016) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.581 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.581 unlock(0x9ea41a4) #1 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:24.581 Socket::SendMessage type 2 id 9 from 240 to 0 <0xb7765b70>
21 01/18/14 16:02:24.581 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:24.581 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.581 acquired(0x9ea41a4) #1 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.581 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.581 unlock(0x9ea41a4) #0 (>1016) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.581 removed from map (0x9ea41a4) #0 (>1016) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
10 01/18/14 16:02:24.581 Sending command getstate,4:1
 <0xb5f62b70>
10 01/18/14 16:02:24.629 Receive string: MESSAGE 72             <0xb6f64b70>
10 01/18/14 16:02:24.629 Received MESSAGE 72             0x9ea4058 device: 230 <0xb6f64b70>
10 01/18/14 16:02:24.629 Received Message type 1 ID 193 from 12 to 232 (device: 230) resp 0 <0xb6f64b70>
10 01/18/14 16:02:24.629 Message for Generic Relays RELAY 3:2 passed to Relay <0xb6f64b70>
10 01/18/14 16:02:24.629 Relay Pwr.: target device is 232 <0xb6f64b70>
10 01/18/14 16:02:24.629 gc100::GetPinDeviceID got pin 3:2 device 232 <0xb6f64b70>
10 01/18/14 16:02:24.629 Relay Pwr.: This device is 232 <0xb6f64b70>
21 01/18/14 16:02:24.629 lock(0x9ea4408) (>1041) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:24.629 acquired(0x9ea4408) #0 (>1041) gc100 gc100.cpp:1198  <0xb6f64b70>
10 01/18/14 16:02:24.629 Relay Pwr.: Found 3:2 in module map <0xb6f64b70>
10 01/18/14 16:02:24.629 Relay Pwr.: Regardless, module ID is 3:2 <0xb6f64b70>
10 01/18/14 16:02:24.629 Sending command setstate,3:2,0
 <0xb6f64b70>
21 01/18/14 16:02:24.730 unlock(0x9ea4408) #0 (>1041) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:24.730 removed from map (0x9ea4408) #0 (>1041) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6f64b70>
10 01/18/14 16:02:24.731 EventThread <0xb5f62b70>
10 01/18/14 16:02:24.732 Reply received from GC100: state,4:1,0 <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply interpreted as module: 4:1 change to 0 <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: found module of type SENSOR, 1 <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: matches exactly in m:s format <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.732 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 0) default state:  <0xb5f62b70>
21 01/18/14 16:02:24.732 lock(0x9ea41a4) (>1043) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.732 acquired(0x9ea41a4) #0 (>1043) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.732 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.732 unlock(0x9ea41a4) #1 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:24.732 Socket::SendMessage type 2 id 9 from 234 to 0 <0xb7765b70>
21 01/18/14 16:02:24.733 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:24.733 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.733 acquired(0x9ea41a4) #1 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.733 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.733 unlock(0x9ea41a4) #0 (>1043) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.733 removed from map (0x9ea41a4) #0 (>1043) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
21 01/18/14 16:02:24.733 lock(0x9ea41a4) (>1045) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.733 acquired(0x9ea41a4) #0 (>1045) MessageQueue Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.733 end cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.733 unlock(0x9ea41a4) #1 (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
10 01/18/14 16:02:24.733 Socket::SendMessage type 2 id 9 from 240 to 0 <0xb7765b70>
21 01/18/14 16:02:24.733 relocking (0x9ea41a4) (>149)  <0xb7765b70>
21 01/18/14 16:02:24.733 lock(0x9ea41a4) (>149) MessageQueue: Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.733 acquired(0x9ea41a4) #1 (>149) MessageQueue Command_Impl.cpp:852  <0xb7765b70>
21 01/18/14 16:02:24.733 start cond wait Command_Impl.cpp:852 (0x9ea41a4)  <0xb7765b70>
21 01/18/14 16:02:24.733 unlock(0x9ea41a4) #0 (>1045) MessageQueue: Command_Impl.cpp:845  <0xb5f62b70>
21 01/18/14 16:02:24.733 removed from map (0x9ea41a4) #0 (>1045) MessageQueue: Command_Impl.cpp:845  was: 3 size, now 2 Rel: Y Got: Y <0xb5f62b70>
10 01/18/14 16:02:24.779 Receive string: MESSAGE 72             <0xb6f64b70>
10 01/18/14 16:02:24.779 Received MESSAGE 72             0x9ea4058 device: 230 <0xb6f64b70>
10 01/18/14 16:02:24.779 Received Message type 1 ID 193 from 12 to 232 (device: 230) resp 0 <0xb6f64b70>
10 01/18/14 16:02:24.780 Message for Generic Relays RELAY 3:2 passed to Relay <0xb6f64b70>
10 01/18/14 16:02:24.780 Relay Pwr.: target device is 232 <0xb6f64b70>
10 01/18/14 16:02:24.780 gc100::GetPinDeviceID got pin 3:2 device 232 <0xb6f64b70>
10 01/18/14 16:02:24.780 Relay Pwr.: This device is 232 <0xb6f64b70>
21 01/18/14 16:02:24.780 lock(0x9ea4408) (>1070) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:24.780 acquired(0x9ea4408) #0 (>1070) gc100 gc100.cpp:1198  <0xb6f64b70>
10 01/18/14 16:02:24.780 Relay Pwr.: Found 3:2 in module map <0xb6f64b70>
10 01/18/14 16:02:24.780 Relay Pwr.: Regardless, module ID is 3:2 <0xb6f64b70>
10 01/18/14 16:02:24.780 Sending command setstate,3:2,0
 <0xb6f64b70>
10 01/18/14 16:02:24.784 EventThread <0xb5f62b70>
10 01/18/14 16:02:24.784 Reply received from GC100: state,3:2,0 <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply interpreted as module: 3:2 change to 0 <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: found module of type RELAY, 2 <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.784 statechange Reply: no exact match in m:s format, trying global pin number <0xb5f62b70>
05 01/18/14 16:02:24.784 statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb5f62b70>
10 01/18/14 16:02:24.834 EventThread <0xb5f62b70>
10 01/18/14 16:02:24.834 Reply received from GC100: state,3:2,0 <0xb5f62b70>
10 01/18/14 16:02:24.834 statechange Reply interpreted as module: 3:2 change to 0 <0xb5f62b70>
10 01/18/14 16:02:24.834 statechange Reply: found module of type RELAY, 2 <0xb5f62b70>
10 01/18/14 16:02:24.834 statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 0) default state:  <0xb5f62b70>
10 01/18/14 16:02:24.835 statechange Reply: no exact match in m:s format, trying global pin number <0xb5f62b70>
05 01/18/14 16:02:24.835 statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb5f62b70>
21 01/18/14 16:02:24.880 unlock(0x9ea4408) #0 (>1070) gc100: gc100.cpp:1198  <0xb6f64b70>
21 01/18/14 16:02:24.880 removed from map (0x9ea4408) #0 (>1070) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6f64b70>
10 01/18/14 16:02:24.885 EventThread <0xb5f62b70>


I don't think this is an electronic switch bounce because

a) I've filtered bounces with a hardware circuit and
b) the log doesn't show the state switching from 1 to 0, and then back to 1.

Of note from the log:

10   01/18/14 16:02:23.139      statechange Reply interpreted as module: 4:1 change to 1 <0xb5f62b70>
10   01/18/14 16:02:23.300      statechange Reply interpreted as module: 4:1 change to 1 <0xb5f62b70>
10   01/18/14 16:02:24.570      statechange Reply interpreted as module: 4:1 change to 0 <0xb5f62b70>
10   01/18/14 16:02:24.732      statechange Reply interpreted as module: 4:1 change to 0 <0xb5f62b70>

It seems the GC-100 is double-reporting state changes and LMCE doesn't check to see whether each is a legit state change. Has anyone else noticed this?

Suppose I could have my event script check the time stamp it was last executed and abort if it was under a second ago, but that just seems like a bandaid solution.

Ideas?

33
Users / Re: Z-Wave
« on: January 06, 2014, 04:08:17 pm »
There's a number of knowledgeable users here and on the forums which serve other home automation programs that support zwave (e.g. homeseer)

I haven't found a single dedicated Z-wave forum.

34
Users / Re: Controlling AV equipment - peculiar behavior
« on: December 13, 2013, 02:09:29 am »
My connection diagram is attached.

Can't seem to reproduce the issues I was having before. The only issue I'm still consistently having is that from a powered-off state selecting the Xbox or Chromecast scenario in orbiter, only the SHAC-500D and HDMI Switch turn on. It seems the system looks at devices only one connection downstream.

If I want all downstream devices to turn on, how should I configure this?


35
Users / Controlling AV equipment - peculiar behavior
« on: December 11, 2013, 04:23:14 pm »
I've got 3 devices I'm controlling in my theatre room:

1) Projector (via RS232)
2) HDMI Switch (via RS232)
3) Audio Receiver (via IR)

This is LMCE 10.04 by the way. I've configured connections in the connection wizard as appropriate.

From orbiter, under advanced->infrared codes I can successfully and consistently control each piece of equipment (change inputs and power on/off) individually. However, orbiter actions which should control all three devices appear to be flaky. An example - All devices are off, I select Xbox scenario from orbiter, Projector turns on, HDMI switch does NOT turn on, audio receiver turns on and switches to correct input. The next time I try it, everything might work properly, or else a different component might fail to power on or switch inputs.

The HDMI switch won't switch to an input if there's no signal present, so yes I am making sure there's signal present first before executing scenarios.

I realize there could be various reasons for this, and I have more debugging to do in logs, etc, but I wanted to get this out there just in case there's a known bug or something that people are aware of.

36
Users / Re: Ubiquiti mFi - your thoughts about these devices?
« on: November 25, 2013, 06:12:27 am »
http://www.anandtech.com/show/7530/ubiquiti-networks-mfi-mpower-wifi-power-strip-review

Looks to me like it's not too expensive. But lack of an API that allows other software to control it is an issue.

37
Users / Re: Any motherboard suggestions?
« on: November 23, 2013, 05:41:31 pm »
Good day guys, I've been running 10.04 fine until my motherboard crapped out beyond no repair.  I've been looking at the posts but haven't come up with any suggestions for a new motherboard other than someone suggesting to look at Andrew's setup.  does anybody have any suggestions that has been proven to work with 10.04 or 12.04 which i more than likely will step up to? appreciate any input. thanks

I'm a little rusty as I haven't been in hardware purchasing mode for 4+ years, but...

IIRC, Thom is a big advocate of the more expensive server-grade motherboards for this application. Also, I read that IO is typically the limiting factor for this software... not CPU or RAM.

38
Users / Re: zwave dimmable light switches
« on: November 13, 2013, 02:00:48 pm »
I noticed the same thing, however as I always control my lights from custom scenarios which I write (I never use floorplan or list controls in orbiter) it's not a big problem for me.

39
Users / Re: Kickstarter Campaign to fund a programmer?
« on: September 11, 2013, 12:04:33 am »
Do I think that having Thom dedicate his worktime on LinuxMCE for a year? Absolutely. Do I think that a kickstarter campaign will attract even 10% of Thom's desired goal? Not in a million years.

Let's face it: The people who are using LinuxMCE these days are mainly cheapskates. They use it cause it is free as in beer. Some are here, cause they think they can make a quick buck out of it for clients.

But many of those same cheapskates I bet would pay for a commercial closed source product (IF it existed) with all the polish and finesse that companies with capital could develop. Pluto was ahead of it's time. I think the potential for something like LinuxMCE has grown massively in the last 5 years and none of the major players have stepped in to fill it...yet.

40
Users / Re: Kickstarter Campaign to fund a programmer?
« on: September 09, 2013, 05:42:56 pm »
A couple thoughts:

1) In the ~5 years I've been following this project I've seen a LOT of faces come and go. I don't know if these are mostly people that get their systems running and the cast off until they hit a problem and come back for help, or mostly people who get frustrated and leave. I don't know what the distribution is.

But it's possible that the number of users that would support such a campaign is larger than the active number of users currently on this forum - IF you can somehow reach them.

2) Pitch the campaign not as a list of upgrades to the existing system but as a Full Software Solution. The current LMCE version would be referred to as a "proof of concept" (although internally the team knows it is so much more). This would make the campaign palatable to people that haven't ever HEARD of LMCE (i.e an audience that's orders of magnitude larger than the current community).

41
Users / Re: Kickstarter Campaign to fund a programmer?
« on: September 09, 2013, 02:35:16 am »
Maybe you could find people that want extravagant smart home setups.  Let them pay you to build it from the ground up(most rich people love having things they think nobody else does).  Then give it to us for free :)  Then you could have support funding and people asking you questions about stuff all the time and get payed for it(lackies doing most of the work, ME! ME!).  User error is the biggest money maker.

Installers who use Crestron and AMX already have the rich market cornered.

42
Users / Re: How can I use other devices data in events?
« on: September 04, 2013, 09:41:21 pm »
I took a really bad approach to this in my setup. But it works.

I ended up having my events call a python script which gets the relevant device data or status directly from the mysql database and interacts back with LMCE via MessageSend.

43
Users / Re: Kickstarter Campaign to fund a programmer?
« on: September 04, 2013, 07:22:36 pm »
I'd be interested. Any initial thoughts on how you would structure it? 

44
Developers / Re: Chromecast
« on: August 26, 2013, 04:48:52 pm »

45
Developers / Re: Transmission torrent on LinuxMCE
« on: August 21, 2013, 04:44:15 pm »
davegravy:
What is your level of transmission integration into lmce?  Are you currently using transmission events to trigger notifications?
J.

It's mostly not integrated, except that i have an on-complete script that Tranmission executes when a torrent completes. This on-complete script calls MessageSend which posts a pop-up notification to my orbiters. I started looking into having it also use email notification via LMCE.

Unrelated to LMCE is that I have the on-complete script calling Notify My Android to send push notices to my mobile devices.

Pages: 1 2 [3] 4 5 ... 35