Hi @kepi
you can try the latest Opensource OS or Node-RED OS image for the Axon series.
Then install (or update) the unipi-firmware6 package and try to update the firmware.
If that doesn't help, you can send the controller to the Unipi service center for diagnostics.
Best regards,
Antonin, Unipi
Hi @iVar,
All images must be in the Resources directory, otherwise they are not available, please see screenshot.
Best regards,
Antonín Všetula - Unipi technician
Hi @t-kavan,
We have already encountered this, unfortunately this meter does not wait for the prescribed time and responds too quickly, so that the RS485 (transmit/receive) state in the controller does not have enough time to change.
The RS485 behaviour was modified in later versions of the debian packages. With the current OS image the PRO380-MB meter are already working.
Best regards,
Antonín Všetula - Unipi technician
Hi @lukas009
Thank you for your feedback, I have already replaced the old links with new ones. During the day we will adjust the look and add more information to the page.
The documentation department misunderstood the information and only processed the pages for Base OS, not Node-RED OS.
Best regards,
Antonin, Unipi team
Hi @domguard,
The mentioned problems should not be related to EVOK at all. It's not clear from your description what kind of controller you have or what you actually need. Do you need to connect to an existing WiFi, or do you want to create a WiFi access point from the controller?
But EVOK works normally, right?
Best regards,
Antonin, Unipi team
Hello PEPITO82,
The RPi CM4 is currently not an officially supported platform. However, according to my information, should be mostly compatible with "standard" RPi.
One option may be to use the RaspberryPi OS image and install the necessary components: EVOK, Node-RED.
If you also want so-called Unipi nodes for communication with inputs and outputs, which are available in our Node-RED OS image, just add a suitable module from the palette to Node-RED.
Best regards,
Antonin
Hi everyone,
In these cases, this guide can help: https://kb.unipi.technology/en:sw:01-mervis:automatic-restart-of-1-wire-hidden
Unfortunately, if you have improperly processed cabling, or if you have a large number of sensors connected to this bus, you cannot achieve the desired stability, because the 1-Wire bus is very sensitive to interference.
In this case, I recommend checking the wiring to make sure you have all unused wires and the cable shield connected to the ground terminal. Next, check the length of the bus and the number of sensors on the bus.
An alternative to this connection is also the connection of sensors via Extension xG18, which has 8 separate 1W channels, each reserved for one sensor. Perhaps the only disadvantage of this module is that it is possible to connect only sensors DS18b20 and supporting parasitic power.
Finally, I also recommend reading this article about 1-Wire: https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden
Best regards,
Antonin, Unipi
Hi everyone,
Currently this is possible by flashing Mervis OS and then installing Node-RED following the standard installation instructions: https://nodered.org/docs/getting-started/raspberrypi
However, this solution is not tested and we cannot guarantee that the Mervis RT will behave correctly if other such demanding SW is running on the controller.
Best regards,
Antonin, Unipi
Hi @Vesa-Kauppinen,
try apt update && apt upgrade again.
We made some adjustments due to the new Unipi Iris HW, but this should work fine now.
Best regards,
Antonin, Unipi
Hi @lukec,
You can try the current Node-RED image, which is available at this link: https://kb.unipi.technology/en:hw:007-patron:download-image:02-nodered
Best regards,
Antonin, Unipi
Hi @JakubSzlaur
The documentation is really old, but this command looks functional. As recently as last year, someone used it for an update (link to the Node-RED forum), but I didn't test it.
We will also soon release a new Node-RED OS with the current Node-RED v3. Which is also a certain possibility to update.
Best regards,
Antonin, Unipi
Hi @ArnieX,
Thank you for your post.
This is a typical error when setting up communication with INEPRO/KLEFR electricity meters, and it is really necessary to be careful when setting up other devices (modbus tables).
Best regards,
Antonin, Unipi
Dobrý den,
tyto moduly jsou z prvopočátků vývoje a bohužel se k nim nedochovaly potřebné manuály. Pokud však došlo ke zpomalení komunikace po aktualizaci na novější verzi, hledal bych různé intervaly komunikace (např. u komunikačních skupin) a nastavil je na 0ms.
Případně zkuste připojit modul 1W-4R-4DI přímo na 1-Wire sběrnici zařízení Unipi 1.1.
Přeji hezký den,
Antonín z Unipi
Hi @robinr1,
I'm glad you managed to solve the problem (find the cause).
Regarding the FW update, I recommend reading this article.
Currently, we have also released a new package unipi-firmware6, which already contains the so-called rescue firmware, which ensures that the subsequent upload of new FW is already much safer.
When updating to FW 6, follow the recommendations using the arguments P and U:
/opt/unipi/tools/fwspi -i {0,1,2} -P -U
Best regards,
Antonin, Unipi
Hi @Petter,
First, you need to install and enable the unipi-lte package as follows:
sudo su
apt-get update
apt-get install unipi-lte
systemctl enable unipi-lte
reboot
Configuration is then possible in the /etc/unipi/lte.conf file, e.g. by the program MidnightCommander:
mc -e /etc/unipi/lte.conf
Best regards,
Antonin, Unipi
Hi everyone,
In the current version of Mervis OS 2.4.2.4, writes to the card already occur at least, according to the set interval for storing retain variables.
For a similar reason, the history is newly stored in RAM (data is lost after the power is disconnected or restarted), which does not matter in combination with the cloud-based Mervis DB.
If you disable writes to the internal storage (SD card), there are two possibilities of what can happen (depending on how you disable the writes):
In general, I recommend purchasing an SLC card with a longer lifespan and resistance to random power outages, etc., for the operation of the controller.
You can read more about this issue in this article.
Best regards,
Antonin, Unipi
Hi @udokra,
If you already save the variables in the history (this guide), you can display them in the graph in two ways:
Best regards,
Antonin, Unipi