Hello @Balardo, you are right - there was a bug in schema validation for /json/all endpoint. It should be fixed in the next release. According to the direct Modbus unit register access - you can use e.g. http://<your IP>/json/unit_register/UART_15_2_42 to get the ambient_light register: {"status": "success", "data": {"name": "ambient_light", "value": 122.51519775390625, "glob_dev_id": 2, "dev": "unit_register", "circuit": "UART_15_2_42", "unit": "lux"}} Register values has been also added to the web control panel: You can test it by install the test version: sudo su apt update && apt install evok=2.3.3.test.20200923165635*

Solved by: The pre K value was set to 0.1 as described in the documentation. I set it back to 1. With one every measurement is working properly. Question: Could you explain in more detail how the pre and post K and Q values are working. I'm a bit confused. Obviously its just a matter of scaling since for Pt1000 the pre K factor need to be set to 0.1. So for Pt500 the pre K factor should be set to 0.5? Am I correct?

Hello @rtatibouet, the RS485 and RS232 are completely different buses. The RS485 is differential and doesn't need the GND, since the logic levels are based on the voltage difference between A and B terminal The RS232 is not differential and the TX / RX logic levels are based on the voltages between TX and GND and RX and GND. Best regards, Martin

Hello @Stoeffel, please try to uncomment following lines in the evok.conf within the xG18 section: allow_register_access scan_frequency scan_enabled In case of no success, you can try to "hardcode" the serial line parameters (baud rate, parity, stop_bits) in the config file (by uncommenting appropriate lines).

I am using normal SD Cards, SandDisk and Kingston .... I already ordered two pieces of the recommended cards. Thank you for your advice.

Hello @sacha, all Axon PLCs should be shipped with Debian 10 Buster inside. Of course, you can simply upgrade any older unit to the latest OS (all current OS Images are based on the Buster). Images can be downloaded from our KB. A tutorial of how to flash the image (same for all Axon OS Images).

Relays on Unipi 1 are ware wired via I2C gpio expansion so you will needsomething a bit more complicated. There are many options: linux like https://github.com/Peekayy/mcp230xx Python using already made library like https://github.com/adafruit/Adafruit_CircuitPython_MCP230xx C/C++ or anything else the same way just like Python ...

Hello @daminou53 , what OS image are you using? Have you done any changes in network configuration (e.g. /etc/network/interfaces files)? On the following lines, the connection is successfully initialized (probably with very poor signal quality) but immediately, the LTE service is restarted. 2019-02-14 11:31:58,599 - DEBUG - WAN IP 10.34.177.115, Private IP 10.21.8.1; NON-CONFLICT 2019-02-14 11:31:58,600 - INFO - WAN IP ADDRESS: 10.34.177.115 INTERFACE IP ADDRESS: 10.21.8.1 2019-02-14 11:31:58,602 - DEBUG - RSSI: 19 sigqual: 6 net-type: 7 2019-02-14 11:32:00,023 - INFO - unipi-lte version 0.18 from 2019-02-14 11:11:00.068002 - Logging started.. Are you able to provide remote access to the unit? In the meantime, you can try to install the new beta version: sudo apt install unipi-lte=0.19*

Hi @martin_triska, Yes, that sums up the situation well, so I'll write to support@unipi.technology for replacement request. Many thanks, Pascal

Hello @FabioIT, we have updated the tutorial on measuring the resistance: https://kb.unipi.technology/en:automation:02-glossary:analog-inputs-hidden#measuring_resistance

You are absolutely correct sir! Thanks a lot for your help - now it works like a charm. I've used Neuron's RS485 for communication with xS11 and separate USB dongle with CH340C chip (a bargain really, $2.7 from CZ shop) for communication with PRO1 energy meter through the same Node-RED setup getting data from /dev/ttyUSB0. It's a pity that I cannot edit my previous post ^^ - feel free to edit it with a big warning that you cannot combine multiple processes on one serial (which is absolutely logical, but for us: HW newbies not obvious).

For the record - @r3sist discovered that the corrupted SD card has been causing the delays. Everything in the program has been configured correctly.

one important thing at the end: as soon as you apply a filter the received msg.payload from websocket comes in an array. this means: before the applied filter you could your device with msg.payload.dev with applied filter you must read the device as msg.payload[0].dev !!!

Hello @clueless, the 1-Wire addresses are uploaded to the PLC with Deploy od the solution.

thanks for your information. I have connected a 4 wire cable very close to the three wire sensor and connected the data line to 2 wires in order to use the hub. At the moment it works.

Can you check the statistics registers 2000+ / 2100+?

Hello @juntiedt, the Unipi 1.1 doesn't have RS485 interface, so you need to use some RS485/USB converter. The latest Evok has support for xG18, you just need to set it in the /etc/evok.conf as a normal Unipi Extension.

Hello @juntiedt, this sensor comes in the 3 wire connection + shielding. You can connect it to the 1-Wire hub, ideally as a last sensor. Please consult the 1-Wire hub pinout https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden

Update: I have install it in the fusebox now and there is diffrent powersource. And now it is just Run 3 blinking. And cant get the modul 3 to work. Before works all of them after a reboot but stops and blinks after like 5 min.

The controller was not selected. It's working now. Thank you for pointing that out.