rbrouwer / dahua-vto-dz

Dahua VTO Dz is a plugin, which connects Domoticz to your Dahua VTO doorbell
ISC License
5 stars 0 forks source link

Doorlock issue #3

Closed rezzalex closed 11 months ago

rezzalex commented 11 months ago

Why is the Doorlock q DZ device type "Doorlock INVETERD" ?

Also, the status is always coming back to close / lock 1 or 2 seconds after locking or unlocking...

here si my VTO conf :

image

I don't have any door status feedback connected on the VTO

rbrouwer commented 11 months ago

Works as I intended it to work. Domoticz shows the "Door Lock" device as "Closed" by default, so you can click that to command the VTO to open the door. When you click it, it should unlock your door (if you have hooked up something to the VTO for that) and possibly even play a sound if you configured the VTO to do so when it is unlocking it. It also shows the LED in the VTO while it is unlocking the door. The VTO keeps the door opened for the unlock period. The VTO does not report any event for locking the door after it was opened using the VTO, so the plugin assumes it stops opening the lock after that configured 1 second unlock period.

Between each unlock command the plugin will enforce the "Unlock Responding Interval" and not command the VTO to open if less time was between 2 unlock commands.

rezzalex commented 11 months ago

Ok, got it. this is the 12v gate unlock usecase.

In my case, the VTO triggers a "dry contact" that is connected to my portal electronic board, which opens the portal, and leaves it open unless : It would be automatically closed after X seconds (if configured in the portal electronic board) ; or "manually" by triggering again the same VTO "unlock" button.

This is why in my case I would expect the VTO dz "unlock" device to reflect the real portal status.

What do you think?

rbrouwer commented 11 months ago

This plugin shows what the status is for the VTO device. It cannot easily know what magic connected behind that. In your case it is another board controlling the gate, which basically does expects a push button to toggle its state, while the VTO is probably more meant for controlling something like an electric door strike mechanism.

I believe it would be easy for you to hide the VTO Door lock device by prepending its name with a $ and simply making a virtual switch device in domoticz and a DzVents script, which triggers the VTO Door Lock device and shows whatever state you want.

You will likely run into the same thing I would if I would have to handle your use-case and that's having no way to see what the state of the gate actually is. It's might be possible to desynchronize that status with the real world.

rezzalex commented 11 months ago

Totally agree. I will probably hide the VTO Door lock device in DZ.

Thank you for the answer.