jingai wrote:I may be wrong here, but shouldn't Last_X10Heartbeat be updated every time a sensor is tripped, as well as upon receipt of a heartbeat? I say this because I have two frequently used sensors that are giving me heartbeat warnings, but are working just fine. I think this is because they're delaying the heartbeat until the sensor hasn't tripped for a certain amount of time.
Ericbo wrote:Working on cleaning up my switchboard zones, I am still facing issues with the zone (monitored devices group) having a different status than the individual devices. Example:
Monitored Device Group:
* Outside Sensors
* Number Triggered Devices = 1
* Triggered in Group = Outside Entrance Sensor
Sensor Device:
* Outside Entrance Sensor
* MS14A
* off status
I did remove this sensor from the group and the group status did not change. I also forced a "turn off" on the sensor and it did not change the group status ... I am guessing my multiple updates/upgrades have messed up the group setup but trying to avoid deleting (and loosing the associated triggers/schedules...)
jingai wrote:I may be wrong here, but shouldn't Last_X10Heartbeat be updated every time a sensor is tripped, as well as upon receipt of a heartbeat? I say this because I have two frequently used sensors that are giving me heartbeat warnings, but are working just fine. I think this is because they're delaying the heartbeat until the sensor hasn't tripped for a certain amount of time.
bschollnick2 wrote:Ericbo wrote:Working on cleaning up my switchboard zones, I am still facing issues with the zone (monitored devices group) having a different status than the individual devices. Example:
Monitored Device Group:
* Outside Sensors
* Number Triggered Devices = 1
* Triggered in Group = Outside Entrance Sensor
Sensor Device:
* Outside Entrance Sensor
* MS14A
* off status
I did remove this sensor from the group and the group status did not change. I also forced a "turn off" on the sensor and it did not change the group status ... I am guessing my multiple updates/upgrades have messed up the group setup but trying to avoid deleting (and loosing the associated triggers/schedules...)
Okay, I think I know what is happening here... But I am making *LOTS* of educated assumptions here. Matt and Jay, may want to tell me that I have no idea, and I'm barking up the wrong tree here...
Switchboard may have been confused, since you forced the X10 sensor status to be off.
The X10 wireless devices (eg MS14A, DS10A, etc) are virtual devices in Indigo. The sensor devices don't send data to the X10 devices, they just store the state of the device. So you really can't "turn off" a DS10A.
The way Switchboard tracks the Heartbeat is that it detects a "duplicate" command. So for example:
* Device Sends On
* Device Sends Off
* Device Sends Off <-- Heartbeat
* Device Sends Off <-- Heartbeat
* Device Sends On
* Device Sends On <--- Heartbeat
So it is possible, that you sent the Off Command, which only updated the Indigo UI and database, since there is no way to transmit that command.
The MS14A timed out normally, and sent a X10 Off command, which Switchboard assumed was a heartbeat...
Are you seeing this on any devices that you haven't forced a status change on? And does this happen with any other devices, or just motion sensors?
- Benjamin
Ericbo wrote:But one question : can one device be included in 2 monitored device groups ? (I did that and while one updates the other does not (the one that was created first) .. Much appreciated ... Eric
DU Lou wrote:Ericbo wrote:But one question : can one device be included in 2 monitored device groups ? (I did that and while one updates the other does not (the one that was created first) .. Much appreciated ... Eric
Currently no. I asked the same question a few months ago. There is a workaround that I discovered with Indigo 6 however. You can create a Device Group and add the devices you want to monitor to those groups. Then have Switchboard monitor the Device Groups rather than the actually devices. As long as the Device Groups have a unique name you can add the same 'physical device' to multiple 'virtual' Device groups. Now there still are some devices that cannot be included in device groups i.e. Fanlinc Fans. I asked Jay to add it to the feature list
Hope that helps!
~Lou
Switchboard Error Error in plugin execution ServerReplacedElem:
Traceback (most recent call last):
File "plugin.py", line 611, in deviceUpdated
<type 'exceptions.KeyError'>: ('36224',)
Users browsing this forum: No registered users and 0 guests