Stop vs. stopped argument to setState


#1

Does the current firmware respond to “stop” as an argument to the setState function? Unless I misread the firmware code, I don’t see support for “stop”. If I send “stopped”, is that what is expected? The README.md says that “stop” is an accepted command. Please see this thread on the openHAB forum. Thanks!

John


#2

stopped is a valid argument to the setState. It results in one button click if door is opening, two clicks if door is closing and no effect in all other states.


#3

Thanks! I am correcting the openHAB binding now.