Where is the apk for the new orbiter? I went to android market and it shows as installed. I downloaded that one several weeks ago.

As per the wiki, golgoj4 has his nightly builds hosted from his website: http://www.lasmarthomes.com/QOrbiter-release.apk

Great news! I should be around today and tomorrow evening to test on my Transformer Prime. Send me a note in IRC when you're ready.

My system uses IAX instead of SIP and has issues. Also, my core softphone does not work, whereas my MD softphone does. See my thread about the issue: http://forum.linuxmce.org/index.php/topic,12304.15.html

One thing I missed: LinuxMCE already has support for the GC-100 line from GlobalCache. Those little device can be used in quite a lot of scenarios.

As per my other thread, I haven't had much luck with reliability from my GC-100 - but i'm still investigating the reasons.

It is not live data in web admin, but the last data that it was set to. And it is read from the database, afaik.

Ahh okay. Well I'm not clear on the difference between that and live data. It seems to update immediately after house mode changes, so i think it's good enough for my uses. I'll dig through the database and hopefully I can find and pull the data from there within my scripts.

Thanks

My core will only return the default data, not the live data (at least for house mode).
J.

I get this for all the device data I've tried (and I tried 6 or 7 examples).

It's funny because the live data is visible in webadmin, so it IS accessible somehow... the question is: How?

Hi,
Did you see if the unit is also unresponsive with the GC utilities? See my (fairly) recent post, from Windows, Mac and possibly other OS'es you can directly communicatie with the GC100...
HTH,

I retried the test above using their itest.exe utility from windows, and did not have a single dropped request. Looks like it's LinuxMCE.

I ran a test switching the relay once per second continuously from a bash script, and watching the link light on the GC-100 network card.

For the first 20 seconds it responds normally (1 flash per second). Then it gradually starts dropping requests until after a minute it is completely unresponsive.

Any ideas what might cause this?

My GC-100 spontaneously and sporadically drops communication. I don't know if this is a problem with my specific unit, GC-100s in general, or LinuxMCE. Sometimes the unit regains its connection and resumes normal operation on its own. Other times I need to reset the device (via webadmin, or reload router).

Here are some log samples from me switching a relay back and forth:

Normal Operation:

Code:

10      03/15/12 15:20:02.477           Receive string: MESSAGE 77             <0xb6cffb70>
10      03/15/12 15:20:02.477           Received MESSAGE 77             0x9f1b040 device: 163 <0xb6cffb70>
10      03/15/12 15:20:02.477           Received Message type 1 ID 192 from 0 to 207 (device: 163) resp 0 <0xb6cffb70>
10      03/15/12 15:20:02.477           Message for Siren passed to Relay <0xb6cffb70>
10      03/15/12 15:20:02.477           Relay Pwr.: target device is 207 <0xb6cffb70>
10      03/15/12 15:20:02.477           gc100::GetPinDeviceID got pin 3:2 device 209 <0xb6cffb70>
10      03/15/12 15:20:02.477           Relay Pwr.: This device is 209 <0xb6cffb70>
21      03/15/12 15:20:02.477           lock(0x9f1b3f0) (>1069) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:20:02.477           acquired(0x9f1b3f0) #0 (>1069) gc100 gc100.cpp:1198  <0xb6cffb70>
10      03/15/12 15:20:02.477           Relay Pwr.: Found 3:2 in module map <0xb6cffb70>
10      03/15/12 15:20:02.477           Relay Pwr.: Regardless, module ID is 3:2 <0xb6cffb70>
10      03/15/12 15:20:02.477           Sending command setstate,3:2,1
 <0xb6cffb70>
10      03/15/12 15:20:02.486           Reply received from GC100: state,3:2,1 <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply interpreted as module: 3:2 change to 1 <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: found module of type RELAY, 2 <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 1) default state: 1 <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 1) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 1) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 1) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 1) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 1) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.486           statechange Reply: no exact match in m:s format, trying global pin number <0xb58fdb70>
05      03/15/12 15:20:02.486           statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb58fdb70>
10      03/15/12 15:20:02.536           EventThread <0xb58fdb70>
21      03/15/12 15:20:02.578           unlock(0x9f1b3f0) #0 (>1069) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:20:02.578           removed from map (0x9f1b3f0) #0 (>1069) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6cffb70>
10      03/15/12 15:20:02.593           Receive string: MESSAGE 72             <0xb6cffb70>
10      03/15/12 15:20:02.593           Received MESSAGE 72             0x9f1b040 device: 163 <0xb6cffb70>
10      03/15/12 15:20:02.593           Received Message type 1 ID 193 from 0 to 207 (device: 163) resp 0 <0xb6cffb70>
10      03/15/12 15:20:02.593           Message for Siren passed to Relay <0xb6cffb70>
10      03/15/12 15:20:02.593           Relay Pwr.: target device is 207 <0xb6cffb70>
10      03/15/12 15:20:02.593           gc100::GetPinDeviceID got pin 3:2 device 209 <0xb6cffb70>
10      03/15/12 15:20:02.593           Relay Pwr.: This device is 209 <0xb6cffb70>
21      03/15/12 15:20:02.593           lock(0x9f1b3f0) (>1094) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:20:02.593           acquired(0x9f1b3f0) #0 (>1094) gc100 gc100.cpp:1198  <0xb6cffb70>
10      03/15/12 15:20:02.593           Relay Pwr.: Found 3:2 in module map <0xb6cffb70>
10      03/15/12 15:20:02.593           Relay Pwr.: Regardless, module ID is 3:2 <0xb6cffb70>
10      03/15/12 15:20:02.593           Sending command setstate,3:2,0
 <0xb6cffb70>
