Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Motion channel ON/OFF #24

Closed
andreacioni opened this issue Aug 5, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@andreacioni
Copy link

commented Aug 5, 2016

Hi Tim,

I'm wondering to change the tripped channel from OPEN/CLOSE to ON/OFF because presence in OH2 was linked to the ON/OFF state. What do you think?

@tobof

This comment has been minimized.

Copy link
Owner

commented Aug 10, 2016

Hey Andrea,

according to this: https://github.com/openhab/openhab/wiki/Explanation-of-items

Contact: "Can be used for sensors that return an "open" or "close" as a state. This is useful for doors, windows, etc."

For me presence and tripped are not the same. A door window maybe OPEN but nobody is at home (presence = OFF). :o)

@andreacioni

This comment has been minimized.

Copy link
Author

commented Aug 10, 2016

Ok, not a good idea ;)

@DerTomm

This comment has been minimized.

Copy link

commented Dec 28, 2016

Hi Tobof,

sorry for reviving this issue but today I set up the MySensors OpenHAB binding for the first time and was a little bit confused about using "contact" as item type for motion. Intuitively I would have expected that motion is represented with the status "true/false" (or "on/off") and not with "open/close".

At the moment a non-tripped motion sensor reports "closed" as status. Don't you think that the item type "switch" would be better for motion?

@tobof

This comment has been minimized.

Copy link
Owner

commented Jan 2, 2017

Hey @DerTomm!

I've thought about this for the last days and I have no preference.
@andreacioni do you still vote for ON/OFF instead of OPEN/CLOSE?
If so, I will prepare a fix.

@tobof tobof reopened this Jan 2, 2017

@andreacioni

This comment has been minimized.

Copy link
Author

commented Jan 2, 2017

Hi @tobof and @DerTomm. This old question is hard to answer... Tripped channel is used for both motion and contact sensors. So changing that to ON/OFF may create confusion for who now use door/window things through MySensors Binding.

Probably the simplest thing is to do nothing. But @tobof, what about distinguish tripped channel to: tripped-onoff and tripped-openclose?

@DerTomm

This comment has been minimized.

Copy link

commented Jan 2, 2017

Another argument: In addition to S_DOOR also S_MOTION and S_SMOKE use V_TRIPPED as value. And neither a smoke sensor nor a motion sensor will report something to be open or closed. So I think "on/off" as generic item type would fit best for all of them.

@tobof

This comment has been minimized.

Copy link
Owner

commented Jan 5, 2017

Hmm, it seems, that there is no clear regulation for that.
In the Zwave binding there is ON/OFF for Motion and OPEN/CLOSED for Door.

If I look at this page: http://docs.openhab.org/configuration/items.html
There is the following example:
Group:Contact:OR(OPEN,CLOSED) gMotionSensors (All)

@DerTomm Maybe it makes sense to open a discussion in the community? All bindings should use it the same way.

@DerTomm

This comment has been minimized.

Copy link

commented Jan 5, 2017

I think the Zwave binding distinguishes between ON/OFF for motion and OPEN/CLOSE for door contact sensors because otherwise the motion sensor widget on any sitemap only shows an open or closed window too - which is quite unsuitable here in my opinion.
So I think @andreacioni's approach with two channels "tripped-onoff" and " tripped-openclose" would solve this problem in a nice way.

@Alpoy

This comment has been minimized.

Copy link

commented Apr 11, 2017

So I think @andreacioni's approach with two channels "tripped-onoff" and " tripped-openclose" would solve this problem in a nice way.

Would be nice if this could be implemented! ;-)

@tobof tobof closed this Jul 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.