Vision ZG8101 and Vera Edge

Other Devices & Integrations Door Locks & Sensors
1

Hi!
Just bought a Vera Edge and a garage door detector.
Is there anyone here that knows how to include and use the sensor (it’s not available in the list or devices when adding a new device).
When I include it, it appears as a motion sensor, but all I can see (UI7) when I tilt the detector is that it changed it’s state, not in which state it ends up in (open or closed). It also looks like the vera does not pickup all changes even though the vera and the sensor are on my desk…

Any help greatly appreciated.

/Magnus

2

Try to include it as a generic z-wave device.

The sensor state in Ui7 is represented by the 2 ‘waves’ above the sensor icon. If they are grey it’s untripped and if they are red the sensor is tripped. Granted, the Ui5 way of a ‘green standing man ball’ and a ‘red walking man ball’ icon was a lot more intuitive. The only state shown by the switch is if it is bypassed or armed.

The sensor should work in Ui7 as I have it’s ‘brother’ the Ecolink tilt sensor running under Ui5.

3

Thanks!

4

The vision ZG8101 tilt sensor works ok in my VeraLite in UI7 ( I do not have a VeraEdge yet)

The wakeup internal is set to 1800 s ( 30 mn) after the inclusion of the device but this seems to be a very short duration for a battery device ?

5

It is working as I first had expected now ;D

I just added the device (it was registered as a motion sensor by default) and then I changed:
device_type to: “urn:schemas-micasaverde-com:device:DoorSensor:1”,
device_file to: D_DoorSensor1.xml and
device_json to: D_DoorSensor1.json

Now it looks and acts like a door sensor.

6

Another problem…

I suspect that the sensor is faulty.
When I tilt the sensor it correctly reports that it is tripped. However when I position the sensor vertically it correctly reports that it is untripped, but in less than a second it again reports it is tripped! What is going on?

Any thoughts?

7

Hi All,

I have a vera Lite UI7
and I have the same problem with ZG8101 describe in the previous message

magnusastrom have you resolved the problem?

Best regards

8

Exact same problem here on upgraded Veralite UI6 to UI7 last night.

Vision tilt sensors stay tripped (and are reported as motion sensors). Doesn’t matter if they are set to door sensors. Been working fine for a number of years, so there’s definitely a bug in UI7.

9

I think I have the same problem with Vera Edge and ZG8101. If my garage door opens and the ZG8101 tilts, then the status will change to tripped. If the door closes and the ZG8101 comes back in vertical position, then the status will change to untripped but after about 5 seconds it will become tripped again.

It used to work properly until some months ago. My Vera Edge was updated in the past months, however, I am not sure if an update caused this problem.

Did anyone find a solution?

Best regards,

Wim

10

I have the same problem, with a new Vera Edge and a new ZG8101.

I have changed this, to make it act like a doorsensor.

device_type to: “urn:schemas-micasaverde-com:device:DoorSensor:1”,
device_file to: D_DoorSensor1.xml and
device_json to: D_DoorSensor1.json

When the sensor comes in horisontal position the status changes to tripped and when back in vertical position status changes to untripped for 5 to 8 sek, then back to tripped status.

Best regards

11

I started a duplicate thread but I’ll join in here from now on.

MCV advised me that this is a known bug that would be fixed in a future firmware. Downgrading back to 1.7.541 (7.0.5) will restore functionality.

12

7.0.11 (1.7.690) doesn’t fix this, though there are more messages in the log now so they’ve clearly had a go at it. Symptoms are: going from tripped to untripped is detected unreliably, so sometimes the sensor remains tripped even after the sensor has tilted back to the vertical position.

13

Arhh… I just upgraded to UI7 and I have the same problem you guys have. Really annoying. Will have to look at making a work around scene for the remote control and hoping it will be fixed sometime soon…

14

Hi,

Can you try if this is working? It works for the vision door sensor that was showing similar behaviour.

[url=http://forum.micasaverde.com/index.php/topic,32819.msg248022.html#msg248022]http://forum.micasaverde.com/index.php/topic,32819.msg248022.html#msg248022[/url]

If setting AutoUntrip and IgnoreTripTime works for you I know I can make the move from UI6 to UI7. ;D

Cheers Rene

15

The ZG8101 problem is still not fixed in my VeraLite with the Beta 7.0.12 >:(

16

[quote=“reneboer, post:14, topic:186993”]If setting AutoUntrip and IgnoreTripTime works for you I know I can make the move from UI6 to UI7. ;D

Cheers Rene[/quote]

Hi Rene,

I tried these settings, but alas it makes no difference. I have the Vision sensor, and was unable to make it stay “untripped” - I can see see in the logs, it does go to untripped, but almost immediately trips again so definitely bug.

17

Did you manage to create a scene to solve this? I’m a novice, and I’m sure it can probably be done in code, but having a poke about in the scene editor, the only likely candidate I could find was “ToggleState” which serves only to switch between “armed” and “Bypassed” The service for this seems to be

Service: urn:micasaverde-com:serviceId:HaDevice1

I wondered if this is also incorrect - should it not be serviceId:DoorSensor1 ?

My thought would be to create a scene which effectively saw the untripped state occur, waited x seconds and changed the status of the device to untripped. I’d need to think about a virtual switch or something so that the scene only runs once - or keeps running until the status is changed…

18

Updated to 1.7.719 today, and my Vision Tilt sensors are working again!!!

Who said MCV never fix bugs… that they’ve introduced… in a timely manner… :wink:

19

[quote=“magnusastrom, post:5, topic:186993”]It is working as I first had expected now ;D

I just added the device (it was registered as a motion sensor by default) and then I changed:
device_type to: “urn:schemas-micasaverde-com:device:DoorSensor:1”,
device_file to: D_DoorSensor1.xml and
device_json to: D_DoorSensor1.json

Now it looks and acts like a door sensor.[/quote]

I made these changes and now the icon of the device is ok (ie. a door sensor) but in the dashboard is still shown as motion sensor ( it appears in the dashboard in the motion sensor group).