• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Error while changing Analog input State

    Official EVOK API
    2
    4
    1449
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      christophebler last edited by

      Hello

      We are triyng to set up

      We are trying to set up a UniPi Neuron S103 with a Sx50 Extension in mA Mode.
      Setting the state over the configuration webpage does return an error.

      0_1520331332429_Unbenannt.PNG

      So we tried to setup over curl with the same error message.

       curl --request POST   --url http://127.0.0.1:8080/json/analoginput/UART_15_2_01   --header 'content-type: application/json'  
      --data '{"mode":"Current", "range":"20.0"}
      
      {"status": "success", "data": {"errors": "integer out of range for 'H' format code"}}
      

      Do you have a idea how to fix this?

      Christoph

      1 Reply Last reply Reply Quote 0
      • T
        TomasKnot last edited by TomasKnot

        It looks like there's an error in the device definition file parser for the AI on xS50. I have now fixed this on the latest GitHub master, but it may take a while to percolate to all of our image distributions.

        If possible I would recommend using the manual Github installation process; if this isn't an option then you may have luck with replacing all ".py" files in /opt/evok with files from "evok" directory on the Github repository linked above.

        1 Reply Last reply Reply Quote 0
        • C
          christophebler last edited by

          Thank you a lot for your help.
          Reinstalling the latest version vorm github EVOK version worked fine.

          kind regards

          Christoph

          1 Reply Last reply Reply Quote 0
          • T
            TomasKnot last edited by TomasKnot

            Glad you got it working!

            This should now be fixed in our latest opensource image and EVOK release as well.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post