How to add scene other than motion sensor with light

[marvin-SL]

Hi,

I have some relays, and temperature sensors from sonoff (zbmini and snzb-02). They works well in phoscon, but I want to add 3 scenes and I can't figure how to do so : Scene 1- when humidity reach X, turn on relay1 (recognized as light switch). Scene 2- when humidity reach Y, turn off relay1 scene 3- on monday and friday, turn on relay2 for X hours.

All I can do is scene for motion sensor (turn on/off light with fade in/out).Or maybeI can't do that in phoscon?

Version 2.12.3-beta

Thanks

[SEK-DE]

Hi @marvin-SL,

it´s not possible at the moment in our app. I will mention that in our next programmer meeting, becouse it will be helpfull in the future. For now, you can implement the needed scene over a HA system like IO-Broker or Home Assistant.

I will let this post open until i get something new for you.

[marvin-SL]

Hello @SEK-DE, thank you for your reply, I'll keep an eye on phoscon for that. Thanks in advance

[phluorine]

@marvin-SL I'm trying to implement the same scenario. Both devices work in HomeKit via Homebridge and can be programmed to activate at a certain Rel Humidity threshold (you have to write it as a shortcut) but it'd be super to get this implemented at the Zigbee level. The other option is the non-home automation route-- There are purpose-built bathroom fan switches (eg from Leviton IPHS5-1LW) that do this. One advantage of the automation route is that the sensor can be placed high on the wall so that it detects when warm, humid air is still pooled near the ceiling even if eg you've opened a door and let some of the steam out.

Related but off-topic have you gotten the switch input to work? I haven't, but at least I've finally gotten my SNZB-01 to work correctly and I use it as an on/off toggle in Phoscon (seems like the new deCONZ beta 2.12.6 fixed Phoscon not letting me use it as a switch.) Oddly Homekit doesn't support it but that's not a big deal.

Anyway, whenever I add the ZBMINI to Phoscon, even using the sensor (let alone the switch or light) panel, it still shows up as a dumb "On/off light". I've been muddling through trying to understand how all this works behind the scenes and unfortunately it's not clear to me how to get deCONZ/Phoscon to recognize it as an "On/off light switch" rather than an "On/off light".

[SEK-DE]

Hey folks,

also a feature where our developers are already into it. We´ve planed some major developement and changes for the next months, also this feature is planed. Please be patient, i can´t promise that it will part of the next update, but it will come sooner or later.

[stale[bot]]

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[retrography]

@SEK-DE Great to hear! I find the current level of control we get already fabulous, way beyond what we used to have before. I am now actually considering moving some of my automations away from NodeRED to embed them inside the Phoscon app. It makes my life much easier. But such limitations prevent me to do so.

To add up to the above request: Please consider joint Light Level + Motion action on lights. That makes way more sense than the current time-of-the-day+motion actions. Today is an overcast day in Amsterdam, to the point that there is no daylight to brighten my bathroom. But my lights won't turn on automatically because Phoscon considers that it is day. That despite the fact that my motion sensor has a light meter and reports lux levels, and I also have a separate more accurate light meter in the bathroom.

I suppose joint sensor action is also important for humidity (I switch the fan on, but it only runs when humidity is high, or when someone is in the toilet. Or the fan turns on when humidity is high, but no one is in the bathroom to be bothered by the noise of the fan. Or if the humidity is higher than the level of humidity in the other rooms the fan turns on, but only if the window is closed, because if the window is already open, there is no need for fan. Etc...). Integrating such actions needs careful thinking of scenarios, as people have very different preferences, so that the UI doesn't become over-bloated while providing flexibility and control. For instance, I have noticed that checking for absolute indoor humidity levels regardless of the temperature and the outdoor humidity levels is completely useless for driving fans, and that makes all the humidity-control scenarios much more complicated. That said, you have already pulled it off with the joint switch / motion control, so I am sure you will find a way for the rest.

I hope you can bring up some of this scenarios / usecases with the devs, and I hope that helps them figure out some more advanced / flexible templates.

[stale[bot]]

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[stale[bot]]

As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.