@s0fralk

Basically yes, I recommend websocket but it is up to you what is your approach.

That is for those, who want to develop their own application like Evok which will take care of the low level work with GPIOs and I2C.

Hello @jilet,

I am sorry but unfortunately not. The work is however in progress. I will try to push the update asap.

Hi @tomas_hora

Thanks for your reply, I thought that might be the issue. Using the WebSocket example from the evok git page works perfectly so I will build on that example.

Thanks!

@tomas_hora Hi,
I did a fresh Rasbian install, got the neuron online, did a
git clone http.....
set the permissions (as per the GIT page)
started it up.
and....

PERFECT!

I have my python monitoring program starting automatically as a service, and I had to put a little sleep command in it on start as it was trying to run before EVOK started. Runs great.

Many thanks.
Merv.

@tomas_hora Well, I guess I did have a small typo in my owfs.conf file, but I have fixed that. Here is my current owfs.conf file:
0_1490041735702_UniPi_4.JPG

All the lines above these are commented out.

I still see multiple sensors with invalid IDs, and there are no w1_slave files:
0_1490041819222_UniPi_5.JPG

Thank you again.

Steve

@paulot Do you see the device with address 18 on the i2c bus? Issue i2cdetect -y 1

Hello @SOswald and welcome to the community.

First of all I am sorry that there is still not enough documentation or examples.

We designed EVOK only to act as API which provides easy access to all IOs of UniPi including basic web interface providing overview of state of IOs and basic configuration. It is not a designed to act as a example of a application for complete description of behavior or visualization of the sysytem.

So if you like coding, take a look e.g. at Node-Red. We have made simple example of communication using websockets on it and you can also easily build nice web interafes using Node-Red.

@tradlost.se Basically yes, but since I do not know much about your board it is hard to tell.

@cvdd https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay is only for Neurons and will not work for the UniPi 1. For UniPi 1 there is only Evok as API from us. But if you need Modbus and do not want to use the HTTP REST api, websocket or JSON RPC, then take a look at someone implementing Modbus for UniPi 1

@ubee Thanks for the tip! I will take a look at it.

@Merv,

I have the same problem. It doesn't help to change the log level in the service file. It still continues dumping info about every read attempt which is annoying. I guess the "I" in the log indicates log level is Info. And it remains I whatever level you set.

Try reinstalling the Modbus server as described here: https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay

@HarishKumar
The evok itself is not designed to handle the logic of your application. That's why we call it API.

It is using Tornado which means the server itself runs in one loop so you need to have all the program behavior ready before it is called mainLoop.start(). So if you run an infinite loop anywhere in evok, you stop everything else (reading, setting, all APIs, ...).

So I suggest using that APIs, it is much more easier to implement and you have the same functionality. But if you would REALLY want to do it in evok, you would have to prepare your program in a function, all tasks that would take more time would have to be decorated as coroutines and the call has to be yielded in order not to stop the main loop. The logic behind this is a little bit complicated to describe in one post :)

@tomas_hora Awesome! When I have time again for this project, I'll try it!

@tomas_hora

BTW, I absolute love Neuron! <3 I'll put it everywhere.

Having a simple REST API is a bless.

Thank you for all your hard work that goes into UniPi!

@zeus I will think about it how to make it possible, Thanks for the tip: https://github.com/UniPiTechnology/evok/issues/11

@fipsi72 You can place evok behind a proxy of course...

@Juergen Relay 1 does not exists. Check the web interface of evok for correct identification. The correct identification is eg. 2_1

@Kitaps IC stands for Integrated Circuit. What code?