Bullseye and evok running?
-
I want to install evok on raspi with bullseye.
Does EVOK run on bullseye?
If so, can I use the EVOK version on github? -
I'm also curious on this one.
Because when I tried to install evok on fresh bullseye RPI OS according to this how-to (https://github.com/UniPiTechnology/evok#legacy-installation-process-using-a-shell-script-required-for-unipi-11), I could not use the evok GUI.
So to me it seems there might be a compatibility issue.
There is also an open github issue on this: https://github.com/UniPiTechnology/evok/issues/94
-
I went back to buster. Now evok works ok!
Bullseye definitely needs some work. -
@juntiedt There is now new Evok version on github: 2.4.20
It could work now with bullseye, however, when I tried to run the installation script on fresh RPI Bullseye 32 bit image, it seems to work mostly but I'm missing some digital inputs, relays and analog output.
Probably still needs some rework. But I'm optimistic that unipi team will fix it shortly.
-
I have just re-run the Evok installation script.
Now all inputs etc. work.Maybe I chose wrong device before.
So Evok now also runs on Debian 11 / Bullseye. :)
-
Hi everyone,
We have been working hard on EVOK and other packages for bullseye OS for the past few months and it is already working on most Unipi Neuron and Unipi 1 HW. We are planning to release another version within this week where all Unipi Neuron and Unipi 1 HW will be fully supported.
Adding Unipi packages to Raspberry Pi OS is possible with the following command:
wget -qO - https://repo.unipi.technology/debian/raspberry-install.sh | bash
For the subsequent installation of EVOK, follow the instructions on our GitHub for Unipi Neuron and Unipi 1.
Best regards,
Antonin -
Is Evok 2.4.24 fully compatible with Bullseye?
I have one RPI with headless Bullseye and on that one everything seems to work.
I have another RPI with Bullseye and Lightdm on top and on that one relay state change with JSON POST does not work.
Example:
POST http://localhost:8080/json/relay/1
Content-Type: application/json{
"value": "1"
}Result:
HTTP/1.1 200 OK
Content-Length: 44
Access-Control-Allow-Methods: POST, GET, OPTIONS
Server: TornadoServer/4.5.3
Date: Wed, 15 Feb 2023 09:48:09 GMT
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: x-requested-with
Content-Type: application/json; charset=UTF-8{
"status": "success",
"data": {
"result": 0
}
}The result is "0" and the relay is not switching.
Any idea?
Best regards,
Noël Vaes
-