• Evok problem getting I/O boards data

    9
    0 Votes
    9 Posts
    6k Views
    T
    @Andrew-Watson said in Evok problem getting I/O boards data: Some additional information, since I had time. I flashed a new sd card with a brand new raspbian stretch lite image (latest version, 2017-11-29) installed git and updated the system sudo -s apt-get install git apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y raspi-config and changed the hostname Then installed the latest evok version (from commit 8a14c95 it seems). Selected website port 80 Internal API port 8080 Install for Unipi Neuron (I have the S103) No WiFi Reboot And this time it works... I don't know if this is due to something that was changed in the last commit (between 11am and 1.30pm today) or simply not installing the gpiozero library. It's quite likely it may be the GPIOZero library. Generally speaking software connected to hardware in a direct manner (with its own drivers etc.) is considerably less compatible among itself than other software. We test EVOK internally on clean Raspbian, as well as with our own image, which is based on the Raspbian Zero; for these combinations, along with some simple software (in fact EVOK installs vim itself), the software does pass testing (with occasional edge issues e.g. the light sensor issue recently). As to a guess why the GPIOZero library could be causing issues - we use 4 of the GPIO lines on the RPi to expand the primary SPI bus with interrupts and an extra device select slot. This (among other things) is done through the device overlay installed by EVOK, but it's possible that other software (at least one which is set up under root privileges) might change it, particularly if it deals with GPIO functionality. The latest commits only changed functionality related to the Sedtronic WTS DS2438 1Wire sensor, so it's very unlikely to have caused the problem. The issue you (and @tempurpri) are seeing is due to the expected boards not being found on the SPI bus - this can be because the SPI bus does not function correctly for some reason, or because the I2C EEPROM which stores data about which boards are expected does not function correctly. @tempurpri said in Evok problem getting I/O boards data: @tomas_knot The incompatibility with Codesys (the one you mention and the port incompatibility) would be an understandeable reason for the problems I have....had I not managed to have a working setup of Codesys for raspberry and evok running in the last month. Unless the 1-wire incompatibility between the two only becomes problematic with time (I'm not sure how that could be), then that was not the case for me. Just to make it clear Codesys and digital signal readout worked for me ... Modbus acces and the web interface. I needed that functionality only occasionally, so I'm not sure when it stopped working, but it was during the last month. Neither Codesys nor evok were re-installed nor was there any change in their configuration. I'm trying to find out what happened and especially try to make it work again. @tomas_knot @tomas_hora I understand that proper codesys integration is coming, but unless it's coming during this week it won't help my application. Unfortunately that's the timeframe I'm looking at, nothing to do with with Unipi itself. OK, so if codesys 1 wire driver is the suspect, is there a way to check that and maybe disable it within the Codesys editor ? I was assuming you have a 1Wire UniPi expansion board, which would not work correctly with Codesys. If you do not, it may still be possible to get it running. But first - does the device function correctly with a clean non-Codesys image? If yes then we can confidently say the issue lies with Codesys, and proceed from there.
  • Evok high CPU usage

    10
    0 Votes
    10 Posts
    6k Views
    T
    In the end, nothing else than starting from scratch with a fresh image of the open-source OS helped. Then I was able to change the evok port to 8085 (instead of 8080) and nginx port to 85 (instead of 80) prior to installing codesys and it worked. .. .. for a while. I started a new separate thread since the problems have a little bit different symptoms.
  • No handlers could be found for logger "websocket"

    8
    0 Votes
    8 Posts
    5k Views
    S
    Good day, I do receive all JSON stings from my DS18B20 temperatur sensors and from my DS2413 (Wire Dual Channel Addressable Switch) but I do not receive any strings from DS2438 at moment. I could get the JSON string via the wget method or via http://127.0.0.1:88/rest/all. Do you have any idea on how I could get the strings via the above mentioned python program via Websocket; I actually do not understand why I do not receive the DS2438 strings...
  • SEDtronic Temp and Light intensity sensor

    4
    0 Votes
    4 Posts
    3k Views
    J
    Sorry. Last point is solved. It was a cabling problem. But I have still a question regarding the correct humidity and light intensity. I used the formula for humidity as in the data sheet. Seems to be ok as the result is close to my net- atmo station. regarding the light intesity I don't understand what I have to do. What does Vsens input1 and input2 mean. My vad and vdd dont show the values mentioned in the data sheet.
  • Flask Webserver using nginx

    6
    0 Votes
    6 Posts
    4k Views
    T
    @juntiedt You must have made your changes wrong I'm afraid. Try "sudo systemctl status nginx". NGINX configuration is documented in detail on the NGINX project website, where you can find more help on how to create your desired configuration. Evok doesn't use any non-standard option that I am aware of.
  • Amazon Alexa (UniPi 1.1)

    2
    0 Votes
    2 Posts
    2k Views
    T
    @Ueli-Iff eg https://forum.unipi.technology/topic/524/websocket-filter/7
  • DS18B20 and 12bit resolution.

    2
    0 Votes
    2 Posts
    2k Views
    T
    @rbielefeld not by a parameter, you would have to do it in code ow evok, check https://github.com/UniPiTechnology/evok/blob/master/evok/owclient.py#L125
  • M203 clean evok install not working

    2
    0 Votes
    2 Posts
    2k Views
    R
    Quick update: I repeated the Evok installation as per the instructions above on a clean vanilla raspbian stretch image taken from the official raspberry pi repo (not the UniPi customized one) and everything works fine. Thus - there seems to be some misconfiguration in the official UniPi image, at least when used with M203: beware. Rob
  • One-Wire sensors

    2
    0 Votes
    2 Posts
    2k Views
    T
    Hi @juntiedt! EVOK is designed to work with Sedtronic 1-wire sensors, which you can buy through our store: https://www.unipi.technology/sedtronic-1-wire-sensor-p67?categoryId=3 It will also work with some other 1Wire sensors, but unfortunately the sensors do not have a standardised error correction calculation, and so you will likely get inaccurate results with them.
  • 1-Wire sensors in Evok

    5
    0 Votes
    5 Posts
    3k Views
    A
    This is where it gets weird. My OWBUS section is as follows : [OWBUS_1] owbus = /dev/i2c-1 --i2c=/dev/i2c-1:ALL ; Scanned bus (--i2c=/dev/i2c-1:ALL or localhost:2122 or 'u' for USB dongle) interval = 3 ; [s] Default sensor reading scan_interval = 300 That means the scan is 300 miliseconds, correct? I only have one sensor connected, but the Evok web interface still shows values from two sensors...looks like it stopped updating after first read. Any ideas ?
  • Websocket filter

    7
    0 Votes
    7 Posts
    4k Views
    J
    ok. In which directory should I look for the evok software?
  • Unipi/evok input change detection lagging

    3
    0 Votes
    3 Posts
    3k Views
    O
    Ok, I understand. For now we will burn some cpu to avoid lagging :) Setting polling interval to 8 or 9 works for me at the moment. Although in my opinion if you want to be taken seriously on the market, you really have to improve this part. Other than that, so far I am really happy with the device. Thanx for your replies and support. Regards, Matic
  • Setting filter corrupts the websocket message

    5
    0 Votes
    5 Posts
    4k Views
    T
    @oversc0re You can increase the interval in which evok polls the individual boards for updates in the evok config file /etc/evok.conf. See the scan_frequency parameter of [NEURON] unit and increase it to 5 for start
  • 1wire sensor not giving values...

    2
    0 Votes
    2 Posts
    2k Views
    T
    Hi @Pavelf! It's possible - do you have OWFS installed still? It could be caused by a faulty sensor as well, try plugging them in one by one.
  • Proper way to set websocket filter ?

    4
    0 Votes
    4 Posts
    3k Views
    H
    @tomas_knot Thanks, I will try that. How could I ask for input states through websocket, without using "all" query message? For example ideally I would like to ask about the state of one spesific input ? Or perhaps state of all inputs. -- Henkka
  • Evok Web does not Start

    12
    0 Votes
    12 Posts
    7k Views
    H
    @tomas_knot Hi, Thanks, I think now it's clear. Right after boot I tried multiple times same command, with only few seconds in between; Results are somehow changing; pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom See how last 3 lines there is suddenly no eeprom available ? So something fishy about i2c bus perhaps. I then went on to think about connecting oscilloscope to see what's going on and what we have done so far. When thinking about where to connect it, it hit me - we have an external 7" Pi LCD connected to Raspberry Pi Display connector and it has those 2 extra SDA and SCL pins... Could they be reason for this... They are there for A and B model Pi's that don't have these integrated to display-cable and as this is version 3 Pi, they should not be connected as those are routed via display cable. So I disconnected them and after boot so far it has performed flawlessly! Below are results of the same "test" as above, this time results are all predictable and ok, every time there is an eeprom device on the bus. pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches pi@f:~ $ sudo grep M503 /sys/bus/i2c/devices/1-0057/eeprom Binary file /sys/bus/i2c/devices/1-0057/eeprom matches So, this was my error, not thinking that connection of LCD could anyway be in part of this... Sorry about that. But many thanks for your excellent support! For me at least, I think the issue is now solved (fingers crossed...).
  • Internal Error (500) after fresh Evok installation

    12
    0 Votes
    12 Posts
    7k Views
    T
    @Vesa-Kauppinen Glad to hear it works now! EVOK 2.0 should work fine UniPi 1.1, but obviously much of the extra hardware functionality which Neuron has will be missing. The UniPi 1.1 also has an EEPROM, it's just in a slightly different format. The reason that the installation needs to know which hardware you have is that we need to install certain different libraries to get the hardware to work correctly. Unfortunately this cannot be done automatically, as the EEPROM is not loaded during the installation yet.
  • Problem with get_relay and jsonrpclib

    8
    0 Votes
    8 Posts
    4k Views
    T
    @Hen-Ri Glad you got it working! The bug is not really very significant - basically some of the function use a different name. It's a matter of adding two lines to the code for each device type.
  • Error running install command for unipi_eprom when booting stretch

    4
    0 Votes
    4 Posts
    2k Views
    T
    If I2C works, then the errors should be harmless. The modules are used for older versions of Raspbian, and as a whole don't indicate that anything is wrong by itself. You can delete the 4 lines in /etc/modules to stop the error from cropping up. We'll try to do it with kernel version detection during the installation, or drop the old versions altogether. Edit: The insmod fails because the modules are compiled for an older kernel, and will only load on old Jessie
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    10 Views