Still looks good from here, at least as far as the EDS sensors are concerned.
One minor issue. EDS sensors seem fine and so do DS18B20s connected via
a Link45 or a DS9707U-S09 but a DS18B20 connected via an EDS OWSERVER
shows as status “Unknown” in PaperUI although the temperature seems to
being read correctly.
That‘s strange. I can‘t imagine how this could happen. I‘ll check.
I’m using the onewire-Bundle:
openhab> bundle:list | grep Wire
193 x Active x 80 x 0.11.0.201812271315 x Eclipse SmartHome OneWire Binding
I have 20 iButtons (DS2401) , 3 digitalIO (2Port, DS2406), 7 sole temperature sensors (DS1820) which run stable. Then I have 7 “AMS” sensors. The “humidity” channel of the AMS-Sensor is running fine, but the temperature channel is allways “NAN” in both configurations “Internal DS2438” and “External DS18B20”. The DS1820 Temp. SensorID is correctly recognized by PaperUI. In the logs i do not see anything.
Any hint?
Thanks in advance
Hmm, it isn’t quite as I described. It’s just that some devices take a
little time to establish communication. These are all online now,
although one of the EDS sensors periodically goes offline.
First of all: try latest master build.
Did you configure the sensors via discovery, manual via PaperUI or via text-files?
That‘s expected (at least in unstable situations). IIRC if refreshing fails, the next refresh is done after the configured refresh-time.
I’ll monitor it at a bit more length. I still haven’t got my central heating rules working properly. I was severely bitten in the backside by the QuantityType of new NumberItems and it took a lot of working around to get a number comparison to work.
Hello Jan,
I configured the sensors via PaperUI auto-discovery (Inbox). The Items are defined via .itmes files and linked to the channel.
I tryed the latest build, still the same result, no values for the temperature
Did you check if there is something in the logs? It works here for me.
If I set the binding to Debug with:
log:set DEBUG org.eclipse.smarthome.binding.onewire
and delete a AMS sensor an add it again through PaperUI I get
2019-01-02 20:56:00.106 [DEBUG] [internal.handler.OwBaseBridgeHandler] - onewire:ams:mybridge:26_A0CC6B010000 sucessfully updated properties, removing from property update list
2019-01-02 20:56:00.107 [DEBUG] [ernal.device.AbstractDigitalOwDevice] - configured onewire:ams:mybridge:26_A0CC6B010000 channel 0: path=[org.eclipse.smarthome.binding.onewire.internal.device.OwDeviceParameterMap@61a99813], mode=INPUT, logic=NORMAL
2019-01-02 20:56:00.108 [DEBUG] [ernal.device.AbstractDigitalOwDevice] - configured onewire:ams:mybridge:26_A0CC6B010000 channel 1: path=[org.eclipse.smarthome.binding.onewire.internal.device.OwDeviceParameterMap@4682ed5b], mode=INPUT, logic=NORMAL
2019-01-02 20:56:05.062 [DEBUG] [internal.owserver.OwserverConnection] - closed connection
2019-01-02 20:56:05.063 [DEBUG] [internal.owserver.OwserverConnection] - opened OwServerConnection to XXXXXXX:yyyyy
2019-01-02 20:56:12.664 [DEBUG] [ernal.device.AbstractDigitalOwDevice] - configured onewire:ams:mybridge:26_A0CC6B010000 channel 0: path=[org.eclipse.smarthome.binding.onewire.internal.device.OwDeviceParameterMap@68a9b24a], mode=INPUT, logic=NORMAL
2019-01-02 20:56:12.664 [DEBUG] [ernal.device.AbstractDigitalOwDevice] - configured onewire:ams:mybridge:26_A0CC6B010000 channel 1: path=[org.eclipse.smarthome.binding.onewire.internal.device.OwDeviceParameterMap@6dff4bb8], mode=INPUT, logic=NORMAL
2019-01-02 20:56:15.242 [DEBUG] [internal.handler.OwBaseBridgeHandler] - onewire:ams:mybridge:26_A0CC6B010000 handler missing
The thing itself has the Sttus “Online”, humidity channel is working. Any idea?
If humidity
is working properly, the temperature should be ok (it is read before). Could you please post your .items
?
The Humidity Item:
Number Hum_Keller_WK “Waschkueche Feuchte [%.1f ]” <humidity> (grpOneWireDevices2Check, gRRD4J, gB_WK, gHumInnen) { channel=“onewire:ams:mybridge:26_A0CC6B010000:humidity” }
And the Temperature Item:
Number:Temperature Temperature_Keller_Waschkueche “Waschkueche Temp [%.1f C]” <temperature> (grpOneWireDevices2Check, gTempInnen, gB_WK) { channel=“onewire:ams:mybridge:26_A0CC6B010000:temperature”}
Is that a copy&Paste Problem or are you missing the degree-symbol in front of the „C“? You could also try „%.1f %unit%“. And you should see the item changing its value in the event.log.
Thats it, it was a “unit” problem. Now the temperature gets displayed, thanks a lot!
@ntitley: I have started work on the BAE0910. Are you willing to help testing once I have a working version?
@ntitley, sorry for letting you wait so long. However, I have prepared this which adds support for the BAE0910 sensor. I would really appreciate if you could test and report back.
Jan
Thanks for the work. I'll take a little longer to get this
connected up now because the one I tested before is now
operational, but on a Pi that isn’t part of the openHab system. (I
have a python script that is talking to OWFS and sending the
results out to openHab via MQTT). I’ll get one onto a test board
and get it connected up but it’s going to take a week or two,
especially as my sister-in-law has just died and we have a week at
least of sorting out funerals, paperwork etc.
Sorry about that
Nigel