EVOK sends but is not receiving



  • Hello, I just installed EVOK on UniPi 1.1 and clean Raspbian Stretch.
    1wire is working fine but Relays seem to be working one-way only - web interface for relays is not showing which relays are on or off. But It will switch relays on/off when clicked the switch on webpage...
    Seems like the EVOK is not receiving feedback / some confirmation from relays.

    Can you guide me where/how to start looking for possible cause ?

    Prior to that I had fully working EVOK/Unipi1.1 on Wheezy so hardwarewise all should be ok.

    Attaching start log of evok...

    root@unipi:/etc# systemctl stop evok.service
    root@unipi:/etc# sudo python /opt/evok/evok.py
    [I 190528 20:29:37 evok:1664] Starting using config file /etc/evok.conf
    /opt/evok/config.py:86: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
      self.definitions += [yaml.load(yfile)]
    [I 190528 20:29:37 config:87] YAML Definition loaded: xS10.yaml, type: 3, definition count 0
    [I 190528 20:29:37 config:87] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 1
    [I 190528 20:29:37 config:87] YAML Definition loaded: xS40.yaml, type: 3, definition count 2
    [I 190528 20:29:37 config:87] YAML Definition loaded: xS30.yaml, type: 3, definition count 3
    [I 190528 20:29:37 config:87] YAML Definition loaded: xS50.yaml, type: 3, definition count 4
    [I 190528 20:29:37 config:87] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
    [I 190528 20:29:37 evok:1731] HTTP server listening on port: 8080
    [D 190528 20:29:38 owclient:377] Entering 1wire loop
    [D 190528 20:29:38 owclient:317] New sensor DS18B20 - 281C675F07000040
    [D 190528 20:29:38 owclient:317] New sensor DS18B20 - 28FF9C8C6416038A
    [D 190528 20:29:38 owclient:317] New sensor DS18B20 - 28FF6A09641603E8
    [D 190528 20:29:38 owclient:317] New sensor DS18B20 - 28FF669B6416032F
    [D 190528 20:29:38 owclient:317] New sensor DS18B20 - 28FF1D41631604D1
    [I 190528 20:29:39 web:2064] 101 GET /ws (127.0.0.1) 23.46ms
    [D 190528 20:29:39 evok:158] New WebSocket client connected
    [I 190528 20:29:39 web:2064] 101 GET /ws (127.0.0.1) 5.27ms
    [D 190528 20:29:39 evok:158] New WebSocket client connected
    [I 190528 20:29:40 web:2064] 101 GET /ws (127.0.0.1) 3.78ms
    [D 190528 20:29:40 evok:158] New WebSocket client connected
    [I 190528 20:29:40 web:2064] 101 GET /ws (127.0.0.1) 3.87ms
    [D 190528 20:29:40 evok:158] New WebSocket client connected
    [I 190528 20:29:40 web:2064] 101 GET /ws (::1) 3.96ms
    [D 190528 20:29:40 evok:158] New WebSocket client connected
    [I 190528 20:29:40 web:2064] 101 GET /ws (::1) 4.19ms
    [D 190528 20:29:40 evok:158] New WebSocket client connected
    [I 190528 20:29:40 web:2064] 101 GET /ws (::1) 3.71ms
    [D 190528 20:29:40 evok:158] New WebSocket client connected
    [I 190528 20:29:42 web:2064] 101 GET /ws (127.0.0.1) 6.97ms
    [D 190528 20:29:42 evok:158] New WebSocket client connected```

  • administrators

    @pavelf Hello, it seems to something around the web-socket (used e.g. for relay state readout) connection is going wrong. The connection should be established just once, not several times per second. Can you double-check JavaScript settings in your web browser (must be allowed) and/or try an another one ?