[Feature]: use unipi1.1 with debian trixie and raspberry 5

[rudyvan]

Describe the feature

I wanted to test a raspberry 5 with latest debian trixie and evok and following my tests, only one file needs to change for reboot to work after installation:

/usr/lib/systemd/system/evok.service has to become the following:

[Unit]
Description=EVOK Rest/WebSocket/RPC Server
After=unipitcp.service
After=unipi-one.service
StartLimitIntervalSec=300

[Service]
Type=simple
ExecStart=/opt/evok/bin/evok
TimeoutStopSec=6
SyslogIdentifier=evok
WorkingDirectory=/var/lib/evok
User=evok
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

change TimeoutStopSec 3->6
add RestartSec=10

When doing so, evok starts properly after reboot, i just tested a few times but probably more is needed.

I know raspberry 5 is currently not supported with unipi 1.1, but for me it seems to work fine, maybe a few other users can try and exchange the experience.
Happy to receive ideas or suggestions.

Use case

Raspberry 5.0 is significantly faster than 4.0 and some applications will benefit from the higher speed.

Alternatives Considered

No response

Additional context

No response

[rudyvan]

I have been doing more tests and to make the start of the service at reboot reliable, the timeout and retry has to be increased:

in the file modbus_unipi.py (/opt/evok/lib/python3.13/site-packages/evok/modbus_unipi.py) make the following 3 changes
line 33: add timeout 3 seconds
line 64: same
line 56: retries=0 -> 1

see extract of the result below:

class EvokModbusSerialClient(AsyncModbusSerialClient):
    def __init__(self, port: str, framer: Type[ModbusFramer] = ModbusRtuFramer, baudrate: int = 19200,
                 bytesize: int = 8, parity: str = "N", stopbits: int = 1, timeout: float = 1, **kwargs: Any) -> None:
        super().__init__(port, framer, baudrate, bytesize, parity, stopbits, retries=0, **kwargs)
        for method_name in ['read_holding_registers', 'read_input_registers', 'write_register', 'write_registers',
                            'write_coil', 'connect']:
            setattr(self, method_name, self.__block(getattr(self, method_name)))
        self.port = port
        self.lock = asyncio.Lock()
        self.stime = time.time()
        self.block_count = 0
        self.__timeout = timeout + 3

    def __runtime(self):
        return int((time.time()-self.stime)*1000)

    def __block(self, operation: Callable):
        async def ret(*args, **kwargs):
            async with self.lock:
                try:
                    aret = await operation(*args, **kwargs)
                    if type(aret) in exception_classes:
                        raise ModbusException(f"{type(aret)}: {aret}")
                    return aret
                except ConnectionException:
                    await asyncio.sleep(self.reconnect_delay_current)
                    while not self.connected:
                        await asyncio.sleep(0.001)  # TODO
        return ret


class EvokModbusTcpClient(AsyncModbusTcpClient):
    def __init__(self, host: str, port: int = 502, framer: Type[ModbusFramer] = ModbusSocketFramer,
                 source_address: Tuple[str, int] = None, timeout: float = 1, **kwargs: Any) -> None:
        super().__init__(host, port, framer, source_address, retries=1, **kwargs)
        for method_name in ['read_holding_registers', 'read_input_registers', 'write_register', 'write_registers',
                            'write_coil']:
            setattr(self, method_name, self.__block(getattr(self, method_name)))
        self.host = host
        self.lock = asyncio.Lock()
        self.stime = time.time()
        self.block_count = 0
        self.__timeout = timeout + 3

    def __block(self, operation: Callable):
        async def ret(*args, **kwargs):
            start_stamp = time.time()
            while not self.connected and time.time() - start_stamp < self.__timeout:
                await asyncio.sleep(0.001)
            aret = await operation(*args, **kwargs)
            if type(aret) in exception_classes:
                raise ModbusException(f"{type(aret)}: {aret}")
            return aret
        return ret

After making these changes, the service starts each time after reboot, check with sudo systemctl status evok.service.

Conclusion: it is possible to use a raspberry 5.0 with unipi reliably by making just a few changes in this and previous post.
Will unipi make the updates and officialise them?
Thanks!