No inputs or outputs accessible



  • I´m using UniPi 1.1 and it is impossible to comunicate with.

    I can run the web interface, but it shows no inputs or outputs (except the input 1 and analog output 1) :
    0_1541438231444_Obrázok1 – kópia – kópia (2).png
    0_1541438331581_Obrázok1 – kópia (2) – kópia.png

    the command sudo /opt/evok/evok.py gives the following output:

    [I 181105 17:57:34 evok:1652] Starting using config file /etc/evok.conf
    [I 181105 17:57:34 config:87] YAML Definition loaded: xS30.yaml, type: 3, definition count 0
    [I 181105 17:57:34 config:87] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 1
    [I 181105 17:57:34 config:87] YAML Definition loaded: xS50.yaml, type: 3, definition count 2
    [I 181105 17:57:34 config:87] YAML Definition loaded: xS40.yaml, type: 3, definition count 3
    [I 181105 17:57:34 config:87] YAML Definition loaded: xS10.yaml, type: 3, definition count 4
    [I 181105 17:57:34 config:87] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
    [I 181105 17:57:34 evok:1719] HTTP server listening on port: 8080
    [E 181105 17:57:34 config:360] Error in config section MCP_1 - 'I2C write failed'
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 246, in create_devices
            mcp = unipig.UnipiMcp(bus, circuit, address=address, dev_id=0)
          File "/opt/evok/unipig.py", line 91, in __init__
            i2cbus.i2c_write_byte_data(self.i2c, MCP23008_IODIR, 0x00)  # all output !
          File "/usr/local/lib/python2.7/dist-packages/pigpio.py", line 2435, in i2c_write_byte_data
            self.sl, _PI_CMD_I2CWB, handle, reg, 4, extents))
          File "/usr/local/lib/python2.7/dist-packages/pigpio.py", line 835, in _u2i
            raise error(error_text(v))
        error: 'I2C write failed'
    [E 181105 17:57:35 config:360] Error in config section RELAY_1 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_2 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_3 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_4 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_5 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_6 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_7 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    [E 181105 17:57:35 config:360] Error in config section RELAY_8 - Invalid device circuit number 1
        Traceback (most recent call last):
          File "/opt/evok/config.py", line 251, in create_devices
            mcp = Devices.by_int(MCP, mcp)
          File "/opt/evok/devices.py", line 67, in by_int
            raise Exception('Invalid device circuit number %s' % str(circuit))
        Exception: Invalid device circuit number 1
    Process OwBusDriver-1:
    Traceback (most recent call last):
      File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
        self.run()
      File "/opt/evok/owclient.py", line 376, in run
        ow.init(self.bus)
      File "/usr/lib/python2.7/dist-packages/ow/__init__.py", line 224, in init
        raise exNoController
    exNoController
    [I 181105 17:57:36 web:2064] 101 GET /ws (::1) 5.33ms
    [D 181105 17:57:36 evok:158] New WebSocket client connected
    [I 181105 17:57:37 web:2064] 200 GET /rest/all (::1) 10.10ms
    
    

    this appears to be a problem with I2C, so i tried running sudo i2cdetect -y 1 but I didn ´t find any I2C communication :

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    70: -- -- -- -- -- -- -- --          
    

    Can anyone please tell me what may be the problem?
    Thank you


  • administrators

    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