sorry for the websocket issue. Its now running.

the only thing left is the unipi_eprom problem in the boot process of Raspbian

Hi @juntiedt!

It's hard to know the exact reason for the problems you are seeing from the info you provided, but the most likely possibility is that the input you send to the websocket is in Unicode rather than ASCII; testing this produces the same behavior. This may be caused by the library or environment you use, rather than anything you are doing yourself. We can provide Unicode support quite easily, but it might take a few days to filter into the Git repository/release.

Also note that each instance has separate listening channels, though delta events are sent on all. This means that closing the instance after you send a message will prevent you from receiving a reply, and that you need to listen on the same connection as you use to issue the commands.

As for the filter command, it allows you to specify which device delta events you want to listen to. However unless the Unicode issue is solved you will not be able to properly call the command.

Glad you got it working anyhow, I hope this helps.

Thanks, worked out for me

@devmicha Its only possible to control one RO/DO with one DI with the same number using the DirectSwitch function. If you want to do 1Di to more Do/Ro, than you have to make some program which will take care of it. Or also just do it in the cables :)

thanks for the quick response!

I had SPI on in the raspi configuration. I switched it off, rebooted and all is ok. :-)

Thanks a lot :) !! Greeting from Shanghai

@juntiedt Yes, https://github.com/UniPiTechnology/evok#installation-process-for-the-20-evok-version

I found it:

#sending messages def ws_send(CMD, DEV, CIRCUIT, VALUE): ws = websocket.WebSocket() ws.connect(url) ws.send('{"cmd":"%s","dev":"%s","circuit":"%s","value":"%s"}' %(CMD,DEV,CIRCUIT,VALUE)) ws.close()

@jens
Hi
and where is the solution ?

Regards

@roberts_lando I am afraid we won't be able to provide support to every question on slack...

Ok, wrong subforum. Will post on other, concerning mervis.

Tomas,

thank you, putting "-d" in front (bus = -d /dev/ttyUSB0) worked - maybe you could update the evok.conf file with this (as example)

BR

The reason the values were being sent is that they are stored internally in one register per 16 inputs; therefore we needed to implement state tracking to properly distinguish which of the 16 inputs for a given register actually changed.

Apologies for the issues.

The 1-Wire GPIOs have to be included in the configuration file in order to work. There is an example of how it should be done at the bottom of the UniPi 1.1 configuration file ( https://github.com/UniPiTechnology/evok/blob/master/etc/evok-unipi1.1.conf ).

I think this was my post:

https://forum.unipi.technology/topic/278/evok-documentation

right?

Hi Tom,

great ! Problem fixed !

Thanks for your fast answer and support.

Regards.

Olivier.

Thank you Tomas,

Unfortunately I didn't find this topic throug my research. But now I changed the parameter and it works now.

Greets Martin

Hi @devien hi @tomas_hora

Thank you very much for your help. Life could be easy if you ask the right people ;-)
I commented out the class definition but forgot enableing the DS2438 in the code. After fixing that, it seems to work fine.
I'll edit this post if any errors occur in relation to the DS2438.

Thanks again for your help.

Greetings
M4kr

Websocket solved the issue. Thank you