Hi @marko2276 , thank you for the implementation. I have been testing it in my house installation, and it works pretty fine!
I also successfully tested the your light component, the binary sensor component and the cover component.
Everything works, but I would like to ask for your help with one small thing:
When I operate the cover, no matter up or down, the status up or down stays active forever. It would be nice if the status is automatically reset. Unfortunately, do not find the error. Can you tell me what I'm doing wrong?
Is there a parameter I can set?
I would be very happy if you could help me.

Thanks in advance,
Walter

Looks like Mervis isn't very useable after all and things have moved to node-Red.

will go there 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

@Martin-Kudláček Hi
After a long time of trying and many tutorials, I made it
to switch my relays on my Unipi 1.1, to read temperatures and everything with ModbusTCP and Nodered. When I see it now, it's very easy, thank you for the great board and the software.

Hallo
Ich habe bei mir ein unipi 1.1 bekomme auch Information von mervis zurück ,jetzt meine Frage ,wieviel Modbus Knoten kann ich in node red einbringen.
Ich habe 3 Stück, bei den die Verbindung unterbricht
Was mache ich falsch

Dankeschön für eure Antwort

Udo

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.
Below link to complete tutorial how to connect the S11 extension using node-red
https://youtu.be/HJJRrV9tV7U

I did as shown above. Ended in an Neuron M103 not booting :(

Unfortunately I do not have a possibility to attach a screen to M103 (or can I use the HDMI of the inner Raspi?)

I ended up in restoring the previous image.

So I can not even tell what the issue was- I guess some kernel/ grub based issues.

At current stage I would recommend against the above upgrade procedure.

/KNEBB

Dobrý den @ondbyr2561 ,

příklad naleznete na snímku níže:

5a3961da-bc15-458d-9995-7e86234d2f33-obrazek.png

Přeji hezký den,
Antonín z Unipi

Hello,
I have the same problem but I use NodeRed and EVOK API.
All the sensors connected directly to my Neuron L203 started showing a constant temperature out of nowhere, which was very dangerous. However, the sensors connected via xG18 were showing correctly.
Since then I restart the evok with cron task every hour just to be safe. systemctl restart evok.
1-w-stuck.png