Tamper notifications

[Cameleon 17]

Whats the best practice with handling tamper alarms/notifications? I can see devices have ability to do notifications on state changes, but this seems very crude  and not specific enough to just tamper alarms. Fibaro websites seem to suggest this is possible, to say get a notification when tamper has been detected but it doesn't seem obvious. 

Does it require a scene that is triggered by any tamper notification from a list of devices and write your own logic to push a message/send a text/email/etc? Seems a bit mad that you cant just click a tick box on the GUI to get tamper alarms and tell them what to. Am I missing something? 

[A.Socha 133]

every device with tamper got property tamper, you can use it in scene

 

if tamper == true then sendpush()

[chaicka 195]

Is it possible to use it like 'dead'?

 

Example of 'dead' as trigger:

%% properties
343 dead
347 dead
366 dead
368 dead
372 dead
396 dead

 

Possible to use 'tamper' as trigger?

%% properties

343 tamper

347 tamper

366 tamper

372 tamper

396 tamper

[Cameleon 17]

23 hours ago, A.Socha said:

every device with tamper got property tamper, you can use it in scene

 

if tamper == true then sendpush()

So the control of notifications should be done in a scene, I haven't missed some config on the device that would do it nicely for me? 

 

Also, which device on multi channel devices should be monitored? Say on my smoke sensor, I have 149 as the master, 150 is smoke, 151 is heat and 152 is temperature. Should I be monitoring for tamper on the master device, or smoke? 

 

I also assume that @chaicka is correct and we can use it like he describes?

[A.Socha 133]

tamper is 1 per device, so when you will active tamper it will get value true on all ednpoints ( 149 as the master, 150 is smoke, 151 is heat ) i prefer use id 150 (smoke)

 

Cytuj

So the control of notifications should be done in a scene, I haven't missed some config on the device that would do it nicely for me? 

Yes in LUA you can easy do that

20 godzin temu, chaicka napisał:

Is it possible to use it like 'dead'?

 

Example of 'dead' as trigger:

%% properties
343 dead
347 dead
366 dead
368 dead
372 dead
396 dead

 

Possible to use 'tamper' as trigger?

%% properties

343 tamper

347 tamper

366 tamper

372 tamper

396 tamper

yes

[Cameleon 17]

Great thanks. As a developer I find it easy to code LUA to do what I want, but feel drawn to find GUI options if they are available as they will be pre-tested and proven to work, unlike my own LUA code which usually takes some debugging!  

[chaicka 195]

25 minutes ago, Cameleon said:

Great thanks. As a developer I find it easy to code LUA to do what I want, but feel drawn to find GUI options if they are available as they will be pre-tested and proven to work, unlike my own LUA code which usually takes some debugging!  

 

That is largely because of poor documentation on the available LUA commands/codes and its syntax.

As a result of poor documentation, many times I have to use block to do a simple scene logic and switch to LUA to get the right commands and syntax before I use it in the actual LUA scene.

[A.Socha 133]

use left menu in lua, that will help you what you can use (property, actions with examples)

Please login or register to see this image.

[Cameleon 17]

20 hours ago, A.Socha said:

use left menu in lua, that will help you what you can use (property, actions with examples)

