Hi @domguard,

The mentioned problems should not be related to EVOK at all. It's not clear from your description what kind of controller you have or what you actually need. Do you need to connect to an existing WiFi, or do you want to create a WiFi access point from the controller?

But EVOK works normally, right?

Best regards,
Antonin, Unipi team

@martin_triska Thanks a lot!

I had to do some debugging due to incompatible base source deviceTree (which was ultimately resolved by patching the compatible directives and a bit of merging together), but your response helped a ton!

It works like a charm, so again, thanks! We plan to open source parts of the project in the future as well (along with a stable release) ... so hopefully it will help someone else too :)

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

I see now that these are included in neuron-main tree, but it was never installed on my rpi because the install script failed.

The following packages have unmet dependencies: unipi-kernel-modules : Depends: raspberrypi-kernel (= 1:1.20221104-1) but 1:1.20230106-1 is to be installed E: Unable to correct problems, you have held broken packages. Cleaning temporary files Cleaning temporary files

I am guessing you need a better way of determining the platform, otherwise this is going to break each time a new rpi kernel is released before you have a chance to build the modules package...

If anyone needs a workaround, install like this:

wget -qO - https://repo.unipi.technology/debian/raspberry-install.sh | sed s/unipi-kernel-modules/unipi-kernel-modules-dkms/ | bash

Hi @Brzezinol,

you can try using nginx + LetsEncrypt for this.

Best regards,
Antonin, Unipi

Hi @juntiedt,

if you flashed Mervis OS to the SD card, SSH must be enabled, as SSH is disabled by default for this OS image. For our other OS images (Node-RED OS, OpenSource OS) SSH is enabled.

If it still doesn't work for you, this article might help you: https://kb.unipi.technology/en:automation:unipi-ssh-connect-hidden

Best regards,
Antonin

Hello @Vesa-Kauppinen,

The 'dev' field describes an object type (similarly to di or relay) so the key has to be constant regardless of the PLC series. You are right, this can be a little bit confusing - it's a piece of history ;-).

Now, we will add the new field of a family containing Patron/Neuron/Axon string.

The 'dev' field fix is a breaking change of the existing API and will be subject to change within an upcoming new Major version.

Toto by mne také zajímalo. xS11 ovládat můžu, ale DirectSwitch rozjet nedokážu. Zkoušel jsem vyčíst status registru pomoci mbpoll, ale tam se mi nepodařilo získat smysluplná data.

In the event monitor of FHEM I can see also the following message when I make a "get all": "2022.01.02 14:17:08 3: Neuron (NeuronL513) error decoding response: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 5830 (before "NaN, "circuit": "3_0...") at ./FHEM/00_Neuron.pm line 424." As I can see the error occurs on AI 3_01 or an other till AI 3_04.

It is a problem related to power-supply.
It was some voltage peaks while connecting anything to the same circuit as power-supply.
I've a better one (Phoenix Contact) and it's working stable now.

Topic closed.

The issue was caused by a combination of 64bit Linux kernel and bundled pigpio subsystem (used for peripheral access). After pigpio updating, Evok works on a 64bit platform properly. This change will be part of the next release.