hi all,

i'm trying to get a complete configuration via evok ws/json.
but im kinda confused. doc says:

• 1Wire Device model
• Analog Input state model
• Analog Output state model
• Input state model
• Relay state model
• Register state model
• Neuron state model
• UART state model
• ULED state model
• Watchdog state model
• WiFi state model (if enabled)

but all i get is inputs and relays:

import websocket
import json
import logging

logging.basicConfig()
url = "ws://drhouse:3080/ws"

def on_message(ws, message):
  obj = json.loads(message)
  for single_obj in obj:
    dev = single_obj['dev']
    circuit = single_obj['circuit']
    value = single_obj['value']
    print "Device: " + str(dev) + " / Circuit: " + str(circuit) + " / Value: " + str(value)
  # print json.dumps(obj, indent=2, sort_keys=True)

def on_error(ws, error):
  print error

def on_close(ws):
  print "Connection closed"

def on_open(ws):
  ws.send(json.dumps({"cmd":"all"}))

#receiving messages
ws = websocket.WebSocketApp(url, on_open = on_open, on_message = on_message, on_error = on_error, on_close = on_close)
ws.run_forever()

tja@drHouse:~ $ python testGetAll.py > testGetAll.out
^Ctja@drHouse:~ cat testGetAll.out ut
Device: input / Circuit: UART_1_2_05 / Value: 0
Device: input / Circuit: UART_1_2_18 / Value: 0
Device: input / Circuit: UART_1_2_16 / Value: 0
Device: input / Circuit: 1_01 / Value: 0
Device: input / Circuit: 1_02 / Value: 0
Device: input / Circuit: 1_03 / Value: 0
Device: input / Circuit: 1_04 / Value: 0
Device: input / Circuit: UART_1_2_13 / Value: 0
Device: input / Circuit: UART_1_2_10 / Value: 0
Device: input / Circuit: UART_1_2_11 / Value: 0
Device: input / Circuit: UART_1_2_06 / Value: 0
Device: input / Circuit: UART_1_2_12 / Value: 0
Device: input / Circuit: UART_1_2_15 / Value: 0
Device: input / Circuit: UART_2_3_07 / Value: 0
Device: input / Circuit: UART_2_3_06 / Value: 0
Device: input / Circuit: UART_2_3_05 / Value: 0
Device: input / Circuit: UART_2_3_04 / Value: 0
Device: input / Circuit: UART_2_3_03 / Value: 0
Device: input / Circuit: UART_2_3_02 / Value: 0
Device: input / Circuit: UART_2_3_01 / Value: 0
Device: input / Circuit: UART_2_3_09 / Value: 0
Device: input / Circuit: UART_2_3_08 / Value: 0
Device: input / Circuit: UART_1_2_01 / Value: 0
Device: input / Circuit: UART_1_2_17 / Value: 0
Device: input / Circuit: UART_1_2_03 / Value: 0
Device: input / Circuit: UART_1_2_09 / Value: 0
Device: input / Circuit: UART_1_2_08 / Value: 0
Device: input / Circuit: UART_1_2_02 / Value: 0
Device: input / Circuit: 2_12 / Value: 0
Device: input / Circuit: 2_13 / Value: 0
Device: input / Circuit: 2_10 / Value: 0
Device: input / Circuit: 2_11 / Value: 0
Device: input / Circuit: 2_16 / Value: 0
Device: input / Circuit: UART_1_2_04 / Value: 0
Device: input / Circuit: 2_14 / Value: 0
Device: input / Circuit: 2_15 / Value: 0
Device: input / Circuit: UART_3_4_08 / Value: 0
Device: input / Circuit: UART_1_2_07 / Value: 0
Device: input / Circuit: UART_1_2_14 / Value: 0
Device: input / Circuit: UART_3_4_01 / Value: 0
Device: input / Circuit: UART_3_4_03 / Value: 0
Device: input / Circuit: UART_3_4_02 / Value: 0
Device: input / Circuit: UART_3_4_05 / Value: 0
Device: input / Circuit: UART_3_4_04 / Value: 0
Device: input / Circuit: UART_3_4_07 / Value: 0
Device: input / Circuit: UART_3_4_06 / Value: 0
Device: input / Circuit: UART_2_3_14 / Value: 0
Device: input / Circuit: UART_2_3_15 / Value: 0
Device: input / Circuit: UART_2_3_16 / Value: 0
Device: input / Circuit: UART_2_3_17 / Value: 0
Device: input / Circuit: UART_2_3_10 / Value: 0
Device: input / Circuit: UART_2_3_11 / Value: 0
Device: input / Circuit: UART_2_3_12 / Value: 0
Device: input / Circuit: UART_2_3_13 / Value: 0
Device: input / Circuit: UART_2_3_18 / Value: 0
Device: input / Circuit: 2_05 / Value: 0
Device: input / Circuit: 2_04 / Value: 0
Device: input / Circuit: 2_07 / Value: 0
Device: input / Circuit: 2_06 / Value: 0
Device: input / Circuit: 2_01 / Value: 0
Device: input / Circuit: 2_03 / Value: 0
Device: input / Circuit: 2_02 / Value: 0
Device: input / Circuit: 2_09 / Value: 0
Device: input / Circuit: 2_08 / Value: 0
Device: relay / Circuit: 1_01 / Value: 0
Device: relay / Circuit: 1_02 / Value: 0
Device: relay / Circuit: 1_03 / Value: 0
Device: relay / Circuit: 1_04 / Value: 0
Device: relay / Circuit: UART_3_4_14 / Value: 0
Device: relay / Circuit: UART_3_4_12 / Value: 0
Device: relay / Circuit: UART_3_4_13 / Value: 0
Device: relay / Circuit: UART_3_4_10 / Value: 0
Device: relay / Circuit: UART_3_4_11 / Value: 0
Device: relay / Circuit: 2_12 / Value: 0
Device: relay / Circuit: 2_13 / Value: 0
Device: relay / Circuit: 2_10 / Value: 0
Device: relay / Circuit: 2_11 / Value: 0
Device: relay / Circuit: 2_14 / Value: 0
Device: relay / Circuit: UART_3_4_09 / Value: 0
Device: relay / Circuit: UART_3_4_08 / Value: 0
Device: relay / Circuit: UART_3_4_01 / Value: 0
Device: relay / Circuit: UART_3_4_03 / Value: 0
Device: relay / Circuit: UART_3_4_02 / Value: 0
Device: relay / Circuit: UART_3_4_05 / Value: 0
Device: relay / Circuit: UART_3_4_04 / Value: 0
Device: relay / Circuit: UART_3_4_07 / Value: 0
Device: relay / Circuit: UART_3_4_06 / Value: 0
Device: relay / Circuit: 2_05 / Value: 0
Device: relay / Circuit: 2_04 / Value: 0
Device: relay / Circuit: 2_07 / Value: 0
Device: relay / Circuit: 2_06 / Value: 0
Device: relay / Circuit: 2_01 / Value: 0
Device: relay / Circuit: 2_03 / Value: 0
Device: relay / Circuit: 2_02 / Value: 0
Device: relay / Circuit: 2_09 / Value: 0
Device: relay / Circuit: 2_08 / Value: 0
Device: ai / Circuit: 1_01 / Value: 0.0619234416178
Device: ao / Circuit: 1_01 / Value: 0.0023
Device: wd / Circuit: 1_01 / Value: 0
Device: wd / Circuit: 1_01 / Value: 0

