Closed GoogleCodeExporter closed 8 years ago
From what I understand, the only thing that is not working for you is reading
the status at startup.
For this, you simply have to add the information that a KNX read request should
be sent at startup, i.e. { knx="<1/2/0+1/2/4" }.
Original comment by kai.openhab
on 28 Sep 2012 at 6:47
When i use the Syntax as you wrote it ( { knx="<1/2/0+1/2/4" } ), then i get
the following errors :
OpenHab:
00:32:59.024 WARN o.o.b.k.i.bus.KNXBinding[:461] - Cannot read value for item '
Light_EG_Living_Stehlampe' from KNX bus: timeout waiting for group read response
In the ETS4 Groupmonitor around the same time, i will see a read request on
1/2/0 and not as expected on 1/2/4
# Zeit Dienst Flags Prio Quelladresse Quelle Zieladresse Ziel Rout Typ DPT Info
24021 2012-09-29 00:32:48.989 vom Bus Low 1.1.250 - 1/2/0 Wohnzimmer -
Stehlampe [An/Aus] 6 Lesen
Original comment by tim.wey...@gmail.com
on 28 Sep 2012 at 10:39
That is the expected behavior, read requests are always done on the command GA.
Make sure that your have set the "r" flag in your ETS for this GA.
Original comment by kai.openhab
on 30 Sep 2012 at 6:24
Hi Kai,
I did some initial tests with KNX and openHAB yesterday and would have also
expected to be able to do something like { knx="1/2/0+<1/2/4" } to read from
the e.g. status object. Most KNX actuators have status objects which show the
real state of the channel (the Command GA could have been e.g. blocked).
Do you see any technical or design issues with "<" on listening GAs? I should
be able to provide a fix for this if it is just a matter of parsing the
configuration string.
Thank you.
Cyril
Original comment by cyril.ja...@gmail.com
on 30 Nov 2012 at 1:12
Hi Cyril,
You are right, it should also be possible to read at startup from status GAs.
Not sure if enhancing the parsing bit is enough or if it will require further
work. Feel free to try it yourself and provide a changeset in a clone later on.
Cheers,
Kai
Original comment by kai.openhab
on 30 Nov 2012 at 5:14
I added a fix in my repository. Please review and test it.
https://code.google.com/r/cyriljaquier-openhab-bugfixes/source/detail?r=b8f84cf4
34ac42fda4e6b8db7b781133e32834f4
Original comment by cyril.ja...@gmail.com
on 9 Dec 2012 at 8:47
Cheers, will do after releasing 1.1 - too risky otherwise!
Original comment by kai.openhab
on 9 Dec 2012 at 9:10
Original comment by kai.openhab
on 9 Dec 2012 at 9:10
Hi Cyril,
thank you very much for implementing this fix. I had exactly the same issue.
After checking it out from your repository I tried it a little bit and it
really works well. I will keep it running on my home server while extending my
home automation system.
br
Tony
Original comment by tonyatho...@gmail.com
on 2 Jan 2013 at 7:16
I have just pulled the changeset from Cyril into the current 1.2 branch. Thanks
for your contribution, Cyril!
Original comment by kai.openhab
on 5 Jan 2013 at 10:14
Issue 220 has been merged into this issue.
Original comment by kai.openhab
on 25 Mar 2013 at 6:36
Original issue reported on code.google.com by
tim.wey...@gmail.com
on 28 Sep 2012 at 8:54