reading from path 26.91BC40010000/humidity attempt 1 throws exception

[Bernd Pfrommer]

After upgrading to the new onewire binding I'm getting these error messages in the log:

2015-06-22 10:34:04 ERROR o.o.b.o.i.c.OneWireConnection[:222]- reading from path 26.0FA840010000/temperature attempt 1 throws exception

org.owfs.jowfsclient.OwfsException: Error -1

        at org.owfs.jowfsclient.internal.OwfsConnectionImpl.readPacket(OwfsConnectionImpl.java:264)

        at org.owfs.jowfsclient.internal.OwfsConnectionImpl.exists(OwfsConnectionImpl.java:159)

        at org.openhab.binding.onewire.internal.connection.OneWireConnection.checkIfDeviceExists(OneWireConnection.java:187)

        at org.openhab.binding.onewire.internal.connection.OneWireConnection.readFromOneWire(OneWireConnection.java:203)

        at org.openhab.binding.onewire.internal.OneWireBinding.updateItemFromOneWire(OneWireBinding.java:259)

        at org.openhab.binding.onewire.internal.OneWireBinding.devicePropertyWantsUpdate(OneWireBinding.java:216)

2015-06-22 10:34:04 INFO  o.o.b.o.i.c.OneWireConnection[:119]- Trying to reconnect to owserver...

2015-06-22 10:34:04 INFO  o.o.b.o.i.c.OneWireConnection[:99]- Connected to owserver [IP 'localhost' Port '4304']

2015-06-22 11:54:04 ERROR o.o.b.o.i.c.OneWireConnection[:222]- reading from path 26.0FA840010000/temperature attempt 1 throws exception

org.owfs.jowfsclient.OwfsException: Error -1

        at org.owfs.jowfsclient.internal.OwfsConnectionImpl.readPacket(OwfsConnectionImpl.java:264)

        at org.owfs.jowfsclient.internal.OwfsConnectionImpl.read(OwfsConnectionImpl.java:133)

        at org.openhab.binding.onewire.internal.connection.OneWireConnection.readFromOneWire(OneWireConnection.java:204)

        at org.openhab.binding.onewire.internal.OneWireBinding.updateItemFromOneWire(OneWireBinding.java:259)

        at org.openhab.binding.onewire.internal.OneWireBinding.devicePropertyWantsUpdate(OneWireBinding.java:216)

        at org.openhab.binding.onewire.internal.scheduler.OneWireUpdateTask.run(OneWireUpdateTask.java:59)

2015-06-22 11:54:04 INFO  o.o.b.o.i.c.OneWireConnection[:119]- Trying to reconnect to owserver...

2015-06-22 11:54:04 INFO  o.o.b.o.i.c.OneWireConnection[:99]- Connected to owserver [IP 'localhost' Port '4304']

Despite error messages I'm getting valid numbers, until the disconnects happen, at which point I'm getting default values (which give me false alarm emails, hence this post).

It used to work fine with the old binding, and I haven't changed anything on the one-wire server, just upgraded the binding and the config.

Here is the relevant entry in the .config file:

Number HumidityEastAttic "East attic humidity [%.1f%%]" (gHumidity,gEastAttic) {onewire="deviceId=26.4A9C40010000;propertyName=humidity;tukeyfilter"}

############################## OneWire Binding ########################################

#

# OwServer IP address

onewire:ip=localhost

onewire:tempscale=FAHRENHEIT

Ah yes, and I fixed the tempscale bug to make FAHRENHEIT work, but that should not have anything to do with the disconnects.

Anybody else having the same issue?

[Dennis650]

Hi.

the new version of the binding logs more than in some cases. Do you habe configured readAttemp=1? By default there should be 3 read attemps.
I haven't seen this exceptions on my production system with many different onewire devices.

1. Log-entry: owserver can't find your device
2. Log-etrny: owserver can't read form the device, at this pint the exists-query was already successfull.

It seems like your onewire-bus is not stable and the new binding logs these exceptions.

I can make a config-property that will hide these exceptions on read-attemps, but the binding can't fix the problem.

Greetings
Dennis

[Bernd Pfrommer]

I know that the bus is a little funky, but that was the case before I upgraded the binding, and it worked. I have sunk a lot of time into setting up the physical wiring and that's the best I could make it work.

The issue I'm having is that ever since upgrading the binding I'm getting emails that my flood sensing switches are closed. I'm not even sure they have to do with the exceptions in the log.

I did not configure anything special like readAttemp=1. Where do you even configure readAttempt. Is that an items config? I haven't seen any documented config option for that.

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/gEfCWghtZvc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/f6d1d529-5a1a-45a2-9dac-dba3ce2d9b83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dennis650]

Hi,

sorry, i mean onewire:retry config property. The binding should try to read 3 times by default. If the binding couldn't succefully read the value for the item, the value is set to Undefined. I think this is new in the new Version.

Check your rules what will happen of the value changes to undefined.

Greetings
Dennis

[Bernd Pfrommer]

The
onewire:retry=

property is unset:

#onewire:retry=


I will set it to 10 and see if that makes a difference.

Will also check my rules. I think I send an alarm if undefined because
it indicates malfunction.

Thanks!

Bernd