forum

Hi.

I have set up a logical rule that tells a powerswitch to turn off if there is no movement. However, there is a long delay in the system. The motion detector seems to send the "triggered" signal every 4-5 minutes.

When I press the "update all" button in the expert ui, the motion device does not respond imidiate like the powerswitch. See image:



Why?

I don't know this for sure it's just a guess, but it seems like there might be issues with sensors at the moment, and/or the device is battery powered and it's still not waking even though it should to update (or both).

Recently I was playing with a water sensor and noticed the u.i. would do nothing when the alarm was triggered. The only way I could get the u.i. to trigger an event on water detection was to make sure the device was being triggered when z-way talked to it during it's next scheduled communication (5 minutes).

I'm not sure if it's the exact same issue, but I'm guessing that z-way will update during it's next scheduled update (probably every 5 minutes as well) instead of waking the device and updating immediately. Does the device eventually update, or is it forever hibernating?

Hi Erasmuz.

The device updates after 4-5 minutes.

If I use the device with Fibaro Home Center, it works like a charm. Imidiate response when motion is detected....

This renders the motion detector useless for me.

firmware 2.0 i guess?
had the same problems, webserver slow, also waiting for socket etc
v2.0 is very instable, went back to 1.7.2 and is working smooth again

It's good to know it works in 1.7.2. Hopefully that means it will get fixed quickly.

Just like Rappo this was a deal killer for me and the razberry. The reason I started my z-wave network was to get an alarm if my sump pump water level got too high and the sump pump didn't turn on. Sadly I had to buy and setup a vera edge controller and am now using the razberry as a secondary controller so I can continue to help debug and toy with development. I really like the razberry device though so hopefully soon I can go back to the razberry being my main controller.

Can someone clearly state what is the problem with v2.0? We need some reasonable feedback

I can try, but I have not had enough time to watch logs as events happen to give a 100% sure explanation of what is going on.

It seems as though alarms from devices aren't immediately caught by the z-way ui. From messing with the devices I have that will broadcast alarms it seems as though when an alarm is sent to the z-wave chip the ui does nothing with the alarm to notify the user, or to be able to trigger an event (such as email, sms, etc).

From my testing (haven't tried retesting since 2.0.0rc28) alarm class object's are not even shown in the u.i.
For instace: I have an Everspring Flood Detector (ST812) which I can successfully add to my network and give it the correct ZDDX, but I get no elements/widgets in the ui to attach events for. The device says it uses ALARM_REPORT and SENSOR_ALARM_REPORT command classes, but it seems as though the u.i. does nothing to indicate an alarm trigger from these classes, or an element in the u.i. to use in triggers.

Another Instance: I have a Fibaro Flood Sensor FGFS-101 which again I can successfully put into my network and associate the correct ZDDX file for. This device uses binary switches for when an alarm is happening along with the alarm classes. With this device I can see the switch status in the u.i., and if the alarm is being triggered when an update happens it correctly updates the status in the u.i., but again there is no user feedback from the ALARM class that was sent from the device to the z-wave chip when the alarm was triggered.

I had plan on doing some more in depth testing to find the root cause of all this, but have been bust recently. Hopefully that will at least give enough info to find the problem.

PoltoS wrote:Can someone clearly state what is the problem with v2.0? We need some reasonable feedback

Yes, I can!!

I use several Philio PSM02-1 Sensors all the time with very reliable behaviour.

But now some of them will no longer show motion in the ui because of following problem reported in the log:

[2014-12-14 11:56:06.463] [D] [zway] RECEIVED: ( 01 0A 00 04 00 1D 04 30 03 FF 0C 28 )
[2014-12-14 11:56:06.465] [D] [zway] SENT ACK
[2014-12-14 11:56:06.468] [D] [zway] SETDATA devices.29.data.lastReceived = 0 (0x00000000)
[2014-12-14 11:56:06.470] [W] [zway] Node 29:0 CC SensorBinary: Unsupported sensor type 12 received, ignoring


Other philio sensors (definitively the same type) show the following proper log for motion detected:

[2014-12-14 11:44:21.582] [D] [zway] RECEIVED: ( 01 0A 00 04 00 0B 04 30 03 FF 0C 3E )
[2014-12-14 11:44:21.584] [D] [zway] SENT ACK
[2014-12-14 11:44:21.585] [D] [zway] SETDATA devices.11.data.lastReceived = 0 (0x00000000)
[2014-12-14 11:44:21.587] [D] [zway] SETDATA devices.11.instances.0.commandClasses.48.data.12.level = True
[2014-12-14 11:44:21.589] [D] [zway] SETDATA devices.11.instances.0.commandClasses.48.data.12 = Empty

after having one of these devices excluded and reincluded it works as expected. But I wished these sort of issues would not happen!!

hpd wrote:after having one of these devices excluded and reincluded it works as expected. But I wished these sort of issues would not happen!!

I think just re-interview should help.
"Unsupported sensor type" means sensor type mask is incorrect for some reason (need log to see why).