10      03/15/12 15:20:02.602           Reply received from GC100: state,3:2,0 <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply interpreted as module: 3:2 change to 0 <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: found module of type RELAY, 2 <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 4:1 (state 0) default state: 1 <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 4:2 (state 0) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 4:3 (state 0) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 5:1 (state 0) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 5:2 (state 0) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: testing Command_Impl2 Dev #, 5:3 (state 0) default state:  <0xb58fdb70>
10      03/15/12 15:20:02.602           statechange Reply: no exact match in m:s format, trying global pin number <0xb58fdb70>
05      03/15/12 15:20:02.602           statechange Reply: Sorry, after all that searching, I can't determine which child device should be sent the pin_changed <0xb58fdb70>
10      03/15/12 15:20:02.652           EventThread <0xb58fdb70>
21      03/15/12 15:20:02.693           unlock(0x9f1b3f0) #0 (>1094) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:20:02.693           removed from map (0x9f1b3f0) #0 (>1094) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6cffb70>

When it messes up:

Code:

10      03/15/12 15:26:22.289           Receive string: MESSAGE 77             <0xb6cffb70>
10      03/15/12 15:26:22.289           Received MESSAGE 77             0x9f1b040 device: 163 <0xb6cffb70>
10      03/15/12 15:26:22.289           Received Message type 1 ID 192 from 0 to 207 (device: 163) resp 0 <0xb6cffb70>
10      03/15/12 15:26:22.290           Message for Siren passed to Relay <0xb6cffb70>
10      03/15/12 15:26:22.290           Relay Pwr.: target device is 207 <0xb6cffb70>
10      03/15/12 15:26:22.290           gc100::GetPinDeviceID got pin 3:2 device 209 <0xb6cffb70>
10      03/15/12 15:26:22.290           Relay Pwr.: This device is 209 <0xb6cffb70>
21      03/15/12 15:26:22.290           lock(0x9f1b3f0) (>5415) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:26:22.290           acquired(0x9f1b3f0) #0 (>5415) gc100 gc100.cpp:1198  <0xb6cffb70>
10      03/15/12 15:26:22.290           Relay Pwr.: Found 3:2 in module map <0xb6cffb70>
10      03/15/12 15:26:22.290           Relay Pwr.: Regardless, module ID is 3:2 <0xb6cffb70>
10      03/15/12 15:26:22.290           Sending command setstate,3:2,1
 <0xb6cffb70>
21      03/15/12 15:26:22.390           unlock(0x9f1b3f0) #0 (>5415) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:26:22.390           removed from map (0x9f1b3f0) #0 (>5415) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6cffb70>
10      03/15/12 15:26:22.404           Receive string: MESSAGE 72             <0xb6cffb70>
10      03/15/12 15:26:22.404           Received MESSAGE 72             0x9f1b040 device: 163 <0xb6cffb70>
10      03/15/12 15:26:22.404           Received Message type 1 ID 193 from 0 to 207 (device: 163) resp 0 <0xb6cffb70>
10      03/15/12 15:26:22.404           Message for Siren passed to Relay <0xb6cffb70>
10      03/15/12 15:26:22.404           Relay Pwr.: target device is 207 <0xb6cffb70>
10      03/15/12 15:26:22.404           gc100::GetPinDeviceID got pin 3:2 device 209 <0xb6cffb70>
10      03/15/12 15:26:22.404           Relay Pwr.: This device is 209 <0xb6cffb70>
21      03/15/12 15:26:22.404           lock(0x9f1b3f0) (>5440) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:26:22.404           acquired(0x9f1b3f0) #0 (>5440) gc100 gc100.cpp:1198  <0xb6cffb70>
10      03/15/12 15:26:22.404           Relay Pwr.: Found 3:2 in module map <0xb6cffb70>
10      03/15/12 15:26:22.404           Relay Pwr.: Regardless, module ID is 3:2 <0xb6cffb70>
10      03/15/12 15:26:22.404           Sending command setstate,3:2,0
 <0xb6cffb70>
