Shubhamjain007 / openhab

Automatically exported from code.google.com/p/openhab
0 stars 0 forks source link

DTP 5.001 not shown in visu #135

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
openhab Version 1.1.0 Snapshot # Build 291 
(https://openhab.ci.cloudbees.com/job/openHAB/)

Item:

Number Rolladen_DG_Schlafen_Pos         "Schlafen Höhe [%d %%]" (gDG, 
Rolllaeden)       {knx="<5.001:3/3/16"}

Log:
Rolladen_DG_Schlafen_Pos received command 90

Visu:

- %

When i use 5.004 i get
Error while receiving event from KNX bus: java.lang.IllegalArgumentException: 
Value must be between 0 and 100

Original issue reported on code.google.com by kleina.i...@gmail.com on 4 Oct 2012 at 6:13

GoogleCodeExporter commented 8 years ago
The visu works for me. Please note that the visu is not related to any binding.
To try it out, define

Number Rolladen_DG_Schlafen_Pos         "Schlafen Höhe [%d %%]" (gDG, 
Rolllaeden)

and type "openhab send Rolladen_DG_Schlafen_Pos 90" in the OSGi console. You 
will see the correct value "90 %" appearing in the visu.

Can you check that the item state is indeed set by the binding? Do a "openhab 
status Rolladen_DG_Schlafen_Pos" on the OSGi console.

Original comment by kai.openhab on 5 Oct 2012 at 3:12

GoogleCodeExporter commented 8 years ago
i checked it.

when GA gets an update from the bus the log shows correctly the value

Rolladen_DG_Schlafen_Pos received command 90

but "openhab status Rolladen_DG_Schlafen_Pos" show "Uninitialized"

after "openhab send Rolladen_DG_Schlafen_Pos 90" the log show also: 
Rolladen_DG_Schlafen_Pos received command 90
and the status command shows the correct value 90 and the the visu also is fine.

So when the update for the status comes from the knx or the local send command 
the logs shows the same, but only the local send command will update the status 
corretly.
How do i get the KNX Binding will update the status corretly?

Original comment by kleina.i...@gmail.com on 10 Oct 2012 at 6:28

GoogleCodeExporter commented 8 years ago
This problem should hopefully be fixed by 
http://code.google.com/p/openhab/source/detail?r=d35cb0ea913dcb833e2015e40e13907
e21cf9e2a.

Original comment by kai.openhab on 17 Nov 2012 at 10:01