• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. oversc0re
    3. Topics
    O
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 10
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by oversc0re

    • O

      Output turning off after a few seconds
      Neuron Series • • oversc0re

      4
      0
      Votes
      4
      Posts
      961
      Views

      C

      Hello @oversc0re,
      it is very likely as you say, inrush current burnt the relay, you may use external one or some protection to prevent this in future.

    • O

      Unipi/evok input change detection lagging
      Official API - Evok • • oversc0re

      3
      0
      Votes
      3
      Posts
      2119
      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

    • O

      Setting filter corrupts the websocket message
      Official API - Evok • • oversc0re

      5
      0
      Votes
      5
      Posts
      2698
      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

    • O

      Websocket connection dropping
      Official API - Evok • • oversc0re

      13
      0
      Votes
      13
      Posts
      5481
      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.