Philio PSP01-2 and Monoprice Shock Sensor

Other Devices & Integrations Door Locks & Sensors
1

I bought the Philio for the light sensor but it also has Temp and Motion. I have a scene setup that when a pin code is used on the front door it turns on a lamp module for 2 minutes and then turns off but it does this during the day also. I edited the scene and added the light sensor and set it to less than 2 Lux but the scene does not work pin code and Lux < 2. The scene does pin code or Lux < 2.

Is there a simple way to make it to where the pin code is entered and the light level below 2 Lux to turn on the lamp Module?

Also the temp and light level does not get updated to Vera until the motion goes off. In the instructions it says Auto report Illumination time is 30 minutes per tick and minimum time is 30 minutes, default tick is 12 (6 Hours). Same thing for the auto report temperature. In the instruction under Z-wave Configuration Settings there is 12 different settings but I don’t have a clue where or how to change the settings. I will not be using the motion part of the sensor. Temp and light levels updating every 6 hours will not work for what I want to do. The temp feature is cool but again updating every 6 hours is not much use.

What is a tick and how do I change the tick?
Do all sensor that detect light work the same way or is there a better sensor?

I got a Monoprice Shock Sensor. My plan was to attach the sensor to my front door and if someone knocks on the door it will trigger but with the sensitivity all the way down it detects the vibration when closing the front door. Well that didn’t work. In the instructions it shows two contacts inside the sensor and if used will send a alarm to Vera. I hooked up a alarm contact and when it triggers it sends a tamper not alarm to Vera. Vera does nothing with the Tamper. I figured since the vibration didn’t work I would use it as a door sensor with the contact wired to the terminals inside the sensor.

Is there a way to change it from a tamper to alarm signal to Vera or for Vera to do something with the Tamper?

Thanks
Jim

2

I just noticed that your device (and issue) looks very similar to mine, which I just described in a separate thread:

http://forum.micasaverde.com/index.php/topic,24844.0.html

Have you figured out how to be notified of tamper alarm?

3

With the standard D_MotionSensor1.json provided with the Vera, TAMPER does not trigger a scene or notification.

You can get around this limitiation in a number of ways…

  1. If you use PLEG, test for SID = “urn:micasaverde-com:serviceId:HaDevice1”, variable “sl_TamperAlarm”, value = “1” to trigger your action.
  2. Modify the device json to include an entry under eventList2 that can be used for triggering a notification or a scene.

The entry you will need to add to the json file is:

        {
            "id": 6,
            "label": {
                "lang_tag": "ui7_door_window_motion_sensor_is_tampered",
                "text": "Whenever _DEVICE_NAME_ detects TAMPER whether is armed or disarmed"
            },
            "serviceId": "urn:micasaverde-com:serviceId:HaDevice1",
            "serviceStateTable": {
                "sl_TamperAlarm": {
                    "value": "1",
                    "comparisson": "="
                }
            }
        }

Note 1: Change the ‘ID: “6”’ to be the next ID number is sequence.
Note 2: The text above reflects a motion sensor… the device json for the shock sensor should have slightly different wording.

4

Thank you!! I’ll give this a try :slight_smile:

5

I returned my sensor to the seller.

6

Thank you very much, cybrmage! I’ll go with solution 2 and modify the json for that device - but can you please point me to the documentation for device json files (where they are located, how to modify them (simply in the filesystem or through the UI?), what the dictionary keys and values are, etc.) as I could not find it.
Thank you!

7

Works great - thanks! I’m just not sure what the best way to modify a device json is (I uploaded a new one, then set the device_json field in the Advanced device settings to the new filename, and it all works, but the device_json field gets mysteriously reset to the original value although the new one has effect…).

I’d be very grateful if somebody could clarify what the “official” way to upload a modified json is!

In the meantime, I have also found a third possible solution to the problem: in the Startup Lua for the Vera Edge, I added the following code:

[code]function reportTamper(lul_device, lul_service, lul_variable, lul_value_old, lul_value_new)
– do something, e.g. trigger a scene
end

luup.variable_watch(“reportTamper”,“urn:micasaverde-com:serviceId:HaDevice1”,“sl_TamperAlarm”, 58);
[/code]