I somehow think 2 would be nice, 3 would be best as it is available now but would mean getting into mqtt etc.
I would not recomment to run the Python script in a continous loop, this will block resources for openhab. And also not to restart it in intervalls when it was not ended beforehand with timeout.
Tried Nr. 1: I came to no solution. I know little about the internal mechanism of tinkerforge. (Callback and so on.)
Nr.2: Should it be instead for Openhab2 (not 1)?
3.Tried that! But the Tinkerforge MQTT is not yet ready for this Outdoor Weather Bricklet. :-o This solution would be nice, because my neighboor could also use my station. (I’m searching for an MQTT Server: simple, secure)
still using the worked out solution from above and still happy with it!
One issue is bothering me: every second my KNX Bus receives a new post containing a temperature value.
1. within the terminal, the command only runs once and then quit:
i tried several combinations of interval values and autorun modes.
Perhaps the rule from above is triggered every second from something else …?
My thoughts are: to use a shell script which saves the values once a minute (every 10 Minutes) to a file, and OpenHAB ist reading the file. Hmmm…
2. OpenHAB Binding
Theo is writing a binding and is looking forward to publish it in a few months.
3. Tinkerforge wrote, they will develop a new MQTT System … in the next few months …
The existing MQTT Proxy Script is not working together with the Outdoor Weather Device.
The new system will work together with every Tinkerforge Device (Brick and Bricklets)