React on Milight actions

---

Hello community,
I have a Milight device triggered by a door contact. Works well so far. But I want the possibility to trigger the rule, dependent on the current state of the device.

Examples:
Light is switched off and someone opens the door --> Turn the light on for 5 minutes. (Current solution)
Light is already switched on by switch and someone opens the door --> Rule should not be triggered, because the light would be turned off again after 5 minutes.

For this case, I need a variable set while turning on the light by switch. Dependent on this variable, I could trigger my rule or not.
But unfortunately there is no state I could request on Milight devices.

My working config so far (relevant snippets):

{
  "id": "beleuchtung-bad",
  "name": "Bad",
  "class": "Milight",
  "addr": "192.168.0.55",
  "zone": 1
}

{
  "id": "contact-bad",
  "name": "Contact-Bad",
  "class": "HomeduinoRFContactSensor",
  "protocols": [{
	"name": "contact1",
	"options": {
	  "unit": 9,
	  "id": 21626178
	}
  }]
}

{
  "id": "turkontakt",
  "name": "Türkontakt Auf",
  "rule": "if contact-bad is opened then turn beleuchtung-bad on for 5 minutes ",
  "active": true,
  "logging": true
}

Do you have any hints?

@SaxnPaule said in React on Milight actions:

{
“id”: “contact-bad”,
“name”: “Contact-Bad”,
“class”: “HomeduinoRFContactSensor”,
“protocols”: [{
“name”: “contact1”,
“options”: {
“unit”: 9,
“id”: 21626178
}
}]
}

you could add a auto-reset-parameter by teh same time like

{
  "id": "contact-bad",
  "name": "Contact-Bad",
  "class": "HomeduinoRFContactSensor",
  "protocols": [{
	"name": "contact1",
	"options": {
	  "unit": 9,
	  "id": 21626178
	}
  }],
  "autoReset": true,
  "resetTime": 300000
}

so the contact sensor will be 5 minutes present before it goes absent… the rule should not be re-triggered…

second method was a xx-minutes-active rule by holding the presence active

if contact-bad is present and $movement_bath_xx_minutes = "no" then set $movement_bath_xx_minutes to "yes" and after xx minutes set $movement_bath_xx_minutes to "no"

and work with $movement_bath_xx_minutes in your rule

"rule": "if $movement_bath_xx_minutes = "yes" then turn beleuchtung-bad on for 5 minutes "

You understood me wrong. The contact sensor works well. See rule in first post.

But if I turn the light on by switch and open the door afterwards, the rule is triggered and turns the light off after 5 minutes.

I want to achieve, that the rule isn’t triggered, if I turned the light on by switch before.

@SaxnPaule

ooh okay… i misunderstood…

you could try if trigger: contact-bad is opened and beleuchtung-bad is off then turn beleuchtung-bad on for 5 minutes

And exactly this is the problem. There is no possibility to ask if beleuchtung-bad is on/off.
You aren’t able to receive the state of a Milight device.

I’m a step closer. You could create a rule with a variable Milight devices provide. The variables are:
$beleuchtung-bad.power
$beleuchtung-bad.color
$beleuchtung-bad.mode
$beleuchtung-bad.brightness

but I don’t know which values could be set.

Tests like:
if $beleuchtung-bad.power="on"
if $beleuchtung-bad.power=1
if $beleuchtung-bad.power

fail during saving with the message "Could not find an provider that decides next predicate of $beleuchtung-bad.power=‘on’ "

With pimatic 0.9 at least you can do the following in the when section. Currently don’t have a 0.8 system running anymore

Stehlampe Wohnzimmer is on and trigger: Bewegungsmelder Flur is present

Is your “Stehlampe Wohnzimmer” a Milight device? For my switched power sockets I can ask whether they are on or off, but not for my Milight devices.

Does not help a dummy switch with a rule?

{
“class”: “DummySwitch”,
“id”: “dummy-switch”,
“name”: “Dummy Switch”
},

if
Dummy Switch is turned on and Door is opened

then
turn Milight on for 5 minutes

Who/What will turn the Dummy switch on and off?

I was thinking that you want to switch manually separated milight rule.

Sorry, no, it is not. I suspected the milight plugin also extends it’s light devices from the switch class which doesn’t seem to be the case. Nevertheless maybe it would be an easy addition/fix in the milight plugin to use the baseclass provided with pimatic.

There seems to be a bug at least in 0.9 which doesn’t let you do comparisons for boolean attributes.
@pimatic-team who could have a look at it?

neither $blah = "true" nor $blub = 1 currently works to evaluate a boolean attribute. (for example the state)

What I found is a workaround with other comparison methods, not nice but seems to work in 0.9 but only for checking the true state:

$licht_kueche.state is increasing //triggers on change to true
$licht_kueche.state is decreasing //triggers on change to false
$licht_kueche.state > 0 //evaluetes true for true

Created an issue for the problem with evaluation:
https://github.com/pimatic/pimatic/issues/889

@thex said in React on Milight actions:

I suspected the milight plugin also extends it’s light devices from the switch class which doesn’t seem to be the case.

I am assuming you’re referring to pimatic-led-light plugin, right? As you have suspected this plugin
does not derive from the standard switch as it should. Instead of “state” the attribute is “power”. The following works for milight:

if power of MyDevice is on (then) turn myDevice2 on

if contact-bad is opened and power of beleuchtung-bad is off then turn beleuchtung-bad on for 5 minutes

does the trick. Thank you very much.

neither $blah = "true" nor $blub = 1 currently works to evaluate a boolean attribute.

For normal, a if $blah should be enough for a boolean check

guess this issue is “solved” now ?

@SaxnPaule said in React on Milight actions:

For normal, a if $blah should be enough for a boolean check

Note, for variables only string and number types are supported as far as I know. $blub = 1 should match if $blub has been assigned a number. If $blahis a string the is equal to operator should match.