hi @marko2276,
Thank you for sharing your integration.

I am a beginner and now I used it for HA communication with NEURON M203 via EVOK layer. Installation of the integration and configuration of the LIGHT sensors (I used for DO and RO outputs) are fast and functional. Turning on/off the relay on M203 has a small response:
Clipboard01.jpg
When I added the BINARY sensors (DI) configuration, the problem already arose => LIGHTs do not work at 100%:
Clipboard02.jpg
I always check the configuration in Developer Tools before restarting HA:

#UNIPI NEURON via EVOK unipi_neuron: - name: "neuron5" type: M203 ip_address: 192.168.88.20 reconnect_time: 30 light: - platform: unipi_neuron device_id: "neuron5" devices: - name: svetlo_garaz device: relay mode: "on_off" port: "1_02" - name: svetlo_dilna device: relay mode: "on_off" port: "1_03" - name: svetlo_vcelin device: relay mode: "on_off" port: "1_04" - name: svetlo_zidky_1 device: relay mode: "on_off" port: "2_05" - name: svetlo_zidky_2 device: relay mode: "on_off" port: "2_06" - name: svetlo_zidky_3 device: relay mode: "on_off" port: "2_07" - name: majacek_svetlo_zelena device: relay mode: "on_off" port: "2_08" - name: blikac_fasadni device: relay mode: "on_off" port: "2_11" - name: svetlo_fasada_garaze device: relay mode: "on_off" port: "2_12" - name: majacek_svetlo_zluta device: relay mode: "on_off" port: "2_13" - name: majacek_svetlo_cervena device: relay mode: "on_off" port: "2_14" binary_sensor: - platform: unipi_neuron device_id: "neuron5" devices: - name: tlacitko_svetlo_fasada device: input port: "1_01" - name: tlacitko_svetlo_garaz device: input port: "1_02" - name: tlacitko_svetlo_dilna device: input port: "1_03" - name: tlacitko_svetlo_vcelin device: input port: "1_04" - name: kontakt_dalkove_ovladani_A device: input port: "2_01" - name: kontakt_dalkove_ovladani_B device: input port: "2_02" - name: tlacitko_otevreni_vrat device: input port: "2_03" - name: tlacitko_zahradni_zalivka device: input port: "2_04" - name: kontakt_vrata_v_pohybu device: input port: "2_05" - name: kontakt_vrata_zavrena device: input port: "2_06" - name: kontakt_vrata_otevrena device: input port: "2_07" - name: kontakt_vrata_prekazka_v_zavreni device: input port: "2_08" - name: tlacitko_opusteni device: input port: "2_09" - name: kontakt_PIR_osoba_vgarazi device: input port: "2_10" - name: kontakt_kour_v_garazi device: input port: "2_11"

Could you advise me where the problem could be?

I would also like to use this integration on the NEURON L303 and L403, where I have connected analog inputs, analog outputs, and 1-Wire temperature, humidity, and lighting sensors. Will you please complete the configuration for these mentioned inputs and outputs as well?

I look forward to your reply
Petr

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