Connection closed

Re: Sysfs interface support for extension modules

hi martin,

is this feature planned or will we have to use evok if we want to access the extension modules ?

i'm asking as a colleague of mine (michael hacker) wrote "unipi-mqtt-api" a sysfs-based implementation of a mqtt client (with home-assistant support) which is a lot faster then my own evok-based script.

as i'm having 3 extensions on my production neuron i have to stay on the evok-based solution atm but it would be nice to have sysfs support for the extensions ... even if they might be not as fast as the built-in module.

tia, wbr, tja...

@tomasknot
another question tomas:
if i understand correctly the extensions or the daughterboards == input banks have their own firmware ... is there a way to check the firmware version and correctness of all the parts on a running neuron (eg without shutting down and/or have to use some windows machine etc etc) ?

tia,tja...

@tomasknot said in evok still not stable, inputs will not cause events after some time, restart required:

I really am not sure how this happens. I think it may be due to system load, but since as you say OpenHab is not on the system I am not quite sure why this is. Could you please run

ps -fax

when the system hangs, and post the output here? It could show us the system load in that case.

i took the opportunity to make a walk through the house checking all the switches and sadly (from a debugging point of view ofc :D ) all switches work atm.
i will report any new problems and attach evok's logs, neurontcp's status and ps fax asap.

in the meantime, thx for your efforts to help me. i would really like to put this bug ?!? to rest.

tia,tja...

@tomasknot
the inputs connect to plain wallmounted switches.
the length of the impulse is determined by the length of the switch press - and even if i press for half a minute evok in this "error" state will not recognize this/these input(s) any more.

as todays error happened i fetched my notebook to check for evok-webapp and it wouldnt show the keypress either.
as it happends it was the input for the light in the technics-room where the cabinet with the neuron is located so i could look for the led the very moment i could check evok-webapp so i can be sure that the input got signal (the led lights) and therefore the switch is not the cause.

i always use evok-webapp to check the error to rule out openhab and my bridge script.

