Ok, I'll do it on the board then.
I'll take my chances communicating directly with the modbus tcp server instead of using Evok's layer.

Cheers,
Ronan

Hi @martijn-hemeryck, those are great news! I'm glad we were able to put it together, together:) I'm looking forward for your results.

Martin

I took up the sysfs-based approach in my own (golang-based) project: https://github.com/mhemeryck/unipitt

Basically, it does active polling on a series of files, representing the different inputs and pushes out an MQTT-event in case there's a change.

Hi @anders-kjellström,
it works, you can check in the default installation of the Evok:

0_1560149083570_115de405-bd5a-4d14-b1f8-b0f9913f3249-image.png

Do you have some example where the aliases don't work?

Best regards,
Martin

Yes, it is clear now. You have to implement this kind of functionality by yourself as Evok does not offer it.

@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

@tomas_hora I installed a clean OS from UniPi website and everything works.

@roberts_lando Evok uses the Modbus TCP interface to interact with the IOs, disabling it will cause that evok wont work.

You can disable it by calling "systemctl stop unipitcp" and "systemctl disable unipitcp".

Hello @burnscm,
moreover, the Modbus doesn't allow to have address 0 and you cannot set the address 0 via our DIP switches. When the DIP switches are in "0" position, the extension uses the address which is stored in the NVRAM, which, by default, is 15.

Best regards,
Martin

@martin-kudláček Thank you Martin, will do that.

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

Hy @martin-kudláček,

Thanks for the reply!

Today I tried again to connect with ".../json/all" and it works.

The only difference compared to my first post is that I restarted the UniPi couple of times whereas at the time of my first post the UniPi was online since weeks.

We are using UniPi Neuron L503 (S/N: 215) with Neuron xS40
Evok PrecedingRelease:v.2.0.7h PrecedingRevision:379

I installed Evok manually

Thanks and greetings
Helmut

Hi @vesa-kauppinen,
writing 1 to coil 1001:

mbpoll -m tcp -a 0 127.0.0.1 -t 0 -0 -r 1001 1

Writing 0:

mbpoll -m tcp -a 0 127.0.0.1 -t 0 -0 -r 1001 0

You can learn more from the quite detailed help of the mbpoll:

mbpoll -h

Regards,
Martin