Official EVOK API

• S

  After installation of a xG18 extention I get a Server Error 500 for the Rest Json
  • Stoeffel  

  21
  0
  Votes
  21
  Posts
  144
  Views

  Y

  Hi Martin, do you have any suggestions on how to resolve. I tried disabling node-red to see if that worked but no success. Am open to suggestions on what to try. If I have some extra time I will try a fresh SD card with the setup you verified for Stefan (specified vanilla neuron OS, install evok, and use the same evok.conf) to see if that will work.
• S

  Watchdog settings via EVOK
  • smontosa  

  3
  0
  Votes
  3
  Posts
  8
  Views

  M

  Hello @smontosa, please try to download the current version 2.4.10. The issue should be fixed. Please note that watchdog settings (same as other parameters) are stored in RAM memory by default. To burn it into non-volatile memory (FLASH), use the appropriate coil 1003 or call the separate REST request on the same endpoint with parameter nv_save=1.
• K

  Broken dependencies during EVOK installation
  • khachvla  

  3
  0
  Votes
  3
  Posts
  14
  Views

  K

  @Martin-Kudláček After flashing the image everything works fine. Thank you
• M

  Is there a way to set relays to default state after RaspberryPi reboot?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  31
  Views

  M

  Hello @mglowinski, sorry, but this feature is not supported in Unipi 1.1 series products. Please consider buying Neuron/Patron series PLCs which can do it.
• M

  Unipi 1.1 watchdog?
  • Maxiba  

  2
  0
  Votes
  2
  Posts
  15
  Views

  M

  Hello, unfortunately, the Unipi 1.1 does not have a watchdog device. You can see all available devices/circuits in reply to the "all" GET request. Example (can be invoked from your web browser): http://<your_unit_IP>:8080/json/all
• M

  How to count impulses on digital input via EVOK API?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Hello @mglowinski, the Evok doesn't have such logic. If the DI doesn't support counters (which does not on Unipi 1.1), the Evok is not able to share this information. This has to be done in your software. Best regards, Martin
• M

  Recommended way of connecting analog sensor
  • mglowinski  

  3
  0
  Votes
  3
  Posts
  17
  Views

  M

  Thx for explanation!
• M

  How to control relay extension board via EVOK?
  • mglowinski  

  2
  0
  Votes
  2
  Posts
  12
  Views

  M

  To make extension relay module (EMO-R8) working with EVOK below steps needs to be done: Open /etc/evok.conf file Uncomment relays assigned to EMO-R8: Each this line begins with a character ; This character must be removed for all lines related to the configuration for EMO-R8: ; ;Example of 8xRelay extension module addon (EMO-R8) on address 0x21 ; [MCP_2] i2cbus = 1 address = 0x21 [RELAY_9] mcp = 2 pin = 7 [RELAY_10] mcp = 2 pin = 6 [RELAY_11] mcp = 2 pin = 5 [RELAY_12] mcp = 2 pin = 4 [RELAY_13] mcp = 2 pin = 3 [RELAY_14] mcp = 2 pin = 2 [RELAY_15] mcp = 2 pin = 1 [RELAY_16] mcp = 2 pin = 0 Save /etc/evok.conf file Restart evok
• A

  Modbus CRC errors, rs485 extensions on Neuron
  • Achilleas Kotsis  

  5
  0
  Votes
  5
  Posts
  18
  Views

  

  Hello @Achilleas-Kotsis, the issue is not with the unipi-kernel-module, but with the unipi-firmware 5.52. We have removed it from our repository and advise to downgrade to 5.50 (and flash it to the HW via /opt/unipi/tools/fwspi). We are working on the fix. Thank you again for reporting this issue and have a nice day, Martin
• M

  Reading and sending data using UART via EVOK API
  • mglowinski  

  9
  0
  Votes
  9
  Posts
  47
  Views

  M

  I made it work. I enabled Serial in RaspberryPi Setting and and used /dev/serial0 and it worked. Thx @martin_triska for help!
• M

  Accessing I2C devices via EVOK API
  • mglowinski  

  5
  0
  Votes
  5
  Posts
  19
  Views

  M

  @martin_triska, thx for a tip. Indeed it worked quite well:)
