Hello, to get it working you'll have to create your symlink in the "/dev/serial/by-id" directory. This way it would be seen by Domoticz And i'm using this command as sudo : socat -d /dev/ttyUSB0,rawer SYSTEM:'tee /home/pi/ttylog/input.txt | socat - "PTY,link=/dev/serial/by-id/ttyUSB0_fake,rawer ...

You can try this; https://unix.stackexchange.com/question ... rt-traffic ..................................... socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams. In your use case you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0 ...

HI, I've tried my best to capture serial data comming from ttyUSB0 (RFLINK) with no success. I never thought it would be so hard to split a serial channel into two streams with regular linux commands demonized and laucnhed at startup in case of a power cycle. I had a problem in the database this ...

Yes, the report is showing normal values. I had to mess with the database because sometimes I loose connection with the meter (serial RF link) and the values become corrupted. I have the same problem with my rainsesor. When wrong data is received by Domoticz and after that the last data (the last ...

Hi, Version: 2024.7 (build 16453) Platform : RaspberryPi Hardware : RFLINK v1.1 R50 I've noticed something I can't explain in the "comparing usage" chart of my electricity multimeter device. The above example is on red days usage. The comparing usage chart value for december is different from the ...

Thanks for your answer ! It means incorrect data comes from the RFLINK. 2 reasons : - Radio interferences corrupt data and RFLINK think it really receives 0 value. - Homemade rainsesor sends 0 value beacuse of a bug in the program. But this is strange because the value then returns to normal. The ...

Version: 2024.7 (build 16450) Platform : RaspberryPi Hardware : RFLINK v1.1 R50 Hello, I'm having problems with incorrect rain data in the database, showing exagerated and false values on the dashboard. rain2.png rain1.png rain3.png Idon't know why those 0 or 0.1 values come to the database. Maybe ...

+2 for humidity offset