openhab is not in the game as i relocated openhab plus my bridge script to another rpi3 as evok plus openhab on the neuron would cause too much delay on the inputs.
since i put openhab on another machine and used scan_frequency = 20 at least the switches would be much more usable.

@tomas_hora
hi tomas,

as i said evok.log shows nothing.
here's the tail part of the start on the morning till around half past 8 as i saw that one switch/input would not do anymore and i restarted evok:

2018-06-22 07:03:06,564 - evok - INFO - Alias loaded: <neuron.Relay object at 0x758d5f90> al_lights_bedroom
2018-06-22 07:03:06,972 - evok - INFO - Alias loaded: <neuron.Relay object at 0x75918650> al_lights_kitchen
2018-06-22 07:03:06,973 - evok - INFO - Alias loaded: <neuron.Relay object at 0x758d5f90> al_lights_bedroom
2018-06-22 07:03:07,054 - evok - INFO - Alias loaded: <neuron.Relay object at 0x75918650> al_lights_kitchen
2018-06-22 07:03:07,054 - evok - INFO - Alias loaded: <neuron.Relay object at 0x758d5f90> al_lights_bedroom
2018-06-22 07:03:07,102 - evok - INFO - Alias loaded: <neuron.Relay object at 0x75918650> al_lights_kitchen
2018-06-22 07:03:07,102 - evok - INFO - Alias loaded: <neuron.Relay object at 0x758d5f90> al_lights_bedroom
2018-06-22 08:41:42,130 - evok - INFO - Shutting down
2018-06-22 08:41:44,272 - evok - INFO - Starting using config file /etc/evok.conf

i will check neurontcp next time and report back.

tia,tja...

yesterday at last i had enough time to look into this topic again.

the situation for about 8 weeks is that my neuron 203 with 2 xs30 and one xs40 using evok is not stable for daily usage without restarting evok.service hourly via cron and occasionally manual restarting neurontcp.service.
even then sometimes some inputs would not register and send events neither to evok-webapp nor to my openhab2 bridging script.
which inputs are affected is completely random or at least i see no pattern.
sometimes the affected inputs are on the 203 itself, sometimes on the extensions.
sometimes all inputs on a bank are affected, sometimes just 2 or 4.
the hardware itself works as i see the control leds on the neuron & extensions reacting to the inputs.
ofc my WAF (women acceptance factor) is low as she sometimes has to use her phone to switch on the bathroom lights in the morning routine ... :/

yesterday i made a complete new image with a fresh install of evok v.2.0.7 and didnt reimplement the cron-based restarts yet. i'd hoped that the situation software-wise would have improved.
at least the switches/inputs we used worked for half a day but today some inputs wouldnt work again. again restarting evok would fix the situation.

i see no hints for the cause of evoks behavior in any logfile whatsoever.
what should i do to debug ?

root@drHouse:~# cat /etc/evok.conf
#!!! Do not use '#' for comments !!!

[MAIN]
config_version = 2.5
use_schema_verification = False
log_level = DEBUG
log_file = /var/log/evok.log
port = 3180
webhook_enabled = False
webhook_address = http://127.0.0.1:80
webhook_device_mask = ["input","wd"]
webhook_complex_events = False
wifi_control_enabled = False
soap_server_enabled = False
soap_server_port = 8081

[NEURON_1]
global_id = 1
allow_register_access = False
scan_frequency = 20
scan_enabled = True

[EXTENSION_1]
global_id = 2
device_name = xS30
modbus_uart_port = /dev/extcomm/0/0
address = 1
scan_frequency = 20

[EXTENSION_2]
global_id = 3
device_name = xS30
modbus_uart_port = /dev/extcomm/0/0
address = 2
scan_frequency = 20

[EXTENSION_3]
global_id = 4
device_name = xS40
modbus_uart_port = /dev/extcomm/0/0
address = 3
scan_frequency = 20

hi tomas,

2.05a seems to have fixed this error too - the extensions are fully populated and the send events now (the old version didnt send events too as i had to discover).

thx for helping,
wbr,tja...

hi tomas,

the new version (2.05a) seems to be fixed regarding that strange message.

thx for helping,
wbr,tja...

thx tomas !

is there some safe upgrade procedure for evok or should i just install over the old version ?

tia,tja...

hi all again,

my build with L203, 2x xS30, 1x xS40 communicates now without any trouble so far.
today i started to wire all the rest of the buttons in the house and i noticed that the DIs of the xS30 go from 01 to 18 but 19 to 24 are missing from evoks webapp and are not reported via webservices either (output sorted for convenience):

