as far as I can see, this is not in your list, is it?
ga=“9.001”:< followed by “Group Address”
Hint: after restart I get my temperature updates cyclic, so for some time (or temperature does not change) it stays NULL for some time. There is another config to push this update (force Reading from KNX), in some cases I have errors in my logfiles, because KNX cannot read these Group Address values, but a few minutes later, everything works fine.
Hint: I use Visual Studio Code with OpenHab Plugin, nice feature with this popup shown in my screenshot to check values very fast
You don’t say, so I have to ask… are you able to get any response from the KNX installation to your OpenHAB items or is it “only” the temperature items you can’t read ?
I recieved this morning a mail from our KNX installator which says “Address 5/2/11 is for writing value, try 5/3/11 for reading”. I tried, and I see now the value, wich is a big step .
Now, I would like to be able to update this value (which is the target temperature value).
I used :
Type number : tCons1Garage “t° Consigne 1/Garage” [ ga=“9.001:5/2/11<5/3/11” ]
But in interface, it is impossible to update the field.
Do you have an idea ?
(And I’m not able to find documentation about that)
Hi,
Good to have the correct GA’s. You should ask your installer for a complete list of GA’s if you don’t have ETS and have no plan to use/learn it.
I would loose the DPT and try :
Type number : tCons1Garage “t° Consigne 1/Garage” [ ga=“5/2/11+<5/3/11” ]
If it works adding the “+” then you could add the DPT again.
Type number : tCons1Garage “t° Consigne 1/Garage” [ ga=“9.001:5/2/11+<5/3/11” ]
Also, I see that your readInterval is 1. I would set that to a more reasonable number (3600 or even 0 (zero) just to actively read the KNX bus at startup).
first of all as @MartinKo said, if you have no ETS (the KNX programming software), your electrician should be able to export the GAs and you can build your openHAB configuration around that.
second of all, please use code fences ``` at the start and end of your code examples, makes it easier to read.
and finally: in openHAB3 you can easily drop the “standard” DPTs and use the configuration without them - only if you need to specify the DPT yourself (e.g. it comes in handy for alarms, heating GAs…), you should provide them. OH3 does the DPT-transformation for you and it works perfectly for me.
ok: the GUI doesn’t give you functions to update an item with specific values ootb. And also you have to keep in mind, what the difference of a “point” (=item) and a “channel” (sort of a equipment type) is. Please read the docs here:
The docs use Hue, but it’s similar to KNX.
you install the KNX binding and get a bridge, which gives openHAB access to your KNX bus
then you configure things (could be your sensor in the garage), which have channels, which could be temperature as one channel, humidity as another, …
you can then point the specific channel to your semantic model, which makes it possible for you to use the point (aka item) in a GUI or in a rule.
So, what you’re trying to do ist to update a channel, which isn’t possible. You have to link a item to the channel, which you can in turn update with values.
Question: Why do you want to update the temperature reading of your sensor?
Sorry, I missed out your question.
Installator said to me that :
5/3/11 is the address to read the target temperature value (not the current temperature)
5/2/11 is the address to write the target temperature.
ah I see! so that’s your HVAC controller! I misread it for some temperature sensor.
So, in that case you should not use one channel for both, because 5/3/11 is your “actual temperature” and 5/2/11 is your “target temperature”. You can of course use both in one item, but that’ll make it impossible for you to “read” the target temperature.
So, I suggest you configure two channels for each GA and then you can link the 5/3/11 to a simple “number-value” item and for 5/2/11 I’d suggest to use a “dimmer” item, which allows you to change the target temperature simply via the GUI in every case. Play around a bit with the item’s metadata options. for diverse default standalone widgets you can define the look and most importantly a min and a max value.
These two go into one number channel and into one dimmer item; as described above the channel can have multiple GAs, the first is writing, the second is reading.
My 2cents are, that the 5/2/96 GA is the “Writing” GA within your controller, but the “S” flag isn’t set, which means, the controller itself can write the target temperature, but not the bus. Try to change the target temperature on the controller and see, if the t9ChParentsCons and t9ChParentsConsD changes accordingly, so at least you’re sure, the 5/3/96 telegrams are configured correctly.