Switchboard (Formerly Indigo Security Script)

m3rabb,

You should see this:

Code: Select all

 Switchboard Error               An unregistered X10 device has been detected.  Security ID is 243


Is this a new DS12a?

For the DS12a to create it's security code, it has to be initialized...

Press and hold the button inside the Sensor for 3-4 seconds and then release it. This initializes the Sensor and picks a random code that is used when it is registered with the Console. Replace the cover to deactivate the tamper switch.

Once this is done, trigger the sensor and see if you see anything in the Indigo log.

- Benjamin

Ben,

Thanks for the sample readout.

Good news! I got the ds12a sensors to register. I was making two mistakes:
1) I wasn't using the proper coaxial cable for the W800usb.
2) I wasn't closing the sensor after I pressed the reset button.

The bad news is I now get the following errors when I activate the sensor:

Received RF security command sensor alert (min delay) (ID 245)
Switchboard Error Master Bedroom Door [1044616659] not been assigned a Monitored Device Group.
Switchboard Warning, Master Bedroom Door, has no known heartbeat. Please check sensor!
Switchboard Warning, Front Door Sensor, has no known heartbeat. Please check sensor!
Switchboard Error Error in plugin execution ServerSentBroadcast:

Traceback (most recent call last):
File "plugin.py", line 743, in x10CommandReceived
File "plugin.py", line 688, in check_X10_Heartbeats
<type 'exceptions.KeyError'>: key id 89528181 not found in database


I was able to get rid of the heartbeat and and unassociated monitoring group errors by adjusting the settings, but I still have the following error when I activate the switch:


2012-10-17 9:46:56 PM
Received RF security command sensor normal (min delay) (ID 245)
Switchboard Error Error in plugin execution ServerSentBroadcast:

Traceback (most recent call last):
File "plugin.py", line 743, in x10CommandReceived
File "plugin.py", line 688, in check_X10_Heartbeats
<type 'exceptions.ValueError'>: empty string for float()


Do you know if the ds12a has a heartbeat signal like the ds10a?

Thanks!

File "plugin.py", line 743, in x10CommandReceived
File "plugin.py", line 688, in check_X10_Heartbeats
<type 'exceptions.ValueError'>: empty string for float()

I assume that the device that has the X10 Security ID of 245, is the new DS12A?

If you open that device, what is the X10 Heartbeat value set to?

Do you know if the ds12a has a heartbeat signal like the ds10a?

From the little information I have been able to find out about the DS12a, the answer is yes, it does have an X10 heartbeat...

- Benjamin

File "plugin.py", line 743, in x10CommandReceived
File "plugin.py", line 688, in check_X10_Heartbeats
<type 'exceptions.ValueError'>: empty string for float()

I assume that the device that has the X10 Security ID of 245, is the new DS12A?

Correct.

If you open that device, what is the X10 Heartbeat value set to?

Ah, the field is empty, thus the empty string error. I erased the default number of 200 when I thought the sensor didn't use a heartbeat.

I reset the heartbeat field to 4. When I trigger the sensor, I still get the following errors:

Code: Select all

2012-10-18 11:41:13 AM
  Received RF                     security command sensor normal (min delay) (ID 245)
  Switchboard                     Warning, Master Bedroom Door, has no known heartbeat.  Please check sensor!
  Switchboard                     Warning, Front Door Sensor, has no known heartbeat.  Please check sensor!
  Switchboard Error               Error in plugin execution ServerSentBroadcast:

Traceback (most recent call last):
  File "plugin.py", line 743, in x10CommandReceived
  File "plugin.py", line 688, in check_X10_Heartbeats
<type 'exceptions.KeyError'>: key id 89528181 not found in database


(FYI, I have two ds12a sensors; one on the front door and one on the master bedroom door.)

Please let me know if there is anything else I can do to help debug this problem.

Thanks,

Maurice

Switchboard v0.70 has been released.

The changes in v0.70 are as released...

v0.70 - 9/02/2012 - Public Release

• When the plugin is started, it will audit the Monitor Device Groups and detect which devices are triggered, and update the Number_Triggered_Devices, Devices_Triggered, and Triggered_In_Group states as necessary.
• X10 HeartBeat Time Out Warnings - X10 devices send out a periodic heartbeat, the original security script monitored for these, and warned the user if the heart beat had not been seen after several hours. This was not properly implemented in Switchboard. This feature is now available again.
  
  • Please note, you will need to open each X10 device, and then Save it. This will write the new fields to the X10 device…
  • This timeout is configurable on a per device basis. The default value is 200 minutes, roughly 3 1/3 hours... Since the heartbeat on X10 devices is 45 minutes - 1 hour, this seems to be a reasonable amount of time for the Heartbeat Timeout...
• Custom Email Text
• Fixed Trigger_in_Group / Number_Triggered_Devices. When implemented in v0.60, I did not realize that X10 devices were being ignored. They will now appear properly in the Trigger_In_Group / Number_Triggered_Devices...

Please feel free to send feedback, comments, and concerns.

