Official EVOK API

• J

  Watchdog and LED Device mixed in JSON/REST Interface
  • Joerg

  4
  0
  Votes
  4
  Posts
  51
  Views

  T

  It should be fixed in the latest Master development version on GitHub, but it may take a little while before the next release is done. You can test it out yourself by replacing the file as detailed above.
• Y

  This topic is deleted!
  • YoleJemd

  1
  0
  Votes
  1
  Posts
  4
  Views

  No one has replied

• Z

  This topic is deleted!
  • zhangzk

  1
  0
  Votes
  1
  Posts
  14
  Views

  No one has replied

• C

  1-wire sensor not detected in Evok web interface
  • clueless

  9
  0
  Votes
  9
  Posts
  381
  Views

  T

  Hi @clueless, Glad to hear it's working - I'm not sure what exactly could have gone wrong, as everything seemed to be okay in the logs, which left me, well, quite clueless. I was hoping to get back to you with some more information, but frankly could not think of any simple checks to be made. At any rate - I am very glad to hear that it is working for you now!
• J

  Way from Neuron Beta Image to regular Release
  • Joerg

  4
  0
  Votes
  4
  Posts
  209
  Views

  

  Hi @joerg, the UniPian image is indeed broken and not just the download file. There are problems inside, so we removed it from our website and until further notice, it will not be available. You can use stock Raspbian and just to install our packages. To learn how, read this tutorial: https://kb.unipi.technology/en:sw:04-unipi-firmware Best regards, Martin
• B

  This topic is deleted!
  • blair2019

  1
  0
  Votes
  1
  Posts
  30
  Views

  No one has replied

• M

  Switching relays in synchronous mode?
  • majorcsa

  3
  0
  Votes
  3
  Posts
  255
  Views

  T

  Hi @majorcsa, I have added this feature via a config file switch to the Master branch of EVOK. As I've mentioned before it may take a while to propagate to our releases and debian packages, but you should be able to test it out manually. I hope this helps, Kind Regards
• J

  Vanishing 1-wire sensors
  • JasperJackson

  14
  0
  Votes
  14
  Posts
  739
  Views

  T

  Hello @stoeffel, If this happens, you do not need to reboot the whole neuron, just reset the 1Wire bus using Modbus or OW_off variable in case of Mervis. Let us know what you find out.
• 

  sysfs interfacing
  • Martijn Hemeryck

  6
  0
  Votes
  6
  Posts
  429
  Views

  

  'nother update: giving it some thought, I quickly wanted to see if I could do the same stuff again in go, so here goes another POC: https://github.com/mhemeryck/unipitt/blob/37b9a07bc570301c2a11836526df1a2be8b21647/main.go (Don't mind the project name though, I've sort of ran out of original names, I guess) Anyways, performance seems much better in this case. I figure I'll put my efforts into polishing this project as it seems to be the simplest, fastest, most robust. I did notice however when toggling one of the DI's, that another DI also got toggled somehow, still need to investigate that further. Thanks for continuous feedback, this actually adds a lot to me for the overall unipi experience!