Device: input / Circuit: 1_01 / Value: 0
Device: input / Circuit: 1_02 / Value: 0
Device: input / Circuit: 1_03 / Value: 0
Device: input / Circuit: 1_04 / Value: 0
Device: input / Circuit: 2_01 / Value: 0
Device: input / Circuit: 2_02 / Value: 0
Device: input / Circuit: 2_03 / Value: 0
Device: input / Circuit: 2_04 / Value: 0
Device: input / Circuit: 2_05 / Value: 0
Device: input / Circuit: 2_06 / Value: 0
Device: input / Circuit: 2_07 / Value: 0
Device: input / Circuit: 2_08 / Value: 0
Device: input / Circuit: 2_09 / Value: 0
Device: input / Circuit: 2_10 / Value: 0
Device: input / Circuit: 2_11 / Value: 0
Device: input / Circuit: 2_12 / Value: 0
Device: input / Circuit: 2_13 / Value: 0
Device: input / Circuit: 2_14 / Value: 0
Device: input / Circuit: 2_15 / Value: 0
Device: input / Circuit: 2_16 / Value: 0
Device: input / Circuit: 3_01 / Value: 0
Device: input / Circuit: 3_02 / Value: 0
Device: input / Circuit: 3_03 / Value: 0
Device: input / Circuit: 3_04 / Value: 0
Device: input / Circuit: 3_05 / Value: 0
Device: input / Circuit: 3_06 / Value: 0
Device: input / Circuit: 3_07 / Value: 0
Device: input / Circuit: 3_08 / Value: 0
Device: input / Circuit: 3_09 / Value: 0
Device: input / Circuit: 3_10 / Value: 0
Device: input / Circuit: 3_11 / Value: 0
Device: input / Circuit: 3_12 / Value: 0
Device: input / Circuit: 3_13 / Value: 0
Device: input / Circuit: 3_14 / Value: 0
Device: input / Circuit: 3_15 / Value: 0
Device: input / Circuit: 3_16 / Value: 0
Device: input / Circuit: UART_1_2_01 / Value: 0
Device: input / Circuit: UART_1_2_02 / Value: 0
Device: input / Circuit: UART_1_2_03 / Value: 0
Device: input / Circuit: UART_1_2_04 / Value: 0
Device: input / Circuit: UART_1_2_05 / Value: 0
Device: input / Circuit: UART_1_2_06 / Value: 0
Device: input / Circuit: UART_1_2_07 / Value: 0
Device: input / Circuit: UART_1_2_08 / Value: 0
Device: input / Circuit: UART_1_2_09 / Value: 0
Device: input / Circuit: UART_1_2_10 / Value: 0
Device: input / Circuit: UART_1_2_11 / Value: 0
Device: input / Circuit: UART_1_2_12 / Value: 0
Device: input / Circuit: UART_1_2_13 / Value: 0
Device: input / Circuit: UART_1_2_14 / Value: 0
Device: input / Circuit: UART_1_2_15 / Value: 0
Device: input / Circuit: UART_1_2_16 / Value: 0
Device: input / Circuit: UART_1_2_17 / Value: 0
Device: input / Circuit: UART_1_2_18 / Value: 0
Device: input / Circuit: UART_2_3_01 / Value: 0
Device: input / Circuit: UART_2_3_02 / Value: 0
Device: input / Circuit: UART_2_3_03 / Value: 0
Device: input / Circuit: UART_2_3_04 / Value: 0
Device: input / Circuit: UART_2_3_05 / Value: 0
Device: input / Circuit: UART_2_3_06 / Value: 0
Device: input / Circuit: UART_2_3_07 / Value: 0
Device: input / Circuit: UART_2_3_08 / Value: 0
Device: input / Circuit: UART_2_3_09 / Value: 0
Device: input / Circuit: UART_2_3_10 / Value: 0
Device: input / Circuit: UART_2_3_11 / Value: 0
Device: input / Circuit: UART_2_3_12 / Value: 0
Device: input / Circuit: UART_2_3_13 / Value: 0
Device: input / Circuit: UART_2_3_14 / Value: 0
Device: input / Circuit: UART_2_3_15 / Value: 0
Device: input / Circuit: UART_2_3_16 / Value: 0
Device: input / Circuit: UART_2_3_17 / Value: 0
Device: input / Circuit: UART_2_3_18 / Value: 0
Device: input / Circuit: UART_3_4_01 / Value: 0
Device: input / Circuit: UART_3_4_02 / Value: 0
Device: input / Circuit: UART_3_4_03 / Value: 0
Device: input / Circuit: UART_3_4_04 / Value: 0
Device: input / Circuit: UART_3_4_05 / Value: 0
Device: input / Circuit: UART_3_4_06 / Value: 0
Device: input / Circuit: UART_3_4_07 / Value: 0
Device: input / Circuit: UART_3_4_08 / Value: 0

can someone enlighten me about this ?

tia,tja...