Hello @DAWaller, please share a bit more information. What software do you use? Are you connecting to the Evok? Can you verify, whether the Evok stops responding on the websockets entirely? Thank you and have a nice day, Martin

Hello @pavel_nadr, thank you for helping us discover this bug. The consclusion is, that mailing from MervisRT 2.4.0 doesn't work at the moment at all, no matter what you set in the IDE. Best regards, Martin

Hello @mglowinski, the Evok doesn't have such logic. If the DI doesn't support counters (which does not on Unipi 1.1), the Evok is not able to share this information. This has to be done in your software. Best regards, Martin

Hello @HPC, since Modbus doesn't know anything about data types, it is up to both the master and slave to come up with an exchange format. The registers are 16bit, but the ASCII is only 8bit. The data has to be aligned somehow, or maybe two consecutive characters can be stored into one register? Either way, the goal will be to iterate through the string and convert every item of the string array to byte. Best regards, Martin

Thx for explanation!

To make extension relay module (EMO-R8) working with EVOK below steps needs to be done: Open /etc/evok.conf file Uncomment relays assigned to EMO-R8: Each this line begins with a character ; This character must be removed for all lines related to the configuration for EMO-R8: ; ;Example of 8xRelay extension module addon (EMO-R8) on address 0x21 ; [MCP_2] i2cbus = 1 address = 0x21 [RELAY_9] mcp = 2 pin = 7 [RELAY_10] mcp = 2 pin = 6 [RELAY_11] mcp = 2 pin = 5 [RELAY_12] mcp = 2 pin = 4 [RELAY_13] mcp = 2 pin = 3 [RELAY_14] mcp = 2 pin = 2 [RELAY_15] mcp = 2 pin = 1 [RELAY_16] mcp = 2 pin = 0 Save /etc/evok.conf file Restart evok

Hello, I just followed what you told me yesterday, but that doesn't change anything. In my .csv file, the values ​​that I save its data every second and not every tenth of a second ... For the use that I make of it, it is absolutely necessary that I can obtain more values ​​per second. PICOUL Mathurin

As of now yes @lyngaas, until this gets fixed. Or you can create a function which does the recalculation properly. Best regards, Martin

Hello @romainletendart, thank you for considering Unipi products for your project. We already checked Mender.io and it seems like interesting project, on which we would like to focus in the future. Unfortunately we haven't acquired any hands-on experience, yet. Can you please verify, whether the converting of stock RaspberryPI OS works? It would also help to check the HDMI output during the booting, but that's a bit ill-advised, since removing the HDMI blank typically voids warranty. Best regards, Martin

@Martin-Kudláček Thank you.

Dobrý den @Jan-Toth, toto bohužel není možné. Grafy v HMI pouze vzorkují hodnotu proměnné v čase a zobrazují dle nastavení poslední časový úsek. S pozdravem, Martin Kudláček

Hello @Mathurin, I'm using the said SD card (without the HC) extensively and haven't encouter such behaviour, yet. Please, archive the whole Mervis project folder and send it to support@unipi.technology. I'll try to replicate the issue here. Also include the version of IDE you are using and the version of MervisOS image. Thank you and have a nice day, Martin

Hello @kostastifki, we have experienced such behaviour with Avast antivirus, blocking access to the Mervis project files. Try adding and exception for the MervisIDE. Best regards, Martin Kudlacek

Dobrý den @lukas009, ano, pokud má digitální vstup odpovídající releový nebo digitální výstup. Více o tom se dočtete zde: https://kb.unipi.technology/cs:hw:007-patron:description-of-io:01-description-of-di S pozdravem, Martin Kudláček

Update, Since reinistalling on a new card, all seems well, its been running all weekend, with a few reboots and still ok. I also moved the 1st SD card to another Raspberry Pi to test an LCD display and have issues with that too, which tried another - and all ok - guess i'll blame the SD card for both issues. Cheers for your help.

@Peli Hi Martin Due to relatively large number of inputs (All my switches are hooked to a DI on a Neuron device, the same goes for motion sensor. Then I have each light connected over a relay output or digital output for PWM control. Then there are blinds, each requiring two relay outputs. ...) I have three Neuron devices installed. 2 x L203 and 1 x M203. I am running Neuron OpenSource OS image from May last year I think. In the beginning I did intend to run my HA server on one of the Unipi devices, but have ultimately decided to rather use a separate NUC server that I had laying around. But I don't see any reason why it wouldn't work on the integrated RPi (especially if you plan to use only one device). I also did start with some of the links that you are mentioning. But all of them eventually came to the questions how to lower the latency of getting a signal change state from Unipi device to HA. All solution are designed around polling (MODBUS registers) - and this is already being done by EVOK SW layer running on unipi device, so why introduce another layer on top of that that would do the same. So then it is just a question how to hook to EVOK. With number of standard interfaces EVOK luckily also exposes asynchronous one (websockets) and this is where the performance increase (compared other polling mechanisms) comes handy. I am running HA with Neuron device for a while now and I haven't had any stability issues so far. So yes, I would definitely recommend trying it out. I don't have any Zigbee devices installed but there are standard integrations available in HA so this should work out of the box, if you ask me. Regards Marko

The firmware update from 4.6 to 5.56 made the trick and the /dev/ttyNS0 now works as expected, therefore it can be used as Modbus master as intended. nipi@M203-sn21:~$ sudo /opt/unipi/tools/fwspi --auto Board on /dev/unipispi firmware=4.6 hardware=0.1 (B-1000) (spi 6MHz) New firmware 5.56 for device id=0 fw=4.6 REBOOTING... Board on /dev/unipispi firmware=4.6 hardware=8.1 (E-16Di_U-14Ro) (spi 6MHz) New firmware 5.56 for device id=1 fw=4.6 REBOOTING... thanks @Martin-Kudláček for your help!

Problem with activation solved. I have been using virtualised Windows 7 for Mervis programming (and activation) without any trouble until Mervis 2.4 and it seems there is some problem with SSL with current Mervis version and this outdated OS. Everything else works fine, only the activation process fails. With Windows 10 I was able to finish activation as usual. But there is still problem with MervisDB and Proxy communication. SslHanshakeError persists.