Domoticz

Posted: **Thursday 18 August 2016 20:04**

Is-it possible to add a way to identify the tag id who active/desactive the tagreader in domoticz.
When I look in the zwave log, I found this :

2016-08-18 19:56:22.593 Detail, Node006, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x06, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x01, 0x6c
2016-08-18 19:56:22.593 Detail,
2016-08-18 19:56:22.593 Info, Node006, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255
2016-08-18 19:56:22.593 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2016-08-18 19:56:22.593 Detail, Node006, Changes to this value are not verified
2016-08-18 19:56:22.593 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2016-08-18 19:56:22.593 Detail, Node006, Changes to this value are not verified
2016-08-18 19:56:22.593 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2016-08-18 19:56:22.593 Detail, Node006, Changes to this value are not verified
2016-08-18 19:56:22.593 Detail, Node006, Refreshed Value: old value=6, new value=6, type=byte
2016-08-18 19:56:22.593 Detail, Node006, Changes to this value are not verified
2016-08-18 19:56:22.593 Detail, Node006, Notification: ValueChanged
2016-08-18 19:56:22.593 Detail, Node006, Notification: ValueChanged
2016-08-18 19:56:22.594 Detail, Node006, Notification: ValueChanged
2016-08-18 19:56:22.594 Detail, Node006, Notification: ValueChanged

I guess it's possible to extract the tag id in the received data.

I have 3 tags, each of them have a differents code :

Exemple :
Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x06, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x01, 0x6c
Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x06, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x02, 0x6f
Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x06, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x04, 0x69

Posted: **Thursday 18 August 2016 20:24**

double post... for some reason

Posted: **Thursday 18 August 2016 20:27**

I also want to know....

Also want to know how to send a notification when a wrong one is entered... not figured that one out, yet

Is there some array in lua, that we can read in a device script, that holds these values?

which rfid code received
which rfid codes are known

so we can script it ourself?

http://domoticz.com/forum/viewtopic.php ... key#p92916
http://domoticz.com/forum/viewtopic.php ... key#p92404

Posted: **Thursday 18 August 2016 21:17**

I've been reading the log file in order to do this. The code is similar to this. I don't want the log file to get too big so the last line clears the log.

Code: Select all

 if grep -q "Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00" "/home/pi/domoticz/Config/OZW_Log.txt"; then

DO STUFF

truncate -s0 /home/pi/domoticz/Config/OZW_Log.txt
fi

Posted: **Friday 19 August 2016 9:39**

Yes do it into a bash is a possibility, but I rather like to see it with an option directly in domoticz if it's not to complicated to implement.

Posted: **Friday 19 August 2016 19:04**

Second that, I do not my log truncated.

Posted: **Friday 19 August 2016 19:42**

+1

And maybe add a name to each known tags

Posted: **Friday 26 August 2016 16:06**

Yeap, the goal of this is to identify each tag by a name

Posted: **Monday 14 November 2016 16:30**

Is it an options to add a colum: description or name to the use code page?
So we can add normal text to identify who is arm/disarm the alarm?

Posted: **Friday 18 November 2016 0:04**

It should per (card/tag/code) add like a motion sensor. which flips on and off when you use the card or tag or number and yes let the tags/sensors have a name. That would be nice.

Does anybody know how to factory reset the zipato tagreader?

Posted: **Friday 16 December 2016 14:09**

This would be a really nice feature, was thinking about this too when saw some video of Vera / Zipabox usage. Have to think about the log parsing thing which is doable even with my skills...

trixwood wrote: Does anybody know how to factory reset the zipato tagreader?

Probably you found this already but in Domoticz / OZW there is the option under device configuration to factory reset the unit.

Code: Select all

1. Set to Default:  0 (real: 0)

Set all configuration values to default values (factory settings) if set to 0xff.
Last Update: 2016-12-12 15:56:21

From the manual

Fibaro Mini Keypad Manual wrote:The Mini Keypad RFiD/Z-Wave supports a configuration reset function.
CONFIGURATION RESET MEANS
All configuration values are defaulted.
Wake up interval is defaulted.
This function can be activated by sending a configuration set frame:
CONFIGURATION_SET
PARAMETER: 0x01
SIZE: 0x01 (can’t be different from 1)
VALUE: 0xFF (can be any value except for 0x55)
When the value of configuration value is requested 2 possible values
can be returned CONFIGURATION_REPORT
PARAMETER: 0x01
VALUE 0X55: Configuration settings of the device are altered.
The device will report this even if the configuration parameters are
changed back to the default value.
VALUE 0XAA: Configuration of the device is untouched.
Note that this value will not change to 0x55 upon modifying the wake
up interval and that re-setting the value to 0xAA will always reset the
wake up interval

Posted: **Friday 16 December 2016 18:36**

How do i do that?

The aeontec zwave+ usb controller is reseted!
So the device will not show up!

The zipato support where really unfriendly. And no helpfull at all, rather the opposite.

I just do not think its possible and I have a brick. I looked everywhere for a solution...

Well another 60 bucks wasted...

But I am still hopefull.

Still it should be possible with a zipato box, they said :-/ I do not know anybody with such a device nor I am planning to buy one.
Their colored light bulbs sucked ass to... had to smack up really hard to get them included. Tap they said... bitch slapping it was, feels more like almost breaking the bulb before it lighted up to include.

WARNING: EXCLUDE TAGREADER BEFORE RESETTING YOU CONTROLLER, OR ELSE YOU CAN BRICK IT AND NEVER INCLUDE IT AGAIN!

