Topics created by juntiedt

Hi @juntiedt,

Yes, it is possible. On the Unipi 1.1 Lite there is a GPIO connector where the necessary GPIOs are available.

A description of the GPIO connector is available in the Unipi 1.1 Lite documentation. The description of the RJ11 connector on the EMO-R8 is directly on the board.

Best regards,
Antonin, Unipi

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

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

one important thing at the end:
as soon as you apply a filter the received msg.payload from websocket comes in an array.
this means:
before the applied filter you could your device with msg.payload.dev
with applied filter you must read the device as msg.payload[0].dev !!!

Hello @juntiedt,
the Unipi 1.1 doesn't have RS485 interface, so you need to use some RS485/USB converter. The latest Evok has support for xG18, you just need to set it in the /etc/evok.conf as a normal Unipi Extension.

Hello @juntiedt,
this sensor comes in the 3 wire connection + shielding. You can connect it to the 1-Wire hub, ideally as a last sensor. Please consult the 1-Wire hub pinout https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden

thanks for your information.

I have connected a 4 wire cable very close to the three wire sensor and connected the data line to 2 wires in order to use the hub. At the moment it works.

Hi Martin,

thanks for your help and support.
All running again!

regards Hannes

Node-Red on Raspi 4 works perfect - no problems at all

Hello @juntiedt,
I'm sorry for not getting back to you in timely manner. This error is in the Evok and we have created a bugfix. Next week we will release a fixed package and if everything goes well today, the source code will be available on the Evok's Github.

hank you for your patience and have a good day,
Martin

{"status": "success", "data": {"group_assignments": [[{"value": 0, "pending": false, "circuit": "1", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "3", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "2", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "5", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": true, "circuit": "4", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "7", "dev": "relay", "glob_dev_id": 0}, {"value": 0, "pending": false, "circuit": "6", "dev": "relay", "glob_dev_id": 0}, {"value": 1, "pending": false, "circuit": "8", "dev": "relay", "glob_dev_id": 0}]]}}```

Hi @juntiedt,
there is a M103 with 8 relays.

this works as well:

msg.url = "http://10.0.0.52:8080/json/relay/3"; msg.headers ='({"content-type":"application/json"})'; msg.payload = '({"value": "1","timeout": "20"})'; return msg;

@juntiedt said in MQTT to unipi Control Panel:

As the flow is to big to upload I am just sendig a picture. Let me know if you want to get the flow directly.

Hi @juntiedt, it looks like a very great job! Could you consider hosting the file and provide a public link? You might for instance use a Dropbox / pCloud public link, or a GitHub gist.

If anyone has ideas for improvements please let me know.

I think it might be possible to parametrize the flows with variables, in order to avoid repetition. At least, it seems it was done this way by @Jan-Teunis here:

https://forum.unipi.technology/topic/735/node-red-flow-evok-to-mqtt-to-evok

0_1551607450428_unipi-mqttt.JPG

Hi @juntiedt!
That looks great, and does perform very well.

@juntiedt OK, thanks for the additional info. We'll take a look at it.