Ole8700 / openhab

Automatically exported from code.google.com/p/openhab
GNU General Public License v3.0
1 stars 0 forks source link

Pushbutton-Item not working in HABDroid #268

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create pushbutton-switch in sitemap with only one value:
Switch item=hallway label="Hallway Light" mappings=[ON="On"]

2. Create corresponding Item:
Switch hallway   "Hallway Light"     (Hallway) { 
http=">[ON:GET:http://localhost:8888/hallway/1]" }

3. Push button in HABDroid

The Widget should send an "ON" command to the item, the way it does in 
GreenT-UI, but it doesn't.

I'm running HABDroid 1.2.0.14 on Android 4.1 and OpenHAB 1.0.0 on Raspian with 
softFP.

Original issue reported on code.google.com by alexande...@commerce-plus.com on 2 May 2013 at 9:26

GoogleCodeExporter commented 9 years ago
I doubt that there is a problem with HABDroid - the demo sitemap contains

Switch item=DemoSwitch label="Button Switch" mappings=[ON="On"]

and this works as expected. If I press the button in HABDroid I get in the log:

22:22:22.279 INFO  runtime.busevents[:42] - DemoSwitch received command ON

I therefore assume that you must have some other problem. Feel free to reopen 
this issue or create a new one, if you have identified a problem.

Original comment by kai.openhab on 2 May 2013 at 8:24

GoogleCodeExporter commented 9 years ago
Could it be that the hallway switch is already in the ON state, and thus the 
button is disabled? It's the same behavior I get. If the status is already ON, 
HABDroid will not allow me to click (and thus no command posted) but the 
standard web interface will allow. You have to change the state of the switch 
to something else before it is "clickable" again.

Original comment by frederic...@gmail.com on 30 May 2013 at 11:41

GoogleCodeExporter commented 9 years ago
Actually yes, that's exactly what I meant in the first place. I worked around 
it with a rule to update the status to OFF immediately after turning it ON. 
It's a temporary switch anyway, so this is the expected behaviour.

Original comment by alexande...@commerce-plus.com on 31 May 2013 at 8:28