• L

  EVOK and PIGPIO
  • luc

  6
  0
  Votes
  6
  Posts
  478
  Views

  L

  @tomasknot The wiegand is 0-5 Vdc (it's not even 5 its 3.8Vdc) Wiegand data pulses are 50ys width and come at 1ms wiegand protocol (while Neuron DI locial 1 must be higher then 4.5Vdc and min puls with is 20ys) Is there any possibility to connect this to Neuron M103 Are there raw PI inputs available?
• T

  Working with EVOK API for the first time
  • thiagoralves

  25
  0
  Votes
  25
  Posts
  1487
  Views

  T

  Alright, thanks! I'll try the package installation on Raspbian and report back if I have any issues.
• D

  No inputs or outputs accessible
  • dominikmlkvy

  2
  0
  Votes
  2
  Posts
  252
  Views

  T

  Hi @dominikmlkvy, This looks like a hardware problem. Are there any visible signs of damage on the board, or perhaps an interrupted connection somewhere? It might help if you can provide photos of the device in it's current state with a sufficient resolution to examine the hardware. If you are positive that you have not used the device in a way that is outside the intended operating parameters you can send the device for a replacement, but you may be charged some or all of the cost if the fault is due to improper use. Please contact support@unipi.technology for further help. We keep test logs of our devices before sending them out - it would help if you could provide me with a serial number of your device so I can check it, but I don't expect that it failed testing as we perform a final check before sending each product. I hope this helps
• S

  Evok - Websocket bugs/problems
  • StevenBrs

  3
  0
  Votes
  3
  Posts
  376
  Views

  S

  Follow-up on this one: Bullet 1 and 2 are still a problem. Unipi people, can you please comment on this ? Bullet 3: When changing a relay state I get an array back with all relay states of that group. This was a problem because I wanted to propagate the state change to MQTT. I solved this by looping over the array and returning every state. Although this creates a little overhead, MQTT is fast enough to handle.
• W

  All ports disappear via webinterface after EVOK update on L203
  • wizro_pl

  7
  0
  Votes
  7
  Posts
  425
  Views

  T

  @wizro_pl The thing is that the evok installed from debian package is not compatible with the one installed as mentioned on github. To make it easier, please use the Raspbian stretch lite and install evok according to the guide on Github. We will publish a UniPian OS with the package version of evok soon.
• S

  Analog Input - Evok Settings are not clear
  • seecosmea

  2
  0
  Votes
  2
  Posts
  191
  Views

  T

  @seecosmea If you wish, you can set a lower bit resolution to get faster read of the AI. The correction is stored in the onboard memory (corr_rom and corr_addr), if you comment these out, you can set it manually using the correction parameter. Ignore the gain parameter.
• G

  JSON Bulk not working
  • Gradient

  4
  0
  Votes
  4
  Posts
  383
  Views

  

  Hello @gradient, we can confirm, that the provided script doesn't turn off all relays, as it should. If a delay of at least 7.5ms is inserted between the commads, the result is as expected. We will look into this, but I cannot say when the fix will be released. Thank you for understanding, Martin
• M

  UniPian Neuron OS on UniPi 1.1
  • Martin Trojan

  3
  0
  Votes
  3
  Posts
  292
  Views

  M

  Ok. When you write it like that it makes sence :). I have readed UniPi 1st generation -> This is the same image as for Neurons -> Click -> Choosed image only with Evok. Opensource images was not familiar for me as I was looking for prepared image. Maybe try to make it more obvious and place guide from git hub on the same page, to make it consistent. Anyway thank you for your reply.
• 

  Axon M505 bluetooth
  • Vesa Kauppinen

  3
  0
  Votes
  3
  Posts
  312
  Views

  

  @martin-kudláček said in Axon M505 bluetooth: Could you please share with us your intention, so I can point you to proper solution? Hi, We have developed our own software for Axon. We would now like to have Bluetooth enabled. With these instructions (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Plus2#Bluetooth), we have not been able to do it work. I would be very grateful if I could get specific instructions for starting Bluetooth. Also ping @TomasKnot /Vesa
• O

  Websocket connection dropping
  • oversc0re

  13
  0
  Votes
  13
  Posts
  1547
  Views

  T

  It should only disconnect if either a certain number of requests fails to reach the client; or no successful messages have been sent over >10 minutes, while there have been failures during that time. The actual implementation/behaviour is from the tornado.websocket library, albeit we use a slightly older version of Tornado. If you do have the time to investigate further we would quite welcome the feedback. We have put this on our list of things to improve in the future, but right now I can't give you any more specifics.
• D

  Wall switch - with Evok
  • devmicha

  2
  0
  Votes
  2
  Posts
  272
  Views

  

  Hello @devmicha, The infrastructure looks like this: IOs -> (SPI) -> ModbusTCP server -> (ModbusTCP) -> Evok -> (REST, WebSockets,...) -> your code The ModbusTCP server (unipitcp service) is polling the complete status of underlying HW via SPI. This happens very quickly, in less than milisecond interval. The Evok aggregates data from the ModbusTCP server and from the owfs (for 1-Wire devices). Your application can poll data from the Evok in multiple ways (REST, WebSockets,...) As you can see, the Evok doesn't communicate with the HW directly. We discussed the possibility of custom software pulling the SPI in this thread: https://forum.unipi.technology/topic/711/reading-spidev I fully understand your concerns about infinite polling data over GET requests. This is generally slow and causes high load on the PLC. The WebSocket offers you a way to subscribe to updates of the IO. You can poll the complete status of the PLC at any time and yet you can listen to updates and act accordingly. Check the documentation and example: https://evok-9.api-docs.io/1.08/ubmjnyexu77wxwo4q/websocket. Martin