It looks to have another device next to it with the same name but it is showing an icon and variable that is tripped? Checking the logs all I can ‘grep’ is as follows.
09 02/09/13 17:17:00.557 JobHandler_LuaUPnP::Run device 142 RFX Door D/0B99A1 room 0 type urn:schemas-micasaverde-com:device:DoorSensor:1 id DS/D/0B99A1 parent 39/0xe74490 upnp: 0 <0x2ac87000>
50 02/09/13 17:17:09.686 luup_log:39: RFXtrx: Found child device id DS/D/0B99A1 of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2b3bb680>
09 02/09/13 17:18:12.924 JobHandler_LuaUPnP::Run device 142 RFX Door D/0B99A1 room 0 type urn:schemas-micasaverde-com:device:DoorSensor:1 id DS/D/0B99A1 parent 39/0xc9d3b8 upnp: 0 <0x2b7bf000>
50 02/09/13 17:18:21.266 luup_log:39: RFXtrx: Found child device id DS/D/0B99A1 of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2c0f3680>
09 02/09/13 19:30:22.456 JobHandler_LuaUPnP::Run device 142 RFX Door D/0B99A1 room 0 type urn:schemas-micasaverde-com:device:DoorSensor:1 id DS/D/0B99A1 parent 39/0xeb1490 upnp: 0 <0x2b4b8000>
50 02/09/13 19:30:30.470 luup_log:39: RFXtrx: Found child device id DS/D/0B99A1 of type urn:schemas-micasaverde-com:device:DoorSensor:1 <0x2bdeb680>
UPDATE - It now does not record any more entries in the log, no matter how many times I open and close it.
You should get “cmds: D/0B99A1 Door 1 D/0B99A1 BatteryLevel 100” when opening your door and “cmds: D/0B99A1 Door 0 D/0B99A1 BatteryLevel 100” when closing your door. The “Tripped” variable will be set respectively to 1 and 0.
If you have several devices with the same altid, that’s very strange (normally impossible). Delete all these devices and reload. Then start again properly: open your door and check if the device is created (refresh your web browser). Then close your door and normally your device will be updated (Tripped set as 0).
Please replace the commented line at line 2366 in the lua file
Reload and check the RFXtrx logs in real time. Each time you open or close your door, the plugin should produce this log. If this is the case, please tell me what is logged when you open and close. If not, that could be a bug in the RFXtrx.
Edit: what(s your firmware version of Vera and RFXtrx ?
I have Alpha 6 version of the RFXCOM plugin and leaving things ‘as they were’ it still create two separate devices, one (device :142) is updated when opening and closing the door and the other (device : 141) looks to be updated after a period of time (approx 3 mins) with the status of the door.
Device 142, when open, looks to have its status reported very regularly about every minute, but not when it is closed.
Alpha 6 is very old. Please try with alpha 8. It is not normal that you have two devices created. I will investigate only after you confirm the same behaviour with alpha 8.
It is normal to have the status reported regurlarly.
Bert, it looks like messages arrives with 2 different id: 0B99A1 and 8B99A1. Note that these id are very close, just one bit difference.
Before loosing time, you and me, first we should be sure that the result is the same with a recent version of my plugin and a recent version of the RFXtrx firmware.
To be honest, that is a surprise for me to see that Visonic devices are already managed. I did not know that certain Visonic devices were using 433 MHz frequency.
On a MCT302, you have a primary contact and a secondary contact. Here is why you have 2 devices (and two sensor ids). Vera device corresponds to your main contact and Vera device 141 to your auxiliary contact. So I imagine 141 remains open because you don’t use this contact ?
I am discussing with RFXCOM to understand if it is normal to have the auxiliary contact reporting something even if not used by the user.
The other question is, if I understand, why the main contact is not reporting at the same frequency when opened or closed ?
This is what the user guide says about the auxilary contact:
Remember! If your application does not require the auxiliary input, be sure to set DIP switch SW2 to OFF and to short the input terminals together with a piece of jumper wire.
I’ve managed to turn off DIP switch 2 and put a piece of wire between the two aux points and now it seems to be working fine… It did create another device initially so I had 3, but I deleted them all and then did a reload/refresh again so I could start again…
So after moving the sensor block on the MCT-302 to simulate opening and closing the door I now have one device called “RFX Door D/0B99A1”
(Which looks to be the same name as before)
Thanks so much for your help, i’ll let you know if I notice anything strange occur.
When using the Visonic Door/Window sensor, it sends upto 3 successive notifications when a door is opened or closed. This results in 3 emails or Prowl alerts when the door is touched. Is there a way to suppress the other alerts in Vera once it has confirmed receipt of the first one?
This feature is now added: variable RepeatEvent now available for motion and door sensors: when the variable is set to 0, tripped event is notified only when the sensor state changes.
Would it be possible in a future release to have an invert variable option so that e.g a normally open (N.O) wired door bell connected directly to the MCT-302 auxiliary switch, can show up as closed, rather than always opened?
I’ve looked at the MCT-302 manual and it talks about N.O (Normally Open) but for the life of me I can’t get it to work, with an E.O.L set up and a transistor. (It would be so much easier if you could just wire it directly into the terminals and invert the readings)
So it’s my hope that an invert feature is a simple way to get around it?
Best Home Automation shopping experience. Shop at Ezlo!
)