https://dl.dropbox.com/u/241415/Switchb ... 0v0.72.zip

Thanks a lot for the heartbeat monitor function but sorry, though reading thru and thru, could no figure how I could get an email sent when one of the heartbeat monitor triggers (times out). Is that possible ? Thank you !

Thanks a lot for the heartbeat monitor function but sorry, though reading thru and thru, could no figure how I could get an email sent when one of the heartbeat monitor triggers (times out). Is that possible ? Thank you !

I didn't have a chance to finish the email portion of the Heartbeat timeout.

The next version, which I expect to be have ready within the next week, will offer the email notification.

- Benjamin

Thanks a lot for the heartbeat monitor function but sorry, though reading thru and thru, could no figure how I could get an email sent when one of the heartbeat monitor triggers (times out). Is that possible ? Thank you !

I didn't have a chance to finish the email portion of the Heartbeat timeout.

The next version, which I expect to be have ready within the next week, will offer the email notification.

- Benjamin

Wow .. that is fast, I am setting up a full set of sensors for the house and will be happy to start monitoring their batteries once you release your next version

Dear Ben,
I am switching from the Security Script to your new Switchboard. I found that it is very good enhancement overall. No more need to define devices on the matrix or poke into applescript, and a sort of new possibilities. However, I have some aspects that I would like to clarify. First, my setup. I have a SC9000 alarm (some KR21 remotes), and a CM15 USB linked to Indigo on ML 10.8.2.
a) the log is telling me about the KR2:
Switchboard Warning, Remote_1, has no known heartbeat. Please check sensor!
Switchboard Warning, Remote_2, has no known heartbeat. Please check sensor!

Each KR21 was defined with a separate ID ant into a general remotes group. Can I stop that from appearing?

b) I can not figure out the right way to define the Marmitek SC9000 in the system. Right now I just have a normal device, with its address, to tell me when it is on or off. Is there a way to define within the switchboard plugin? Using my approach i am unable to detect with Indigo when you manually arm/disarm/turn into home mode the console. I can just detect it when using the remotes.

c) the switchboard defined devices does not appear in Indigo Touch. I know that I can define some variables to mimic the switchboard devices, but it would be nice to have those directly there. Maybe this is more a question to Matt and/or Jay...

d) I am not consistently getting the same state between the switchboard device and the SC9000 for a particular x10 module (DS90's) , and I can not understand why. I'll try to better explain the problem: If I open a door with a DS90, the SC9000 acknowledges with its typical two tone, then I close the door, and the SC9000 receives the 'closed' command. The corresponding device in Switchboard, however, stays on 'open'. This behaviour is not consistent, sometimes I get the closed status, sometimes not. All my MS90's are consistent, though.

That's all, Hope it is not too much...

Thank you very much and keep the nice work!

Ben,

I'm seeing this error:

v 14, 2012 6:52:54 PM
Indigo Cocoa client disconnected (10.0.1.28)
Indigo Cocoa client authenticated (10.0.1.28)
Reloading plugin "Switchboard 0.74"
Stopping plugin "Switchboard 0.74" (pid 211)
Plugin "Switchboard" disconnected
Starting plugin "Switchboard 0.74" (pid 235)
Plugin "Switchboard" connected
Plugin "Switchboard 0.74" started
Switchboard Switchboard is Monitoring X10 communications
Switchboard Switchboard is Monitoring Insteon communications
Switchboard Updating Monitored Device Zone 'Door Sensors'
Switchboard Updating Monitored Device Zone 'KeyFobs'
Switchboard Error Error in plugin execution startup:

Traceback (most recent call last):
File "plugin.py", line 617, in startup
File "plugin.py", line 243, in re_init_zones_with_trigger_status
<type 'exceptions.KeyError'>: key id 1953152192 not found in database

I am switching from the Security Script to your new Switchboard. I found that it is very good enhancement overall. No more need to define devices on the matrix or poke into applescript, and a sort of new possibilities. However, I have some aspects that I would like to clarify. First, my setup. I have a SC9000 alarm (some KR21 remotes), and a CM15 USB linked to Indigo on ML 10.8.2.
a) the log is telling me about the KR2:
Switchboard Warning, Remote_1, has no known heartbeat. Please check sensor!
Switchboard Warning, Remote_2, has no known heartbeat. Please check sensor!

Each KR21 was defined with a separate ID ant into a general remotes group. Can I stop that from appearing?

Not currently... I will look into adding that to the X10 device preference...

b) I can not figure out the right way to define the Marmitek SC9000 in the system. Right now I just have a normal device, with its address, to tell me when it is on or off. Is there a way to define within the switchboard plugin? Using my approach i am unable to detect with Indigo when you manually arm/disarm/turn into home mode the console. I can just detect it when using the remotes.

As far as I can tell, the SC9000 doesn't send any X10 signal when it's state changes. If there is a serial adapter, or some other source of information, I maybe able to add something to the plugin. But right now, the plugin will only be able to act on X10 or Insteon signals.... So I don't think there is a way to read the SC9000's state at this time.

