@mtomek Hi Michal,

if the period of read/write request won't be shorter than a few seconds I would use REXYGEN REST API - see docs: https://www.rexygen.com/doc/ENGLISH/MANUALS/RexRestApi/RexRestApi_ENG.html

Have a look at the "0302 IoT Integrations" examples folder - it contains some examples on using REST API.

Cheers,
Tomas

@mtomek Hello,
I'm really sorry—I somehow overlooked the fact that you were posting in this old thread. The "Warning 1 1" indicates that the buffer for serial communication between the Master and Slave devices is full:

#define WARNING_SERIAL 1 #define WARNING_SERIAL_BUFFER_FULL 1

Have you added any new data communication or changed the communication speed recently? I’d also like to point out that REXduino is a third-party project, and we don’t have direct control over it. I found the explanation for the warning directly in the source code here:
https://github.com/jaroslavs/REXduino/blob/master/REXduino_slave/REXduino_slave.ino

Cheers,
Jan

@mtomek Hi Michal,
you are welcome. I'm glad the problem has been fixed.

Cheers,
Jan

@mtomek Hi Michal,
I found the meaning of the errors directly in the REXduino_slave.ino code. The first number indicates the type of error and can have values:

49 - ERROR_COMMAND 50 - ERROR_PINMODE 51 - ERROR_SERIAL 52 - ERROR_ONEWIRE 53 - ERROR_I2C
The second number indicates error specification. For example for ERROR_ONEWIRE: 49 - ERROR_ONEWIRE_NOMOREDEVICES 50 - ERROR_ONEWIRE_BUSYBUS 51 - ERROR_ONEWIRE_BADCRC 52 - ERROR_ONEWIRE_DEPLETED 53 - ERROR_ONEWIRE_NOTEMPDEVICE
I agree that the errors could be mentioned more explicitly somewhere.

So in your case, the code 52 51 means bad crc error. So, for example, some noise may have appeared during data transmission.

I don't have any experience with the UniPi hub, because I'm using Monarco HAT. But as I understand to the UniPi 1-wire knowledge base, you should use the first hub port to connect the hub to your Raspberry Pi GPIO. Default GPIO pin for 1-Wire is GPIO 4. After connecting, you can read the data in REXYGEN using OwsDrv module. Please pay special attention to the note in the knowledge base:
b7515074-e8a3-460c-8a1d-58874c661791-image.png

Unfortunately, I have no idea if the UniPi hub provides ESD protection. You should check this directly from the manufacturer. If the hub doesn't have protection, I definitely wouldn't connect it directly to the Raspberry GPIO. The resistance of such a solution to the induction of unexpected voltages is negligible and it's possible that your Raspberry would get burned. In the absence of ESD protection, I would rather invest in Monarco HAT, where ESD protection is present and Monarco communicates 1-Wire over the I2C bus (documentation here), so 1-Wire is not connected directly to the processor.

Cheers,
Jan

@mtomek Hi Michal,
you are welcome. I'm glad everything is working as it should. Good luck with your project.

Regards,
Jan