• M

  Curl works, Python http.client.request not fully
  • Maxiba  

  3
  0
  Votes
  3
  Posts
  22
  Views

  M

  Thank you for the answer! I am using the websocket API now, as this suits my requirements the most. Have a nice day!
• N

  Read 1wire temp sensor on Axon
  • netman  

  2
  0
  Votes
  2
  Posts
  14
  Views

  No one has replied

• B

  installation of Evok on actual raspian fails
  • burnscm  

  4
  0
  Votes
  4
  Posts
  12
  Views

  

  Hello @burnscm, thanks to you, we have discovered that the package unipi-kernel-modules v1.54 for Neuron has been incorrectly built. It is now fixed and new OpensourceOS image has been built. I recommend to download the said image (https://kb.unipi.technology/_media/files:software:os-images:neuron-opensource-os_image-20210105.0.zip) and do apt update && apt install -y evok. Thank you for understanding and have a nice day, Martin
• L

  "time"-value for Digital Input on unipi?
  • Lasse  

  2
  0
  Votes
  2
  Posts
  20
  Views

  M

  Hello @Lasse , this value is Unipi 1.1 specific and comes from pigpio subsystem tick value. From documentation: tick: the number of microseconds since system boot. It wraps around after 1h12m
• S

  Extension xG18 on a Neuron failed, missing xG18.yaml?
  • Stoeffel  

  8
  0
  Votes
  8
  Posts
  55
  Views

  S

  So. Now I solved the problem: After a sudo apt-get remove --purge evok && sudo apt-get update && sudo apt-get upgrade && sudo apt-get install evok and with this new configuration in the evok.conf I got it: [EXTENSION_1] global_id = 2 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xG18 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory ;neuron_uart_circuit = 1_01 ; Optional allow_register_access = True ; Optional address = 1 ; Optional, scan_frequency = 10 ; Optional, scan_enabled = True ; Optional, ;baud_rate = 19200 ; Optional ;parity = N ; Optional, ;stop_bits = 1 ; Optional
• A

  Upgrading unipi-kernel-modules-dkms to 1.54 causes infinite reboot loop
  • Achilleas Kotsis  

  6
  0
  Votes
  6
  Posts
  42
  Views

  M

  Hello @Achilleas-Kotsis, I have tried to upgrade the system from a few older images (also with DKMS drivers) and this kind of behaviour did not occur. The issue seems to be coupled with the filesystem write operation and the following sync (should be invoked by umount command in the script). Moreover, the .inc file should be updated formerly within the upgrade process (as the step of unipi-common package postinst script). Can you retry the whole process with a new uSD card? This kind of problems sometimes occurs on corrupted cards as the write operation is not fully synced in fact.
• K

  Where is the modbus register map for Unipi 1.1 ?
  • Kermit  

  3
  0
  Votes
  3
  Posts
  18
  Views

  K

  You take any cheap 20$ China Raspberry hat and there is a 2-Page manual (in bad english) that gets you up toggling your inputs and outputs in like 20 minutes. I have now been digging for at least a solid 5 to 8 hours in the unorganized pile of stuff available here. Best I have found out now is Unipi 1.1 is outdated and abondoned. Existing docs do not mention all the things that are unimplemented. I will now just throw away the board and not sink any more time in it.
• 

  Indoor Air Quality (IAQ) sensor modbus connection not working
  • Balardo  

  4
  0
  Votes
  4
  Posts
  40
  Views

  M

  Hello @Balardo, you are right - there was a bug in schema validation for /json/all endpoint. It should be fixed in the next release. According to the direct Modbus unit register access - you can use e.g. http://<your IP>/json/unit_register/UART_15_2_42 to get the ambient_light register: {"status": "success", "data": {"name": "ambient_light", "value": 122.51519775390625, "glob_dev_id": 2, "dev": "unit_register", "circuit": "UART_15_2_42", "unit": "lux"}} Register values has been also added to the web control panel: You can test it by install the test version: sudo su apt update && apt install evok=2.3.3.test.20200923165635*
• J

  filter websocket input in order to get all devices except temp
  • juntiedt  

  3
  0
  Votes
  3
  Posts
  17
  Views

  J

  one important thing at the end: as soon as you apply a filter the received msg.payload from websocket comes in an array. this means: before the applied filter you could your device with msg.payload.dev with applied filter you must read the device as msg.payload[0].dev !!!