(unless you have the newer models, which include in the manual a factory reset :-/

Posted: **Friday 16 December 2016 19:48**

It can't be included to another controller once included to one already? Shame, unless you have some backup from before resetting the controller it sure looks bad

Guess this and the lack of manual reset is because it could compromise the security somehow?

Good to know this anyhow to avoid bricking mine, thanks!

Posted: **Friday 16 December 2016 20:17**

Not being able to factory reset the device is security?
It's not that you can disarm the alarm when its reseted or the batteries are removed

And security of z-wave sucks balls anyway

I would not trust it with my life as "real" security

O well

Posted: **Friday 16 December 2016 20:26**

Sounds secure to me when one can't even factory reset it

But seriously, I guess nothing is unbreachable but I like at least the small added security of z-wave compared to some other wireless systems. I guess in the end it is always up to how well the possible intruders knows the target. All systems can be breached one way or the other.

Posted: **Friday 16 December 2016 21:08**

Well, you have not wasted 60 bucks on it

and it have nothing to do with the zwave network traffic security.

In the off change, that somebody resets the keypad, include it in their own z-wave network still does not show you the pincode or the cards previously stored...

And if you can access it you can also smash it to blittereens. Which is the same as you factory reset it yourself. So the whole not having a factory reset is from a security point of view nonsense.

Somebody did not think this through, and it cost me 60 bucks...

Thanks Zippato for knowing this and not saying a word anywhere...

Never ever going to buy something from them again.

Did I already mentioned their terrible terrible color lightbulb... which change color, but not smooth, after 2 or more seconds when you press the button. Not to mention wasting more then an hour figuring out you have to bitch slap them instead of tapping them gently. Thank god for hue

Zippato crap, pfff.... zippato support hope they hang themselves, never been treaded more rudely.

Posted: **Friday 16 December 2016 22:15**

trixwood wrote:Well, you have not wasted 60 bucks on it and it have nothing to do with the zwave network traffic security.

Yes, my first comment was supposed to be the funny part..

You got every right to be pissed at Zipato, I would be too. Have you btw seen this: http://forum.micasaverde.com/index.php?topic=38138.0 Someone has been able to reset it without the original controller to which it was paired (and without Zipabox).

Posted: **Saturday 17 December 2016 2:21**

AAaarrgghhh!!!

So it is possible!!!
also do not have a vera

maybe it's also possible with openzwave, i head over there to ask! thanks!

Posted: **Saturday 24 December 2016 10:54**

I really would like to see this, even if it's only a tag ID in the log file, I just want to see who's entered the house.

According this post it is implemented in OpenZwave. It only needs to be implemented in Domoticz:

viewtopic.php?f=28&t=14350&p=106110&hil ... v2#p106110

proncola wrote:Should not be a big deal for anyone familiar with compilation mechanisms (I'm not)
I 'm looking for such a solution for several week.
I made several trials with some of my keyfobs after enabling debug for my ZWAVE.ME UZB device.
The logs clearly shows that the Keyboard does send the information (an index corresponding to the keyfob just before the last byte)
However, it doesn't seem to be passed to domoticZ by the OpenZWave USB driver.
In the 'Received Alarm report' we could likely use sensorSrcID to contain the keyfob index.

Code: Select all

Using DomoticcZ
    Version: 3.4834
    Build Hash: 8398125
    Compile Date: 2016-03-02 08:43:51

    ZWAVE-ME device on Windows DomoticZ:    
        OpenZWave USB Version: 1.4.77.g40eb730.dirty

    KEYBOARD is:
        'Node 014 (0x0e)	Clavier	Schlage Link Mini Keypad RFID' and 5 Keyfobs:

LOGS:

Code: Select all

KEYFOB3: HOME 
2016-11-26 12:11:49.439 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x03, 0x66
2016-11-26 12:11:49.450 Info, Node014, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255

KEYFOB3: AWAY
2016-11-26 12:11:54.051 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0xff, 0x00, 0xff, 0x06, 0x05, 0x01, 0x03, 0x9a
2016-11-26 12:11:54.056 Info, Node014, Received Alarm report: type=0, level=255, sensorSrcID=0, type:Access Control event:5, status=255


KEYFOB2: HOME
2016-11-26 16:07:35.350 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x02, 0x67
2016-11-26 16:07:35.366 Info, Node014, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255

KEYFOB5: AWAY
2016-11-26 16:07:52.012 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0xff, 0x00, 0xff, 0x06, 0x05, 0x01, 0x05, 0x9c
2016-11-26 16:07:52.034 Info, Node014, Received Alarm report: type=0, level=255, sensorSrcID=0, type:Access Control event:5, status=255


KEYFOB1: HOME
2016-11-26 16:11:41.137 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x01, 0x64
2016-11-26 16:11:41.150 Info, Node014, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255

KEYFOB1: AWAY
2016-11-26 16:11:44.121 Detail, Node014,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0e, 0x0a, 0x71, 0x05, 0x00, 0xff, 0x00, 0xff, 0x06, 0x05, 0x01, 0x01, 0x98
2016-11-26 16:11:44.131 Info, Node014, Received Alarm report: type=0, level=255, sensorSrcID=0, type:Access Control event:5, status=255

This is mentioned in the manual: ALARM_REPORT_v2 (ZW Alarm Event 0x05, User ID)

Posted: **Tuesday 03 October 2017 21:21**

DanM wrote: ↑Thursday 18 August 2016 21:17 I've been reading the log file in order to do this. The code is similar to this. I don't want the log file to get too big so the last line clears the log.
Code: Select all
 if grep -q "Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00" "/home/pi/domoticz/Config/OZW_Log.txt"; then

DO STUFF

truncate -s0 /home/pi/domoticz/Config/OZW_Log.txt
fi

Hi,

How do you run this script? As a cron job / scheduled task

Thanks

/Claus

Domoticz

Indentify tag id with the Zipato/beNext TagReader

Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader

Re: Indentify tag id with the Zipato/beNext TagReader