@Niko-Raes Exactly, its polls per second. Honestly, I have not tried the maximum because it depends on the exact model - with more IOs there are more values to be read which results in smaller possible polling rate.
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.
@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.
@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
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.
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.
@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 :)