Hi Martin,
See embedded comments.
On 8/27/2020 2:56 AM, Martin Patzak wrote:
>
> what does *onOff.to_bytes(1,byteorder=sys.byteorder)) *evaluate to? Is
> that resulting in a byte-value? I am not familiar with this...
This seems to be the crux of the problem. After a lot of testing it
appears to be a python 3 issue converting an integer to a byte string. I
am convinced that passing a byte string to the write function is the
problem. Thanks for everyone's help but this is not an owfs problem.
>
> Things you could try:
>
> * In the path use the fully qualifying path and add */uncached *and
> write a byte-value like this
> *owproxy.write('/uncached/3A.0BE14D000000/PIO.BYTE',b'0')*
> * writeto the individual outputs PIO.A or PIO.B directly
> * try reading the sensed values***print('sensed.BYTE = ',
> owp.read('/uncached/****3A.0BE14D000000**/sensed.BYTE')*
>
> **
> On 26.08.20 21:05, Dennis Putnam wrote:
>> I have rewritten my code to use pyownet but am now nearly back where
>> I started. I have the following code:
>>
>> *owproxy.write('/3A.'+blower.id_+'/PIO.BYTE',onOff.to_bytes(1,byteorder=sys.byteorder))
>>
>> *That statement gives me the following error:
>>
>> *pyownet.protocol.OwnetError: [Errno 22] legacy - Invalid
>> transaction: '/3A.0BE14D000000/PIO.BYTE'
>>
>> *The error is meaningless to me. The path is not wrong so is it
>> complaining about writing a single byte?
>>
>> Thanks again.
>>
>> On 8/24/2020 4:33 PM, Dennis Putnam wrote:
>>> Thanks to everyone that replied. I was not aware of pyownet. I will
>>> look into that and rewrite my code to use it.
>>>
>>> On 8/24/2020 11:47 AM, Martin Patzak wrote:
>>>> For python I would highly recommend you use the library *pyownet
>>>> *by Stefano Miccoli
>>>> /https://github.com/miccoli/pyownet/
>>>>
>>>> /using Fuse can lead to weird problems... (not saying that it is
>>>> the reason in your specific case)
>>>>
>>>> or you can use the buil-in functions in owserverÂ
>>>> owread/owwrite/owdir instead.
>>>>
>>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
>> Virus-free. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>>
>>
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
