@Martin-Kudláček it works, but you have to attach using the "Use deploy parameters" as described a few posts above

@mikami Evok supports only Modbus RTU as communication protocol on the RS485. First you have to define the variables(registers) using the example https://github.com/UniPiTechnology/evok/blob/master/etc/hw_definitions/CUSTOM MODBUS DEVICE.yaml (also check the other definitions - you can access ti via registers or using the DO/RO/... objects of evok).

Once that is done, you have to modify to add it to evok.conf restart it and then you will be able to access the device either using the registers (https://evok-4.api-docs.io/1.04/json/get-register-state-json) or using the DO/RO/.. objects if you define.

It will be available e.g. http://127.0.0.1/UART_[UART_ADDRESS]_[DEVICE_ID]/json/register/{circuit}
UART_ADDRESS and DEVICE_ID are the same as defined in evok.conf
circuit is the register defined in your .yaml definition

@mikami https://evok-4.api-docs.io/1.04/aggjmsqrwmypnmorz/extensions

@TriathletC Yes, it's possible.

@CKB Send me a link to download the project to a PM

@Yakub It depends what is the physical and application prototol to communicate with the sensors... We have not tried it so we do not know

@mikeardy Yes, that is the purpose of /tmp aka Temporary folder. You can also try /home/pi/...

@CKB Can you share your project?

@CKB If both UniPis are running Mervis, have them both in one project and use the SSCP protocol which is native protocol of Mervis. An example of this can be found at download section of Mervis.

@mikeardy what about /tmp/