c) the switchboard defined devices does not appear in Indigo Touch. I know that I can define some variables to mimic the switchboard devices, but it would be nice to have those directly there. Maybe this is more a question to Matt and/or Jay...

That is my understanding. Indigo touch only works with Indigo native devices, and does not currently support Plugins, or custom devices.... Assuming that I remember the conversation with Jay correctly....

d) I am not consistently getting the same state between the switchboard device and the SC9000 for a particular x10 module (DS90's) , and I can not understand why. I'll try to better explain the problem: If I open a door with a DS90, the SC9000 acknowledges with its typical two tone, then I close the door, and the SC9000 receives the 'closed' command. The corresponding device in Switchboard, however, stays on 'open'. This behaviour is not consistent, sometimes I get the closed status, sometimes not. All my MS90's are consistent, though.

My best guess is that your suffering from X10 transmission issues.... What are you using with Indigo to read the X10 security codes? A TM751?

The SC9000 is reading the broadcast from the X10 modules, but whichever transceiver your using, is probably in a different location? It's possible that there is some interference that is sometimes blocking or damaging the RF signal?

- Ben

Indigo Cocoa client disconnected (10.0.1.28)
Indigo Cocoa client authenticated (10.0.1.28)
Reloading plugin "Switchboard 0.74"
Stopping plugin "Switchboard 0.74" (pid 211)
Plugin "Switchboard" disconnected
Starting plugin "Switchboard 0.74" (pid 235)
Plugin "Switchboard" connected
Plugin "Switchboard 0.74" started
Switchboard Switchboard is Monitoring X10 communications
Switchboard Switchboard is Monitoring Insteon communications
Switchboard Updating Monitored Device Zone 'Door Sensors'
Switchboard Updating Monitored Device Zone 'KeyFobs'
Switchboard Error Error in plugin execution startup:

Traceback (most recent call last):
File "plugin.py", line 617, in startup
File "plugin.py", line 243, in re_init_zones_with_trigger_status
<type 'exceptions.KeyError'>: key id 1953152192 not found in database

Double check the KeyFobs Monitored device zone, and see that everything is okay in there...
And double check the Indigo device with the ID of 1953152192. What is it? If it's a custom device, is it configured correctly?

Thanks Ben for your reply and advice. However, I do not fully understand the last answer. To my (very limited) understanding, isn't the sc9000 itself that acts a transceiver for the ds90's, is it? If it is not, another possibility is the cm15 pro, to which the Mac is connected via USB. Or perhaps both are receiving the detection signal from the Ds90's ? Because if both transceivers receive the signal, it may be a location problem, since the sc9000 always receive the 'correct' signal. Could you please elaborate on this 'signal path' a little more to clarify?

Thanks Ben for your reply and advice. However, I do not fully understand the last answer. To my (very limited) understanding, isn't the sc9000 itself that acts a transceiver for the ds90's, is it? If it is not, another possibility is the cm15 pro, to which the Mac is connected via USB. Or perhaps both are receiving the detection signal from the Ds90's ? Because if both transceivers receive the signal, it may be a location problem, since the sc9000 always receive the 'correct' signal. Could you please elaborate on this 'signal path' a little more to clarify?

Since I don't have an SC9000, I don't know. The documentation for the SC9000 doesn't discuss how the sensor signal is received by the SC9000. I presume that the SC9000 does have a more powerful transceiver built-in to it, but that's an assumption.

So you have an CM15 Pro? Can you move that closer to the SC9000?

- Ben

Seeing this error for X10 Security system key fobs.

Switchboard Error Watchdog error. No Heartbeat for Sensor: Marys Keyfob, please check sensor battery.
Switchboard Error Watchdog error. No Heartbeat for Sensor: Daves Keyfob, please check sensor battery.

[quote="bschollnick2"][quote="davehale"]
Indigo Cocoa client disconnected (10.0.1.28)
Indigo Cocoa client authenticated (10.0.1.28)
Reloading plugin "Switchboard 0.74"
Stopping plugin "Switchboard 0.74" (pid 211)
Plugin "Switchboard" disconnected
Starting plugin "Switchboard 0.74" (pid 235)
Plugin "Switchboard" connected
Plugin "Switchboard 0.74" started
Switchboard Switchboard is Monitoring X10 communications
Switchboard Switchboard is Monitoring Insteon communications
Switchboard Updating Monitored Device Zone 'Door Sensors'
Switchboard Updating Monitored Device Zone 'KeyFobs'
Switchboard Error Error in plugin execution startup:

Traceback (most recent call last):
File "plugin.py", line 617, in startup
File "plugin.py", line 243, in re_init_zones_with_trigger_status
<type 'exceptions.KeyError'>: key id 1953152192 not found in database[/quote]

Double check the KeyFobs Monitored device zone, and see that everything is okay in there...
And double check the Indigo device with the ID of 1953152192. What is it? If it's a custom device, is it configured correctly?[/quote]


I don't have a device with that ID.

As best I can tell the keyfobs are set up correctly. At least, they work.