Where can we find docs of what these mean? For instance, "value" means different things dependant on the device. I'm sure this makes sense to people who have worked with the system for a long time, but for newbies this is seemingly very hard to find out. I'm slowly learning all the features, but I know there is a lot more power in the system than I can get hold of (as I see in other people's LUA scripts).

[A.Socha 133]

9 minut temu, Cameleon napisał:

Where can we find docs of what these mean? For instance, "value" means different things dependant on the device. I'm sure this makes sense to people who have worked with the system for a long time, but for newbies this is seemingly very hard to find out. I'm slowly learning all the features, but I know there is a lot more power in the system than I can get hold of (as I see in other people's LUA scripts).

on easy way use left menu in lua scene (chose room, device and you will see data like on screen, by pressing on it, it will generate lua code )

some option you will get in ip_hc/docs  but still i personally like use Hc_ip/api/devices/x (x = id devices) with add-on jsonview (who color json)

 

Cytuj

For instance, "value" means different things dependant on the device.

can you give examples? it always show global status of device (if it safe, turn on, open,) or for measure sensor value like level of temperature, lux, level of device  etc

 

in short

- switch,locks - on/off

- dimmer, shutter - 0-99 (0 = turn off/close 99- fully open/turn on)

- measure sensor (value of temperature or lux ) for them you use unit property to get info is that F or C or LUX

- W/kwh you will always find in property power  and energy

[Cameleon 17]

24 minutes ago, A.Socha said:

can you give examples? it always show global status of device (if it safe, turn on, open,) or for measure sensor value like level of temperature, lux, level of device  etc

 

in short

- switch,locks - on/off

- dimmer, shutter - 0-99 (0 = turn off/close 99- fully open/turn on)

- measure sensor (value of temperature or lux ) for them you use unit property to get info is that F or C or LUX

- W/kwh you will always find in property power  and energy

Thats exactly it. For different devices, "value" may mean on/off OR turn device up/down OR sensor value OR energy value. Being intelligent people, we can work out what this means for the current device (i.e. temperature sensor the "value" will be the temperature and you can not turn that up and down or turn it on/off), but for other properties this may not be so clear and it is not easy to discover. For example, I have just gone and used the menu you mention (very helpful to know about this  ), and see my light sensor has the property "logTemp", but I have no idea what this means or where to go to find what it means. So there are lots of useful information the devices give us, but I have no idea what it is. I know being a programmer that sometimes the obvious to one person is really not obvious to others, especially when you have worked on the system a long time and then trying to understand issues that newbies are having as knowing the system so well, you don't always see it the same way as someone who doesn't know it at all. 

 

Another current issue I have, and this will probably need another thread. I am using my hall downlights to be a nightlight. I have a scene that previously used Philips HUE lightstrip to do this, but the new downlights are dimmable and have a Fibaro dimmer attached so I use this instead. The scene worked perfectly with HUE - turning them on a nice dim glow, by setting the brightness and colour before calling turnOn where it would then light the room with the correct brightness and colour. With the Fibaro Dimmer, I tried calling:

Please login or register to see this code.

But I don't know if I actually need to call "turnOn" or not, or just the "setValue" will do enough to turn them on. It appears that you don't need the "turnOn" (as I did for HUE) but I don't know where this is actually documented in good detail. Currently the light seems to sometimes turn on at the knock back level (dimmed) and sometimes full brightness, even when the scene is reporting it is at the dimmed level. 

 

Does that make sense?

 

PS - set tamper scene up last night and I have a single scene for all devices I am interested in seeing tamper alerts for and it appears to be working 

Edited April 12, 2017 by Cameleon

[A.Socha 133]

3 godziny temu, Cameleon napisał:

Thats exactly it. For different devices, "value" may mean on/off OR turn device up/down OR sensor value OR energy value. Being intelligent people, we can work out what this means for the current device (i.e. temperature sensor the "value" will be the temperature and you can not turn that up and down or turn it on/off), but for other properties this may not be so clear and it is not easy to discover. For example, I have just gone and used the menu you mention (very helpful to know about this  ), and see my light sensor has the property "logTemp", but I have no idea what this means or where to go to find what it means. So there are lots of useful information the devices give us, but I have no idea what it is. I know being a programmer that sometimes the obvious to one person is really not obvious to others, especially when you have worked on the system a long time and then trying to understand issues that newbies are having as knowing the system so well, you don't always see it the same way as someone who doesn't know it at all. 

 

Another current issue I have, and this will probably need another thread. I am using my hall downlights to be a nightlight. I have a scene that previously used Philips HUE lightstrip to do this, but the new downlights are dimmable and have a Fibaro dimmer attached so I use this instead. The scene worked perfectly with HUE - turning them on a nice dim glow, by setting the brightness and colour before calling turnOn where it would then light the room with the correct brightness and colour. With the Fibaro Dimmer, I tried calling:

Please login or register to see this code.

But I don't know if I actually need to call "turnOn" or not, or just the "setValue" will do enough to turn them on. It appears that you don't need the "turnOn" (as I did for HUE) but I don't know where this is actually documented in good detail. Currently the light seems to sometimes turn on at the knock back level (dimmed) and sometimes full brightness, even when the scene is reporting it is at the dimmed level. 

 

Does that make sense?

 

PS - set tamper scene up last night and I have a single scene for all devices I am interested in seeing tamper alerts for and it appears to be working 

ok then some basic

Value = state of device will inform you about state of device

0 = it is OFF

>0 = it is ON

 

in every device on end of list you got action what it support

for wall plug

 

for door window

 

number on end telling how many argument it got for example
 

Please login or register to see this code.

So TurnON - will change state on last device state (for switch it will turnON, for dimmer/shutter it will turnON/open on last position - what was before turnOFF/close)

SetValue - you will set new state and device will turnON/open on that value for example 50 -> 50%

[Cameleon 17]

Great that's all good information, thank you. 

 

Are Fibaro planning to get more easily accessible documentation about this? The information is certainly on the forums and many knowledgeable people (both Fibaro and community members). It's a shame it's difficult to find. 

[A.Socha 133]

wiki is in preparation, but can't give a date, first we want finish something other

[Cameleon 17]

37 minutes ago, A.Socha said:

wiki is in preparation, but can't give a date, first we want finish something other

Great, look forward to seeing it