21      03/15/12 15:26:22.505           unlock(0x9f1b3f0) #0 (>5440) gc100: gc100.cpp:1198  <0xb6cffb70>
21      03/15/12 15:26:22.505           removed from map (0x9f1b3f0) #0 (>5440) gc100: gc100.cpp:1198  was: 2 size, now 1 Rel: Y Got: Y <0xb6cffb70>

Note that linuxmce does not seem to retry its communications when no response is received, or to reset the device.

Has anyone experienced something similar?

Does anyone know (in the meantime until I can get this sorted out) how I can manually force reset the device from the command-line (without reloading router)?

I think I figured out how to do it _IN THEORY_

General Info Plugin has a command "Get Device Data" which accepts a device ID and Device Data ID

Security Info Plugin has a device data field #59 called "Configuration" which stores the current housemode.

Only problem is that MessageSend is returning a blank for some reason.

Code:

root@dcerouter:~# /usr/pluto/bin/MessageSend localhost -o 0 4 1 68 2 "13" 5 "" 52 "59" 53 0
0:OK
5:

Unless I ask for the default device data value (i.e not live):

Code:

root@dcerouter:~# /usr/pluto/bin/MessageSend localhost -o 0 4 1 68 2 "13" 5 "" 52 "59" 53 1
0:OK
5:0,2,

Anyone know why this is?

Don't mean to be rude, but your question suggests you haven't done a lot of research. In my experience, this community can be very helpful to those who have demonstrated they've put in the effort themselves to find the answers first. To others, not so much. Yes, the information isn't organized very well.

You should get any modern consumer-grade NVIDIA chipset card, but you should still read the wiki/forums to understand why.

A word of caution- make sure the morse-code sequence for disarming the system and the one for detonating the short-range nuclear device are sufficiently different. It sounds silly to mention but it catches out the most experienced users from time to time.

I don't have one of those, but I was hoping to have a sequence which initiates the conversion from "regular house" into sex-pad (giggidy-giggidy). I'll heed your advice, as it would be awkward bringing the in-laws into such an environment. 

Hi Phenigma,

I'm very interested to know how you use Messagesend to return device status. I looked in the wiki and it wasn't apparent to me. If you get a chance to check I'd be grateful to know how you accomplish this..

Thanks,

David

I'm interested in something opposite of Messagesend. Is it possible to determine device status, or housemode, etc from the command-line?

One example of why I ask is that I have a doorbell event which launches a bash script and does a variety of different things:

1) If the user has simply pressed the doorbell that's one branch.
2) If the user has pressed the doorbell in the correct morse-code sequence, the system gets disarmed.

A) If the housemode is armed or vacation, and 1 happens, the script sends an SMS message to myself and my wife saying that the doorbell was rung.
B) If the housemode is unarmed, secure-at-home, or entertaining, and 1 happens, the script rings the doorbell
C) If 2 happens, and the housemode was armed or vacation, the script sends an SMS to myself and my wife saying that the system was disarmed via the doorbell.
D) If 2 happens, and the housemode was sleep, the script rings the doorbell.

I've created rather complicated logic within a bash script to log the times for which doorbell push and release events occur, and to interpret these as morse code.

I'd rather not have to create and manage a bunch of respond-to events within web-admin (with various criteria), and then re-use the Morse-code interpretation routine within each event. Preferable would be to have one doorbell push event, one doorbell release event, and then test the various criteria within the code.

Sorry for the drawn out explanation. Is this doable?

I'm in the process of migrating the 1980s DSC alarm system that came with the house I purchased, over to Linuxmce. I've moved all the sensor lines from the alarm panel to my GC-100, and I've also wired a doorbell to the unit. Now I'm wondering what to do about the siren and doorbell notifications.

I realize I could have security breaches trigger an event to play a sound file on all my MDs. The problem is that I have my MDs sleeping most of the time, and I don't want to wait for them to wake before playing a siren or doorbell sound. I could play on my Hybrid, but then I get only localized output (won't be able to hear on the other side of the house).

I'm considering adding an additional sound-card to my Hybrid, assigning a squeeze-server to that output, and connecting this output to a distribution amplifier (wired to the existing DSC horns around the house). I would hopefully be able to send commands to this device, when appropriate, to play siren and doorbell sounds (or any other future whole-house notification sounds... intercom?), without interfering with the primary hybrid audio device operation.

Does this seem like a valid approach? I haven't used squeezeserver before and don't know if what I'm proposing is viable.