• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. actiwerks
    3. Posts
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 5
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by actiwerks

    • RE: 1-Wire sensors in Evok

      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 ?

      posted in Official API - Evok
      A
      actiwerks
    • RE: 1-Wire sensors in Evok

      Thanks for the tip, this Rest call works for me. Perhaps it is good idea to include it to the API docs (https://evok-1.api-docs.io/1.01/) I couldn't find any note about the "sensor" usage there.
      I use the same hub (athough got it elsewhere) think I got the topology right, have three sensors connected, and only can see two of them. Will try to check if one of them is not faulty.

      posted in Official API - Evok
      A
      actiwerks
    • 1-Wire sensors in Evok

      Trying to read the values from DS18B20 temperature sensors. When I connect single sensor, I can get the value in the UniPi Control panel, it is listed in the REST API (when I do the rest/all call) but I am unable to figure out the request to get just single value. I tried many variants, tried to follow schema /rest/ai/{circuit} mentioned in the documentation, but all I can get is the 500 internal error. What is the correct rest call to get this value?
      Another problem I face is that if I connect 1Wire hub, I can see just the same single sensor, while others are invisible. I am using the correct topology. Any idea what could go wrong there ? How often is the 1Wire bus scanned for changes?
      The third issue is that I would like to connect a different kind of sensor, which is not listed in the list of supported 1Wire devices...wouldn't it be possible to add a support of any 1Wire device and just pass the raw data through the interface? Thanks.

      posted in Official API - Evok
      A
      actiwerks
    • RE: Internal Error (500) after fresh Evok installation

      I also noticed that I can't stop Evok service the way it is described in the Github (debugging section). I get "Failed to stop evok.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files" - does this mean that Evok was not properly installed ?

      On top of that, I have the log file full of the following error :

      2017-11-07 23:10:21,222 - evok - ERROR - 'NoneType' object has no attribute 'do_scan'
      Traceback (most recent call last):
      File "/opt/evok/neuron.py", line 217, in scan_boards
      yield self.modbus_cache_map.do_scan()

      posted in Official API - Evok
      A
      actiwerks
    • Internal Error (500) after fresh Evok installation

      I got Neuron unit and try to bring it to life, but I got stuck at the moment when I installed Evok on it. It seems to work, there are no conflicts, but any call, such as http://my_address/rest/all ends in "{"status": "error", "message": "Internal Server Error", "code": 500}" reply. Not sure what could go wrong, and the documentation gives me any hints. Anybody has any idea what could be the reason for this ? Thanks.

      posted in Official API - Evok
      A
      actiwerks