> On 05 Dec 2016, at 09:35, Martin Patzak (GMX) <martin.pat...@gmx.de> wrote:
>
>
>> The new node works fine too, but unfortunately I get an error, when a sensor
>> is right at 85 deg C:
>>
>>
>> Traceback (most recent call last):
>> File "read_a_temp.py", line 15, in <module>
>> sensed = op.read('/28.676A20060000/latesttemp')
>> File "/home/mnm/pyownet/src/pyownet/protocol.py", line 545, in read
>> raise OwnetError(-ret, self.errmess[-ret], path)
>> pyownet.protocol.OwnetError: [Errno 22] legacy - Invalid transaction:
>> '/28.676A20060000/latesttemp'
>
> hold on, my test was done in a rush, so I forgot to stop the task reading the
> temps from the temperature node.
> Could that have anything to do with error message?
As long as you have a single owserver process running, there can be any number
of concurrent clients, or even concurrent access via the same
pyownet.protocol.proxy object from different threads… I do not think this is
the problem.
BTW, pyownet.protocol.OwnetError simply reports the owserver error number (in
this case 22) along with the error description available from
/settings/return_codes/text.ALL (in this case "legacy - Invalid transaction”)
and the path that caused the error.
Me too, I’ve never experienced a 22 error: we need the help of a owfs wizard.
Stefano
>
> I cant test more today, because that was the last sensor over 85 deg C, so I
> have to wait until tomorrow morning...
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
