This looks like an address problem perhaps, or possibly some other communication setting issue. Did you try to set it up as I have above? At least for testing purposes.
If you did do so then it may be another issue, possibly with a hardware definition; if you can run the following commands while connected to the Neuron and paste the output here we may find the problem.
It might be best to try again with the latest version. The EVOK version cannot be easily found since it's done via GitHub versioning, the easiest via is by checking which installation file/image has been used.
Apologies I did not get back to you earlier, but do try it with the latest version.
Ahh I was assuming you are using Neuron; with the UniPi 1.1 you need to rename the inputs and outputs in the "evok.conf" configuration file; using aliases with the UniPi 1.1 is not supported as the various subdevices are fundamentally different devices. Whereas for Neuron they are, well, subdevices, which are communicated with via Modbus handles. And it is these handles which are renamed with the alias.
I can have a look if we can implement the aliases for UniPi 1.1 as well, but as of right now it's not possible. We should remove the alias-setting option for UniPi 1.1 from the web inteface.
As for the instructions, they will indeed get you the latest Master version.
I think this is caused by internal state caching, as the state update takes some time to propagate and be read back. This is an issue we constantly face with Mervis, but in practice is true for all asynchronous communication with the device. Is it possible that the physical real state is at odds with what you get back from EVOK?
If that is indeed what is happening, then unfortunately there isn't much we could do, besides using a write-back cache for relays. Which potentially could cause desynchronisation issues further down the line.
bohužel phillipsnick/unipi-evok není oficiální verze EVOKu, takže chování nemůžeme zaručit. Nicméně dotaz na DI opravdu vrátí stav daného DI; změny jsou počítané jen ve WebSocket kodu, a nikde jinde nejsou použité.