Micasaverde sell this sensor but I wonder if it’s supported properly. The sensor adds as a motion detector as opposed to a door/window sensor. It is still usable but is there any way to have it properly recognized as as a window sensor?
I changed mine from a motion sensor to door/window sensor by changing the device_type to urn:schemas-micasaverde-com:device:DoorSensor:1 and the device_file to D_DoorSensor1.xml under Advanced.
My problem is trying to reverse “tripped” so that it turns on the light when the door is CLOSED not when its opened. The reason I want to do this because I have it associated with a light switch, so the device controls the light without having to use a scene. And simply changing the “Tripped” variable doesn’t work because the device changes it back once it wakes up and configures itself.
Any ideas?
[quote=“philiphill, post:2, topic:178733”]I changed mine from a motion sensor to door/window sensor by changing the device_type to urn:schemas-micasaverde-com:device:DoorSensor:1 and the device_file to D_DoorSensor1.xml under Advanced.
My problem is trying to reverse “tripped” so that it turns on the light when the door is CLOSED not when its opened. The reason I want to do this because I have it associated with a light switch, so the device controls the light without having to use a scene. And simply changing the “Tripped” variable doesn’t work because the device changes it back once it wakes up and configures itself.
Any ideas?[/quote]
Look into PLEG to accomplish this. Also be careful when changing the Device Type and D_xxx.xml for the device. Though there is no issue for this device as Door, Window and Motion devices are all the same, you can mess things up. This is purely a cosmetic thing and not a functional thing.
- Garrett
Thanks Garrett! I may have to look into PLEG if I can’t figure out how to do this through configuring the device. I find it hard to believe that the device maker would assume that you only want to trigger an associated light when the door is closed. But I may be wrong. 
Oops I meant when a door is opened…
Changing the device type certainly works but you also need to manually add the device options. I find the need to do this on a device sold by MCV themselves a bit strange.
Device is not inside the zwave_products_sys.xml - that’s why will not be recognized.
Open a ticket from your Vera - this could be the fastest way 
Actually all 3 sensors are recognized and they all function without making any mods to your VERA. The switching from a motion to a door sensor is only cosmetic and works as a motion. However, the door/window capability is designed to be associated with a light that it turns on/off. Or you have to disable that default behavior because it will resets itself back to a non-tripped state after 5 seconds in order to automatically turn off the light. I figured out on my own how to disable that by setting option 6 to 1 byte dec with a variable of 46. I’m just trying to use it like it was designed, except reverse “tripped” so that it turns on my light when the door is closed NOT when its opened since I’m not using it on an external door which maybe you can’t change. It’s actually a really nice device and would work perfect out of the box “IF” you place it on an external door and have it turn on a light when the door is opened and allow it to automatically turn it off in 5 seconds.
And yes, I did open a ticket with MCV 5 days ago and they haven’t been able to tell me how to simply configure the device that I bought from them. They have just given me suggestion to try, but not actually a solution.
I’ve been testing the PSM-01 light sensor, and trying to trigger scenes when brightness reaches above and below defined thresholds (80 and 66). I’m not finding it reliable at all, and have disabled the triggers while I investigate. It appears to false trigger (high and low in quick succession) but I’ve not got any evidence to prove it. Maybe I need use datamine plugin to plot readings over time to see what is going on.
Anyone else experience issues with brightness triggers on this device?
Anyone recommend a better reliable device for monitoring brightness levels (EU zwave frequency)? Thanks
I have 2 HSM100-S3. I found them quite reliable. There must be an european version too.
I was wondering if anyone noticed the same strange behavior as I did.,. I installed this Philio PSM01 sensor on some of my windows and when I open that window, the sensor gets tripped and the icon on my dashboard turns red (as it should) but after about a 30 seconds or so, the icon reverts back to not tripped (green icon) even though my window is still opened
I have 10 AeonLabs window sensors and 3 Philio PSM01 sensors; all 3 PSM01 react the same way
The only thing I had changed when I installed these PSM01 sensor was the polling time to be at every 5 minutes (instead of 30 minutes if I recall) But a 5 minutes of polling-time is the same setting I use on my other AeonLabs sensor and I do not have this problem.
Any idea anyone?
Thx
Claude