@lyngaas Hello, Unipi officially does not support this USB stick. Please check for supported convertors.

If you want to use different type you need to install appropriate drivers to our open OS.

Hi @roberts_lando, I have the exact same case , an inverter with three pins (+/-/GND) , did you found any solution ? I have a Neuron, it has also only two pins.
But it has a "END" switch next to the RS485 connector
thanks

Dobrý den @ptirala,

můžete nám prosím poslat na email ([email protected]) schéma zapojení, archiv projektu a případně i fotky?

Zdeněk z Unipi

@knebb, I have been successful with my Axon device couple months ago.

Here is my /etc/apt/sources.list.d/unipi.list:

deb https://repo.unipi.technology/debian bullseye main

These are the steps I followed:

sudo apt update sudo apt upgrade sudo apt full-upgrade

I didn't remove any packages after full-upgrade and simply rebooted with a backup in place. After restart, I removed all obsolete packages but those which had unipi or axon in name (see later).

Currently, I'm still using the kernel from Buster because the kernel packages in Bullseye appear to be broken. If I understand correctly, we should be able to use unipi-kernel-modules-dkms with the normal Debian kernel. Unfortunately, it currently has broken dependencies, namely the unavailable unipi-kernel-headers and unipi-os-configurator-data.

Here is the list of obsolete Buster packages I have left on hold:

unipi-kernel-modules unipi-common axon-kernel-headers axon-kernel-image

Since I don't currently need a new kernel, I'm not in a rush to resolve this. However, it would be great to receive an official update.

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

@lukas009 ... all in the right time ;)

@arolli Hello Antonio,
depends on what the project is. Neuron is cheaper and more suitable for smart home/home automation projects. Patron line is more expensive, but is built to full industrial standards. As for longevity I definitely recommend Patron, in case you decide to use Neuron longevity mainly depends on used SD card, check our eshop for SLC uSD cards, they help a lot.

@Beny44
Edit: TČ používá PLC Carel, kde bych se měl přes BMS2 linku propojit s Gate. Bohužel jde komunikace jen z Gate, zpět nic.
Nastavení jako rychlost a adresu zařízení mám dobře.
Našel jsem že i Domat má integraci Carla, viz. https://www.domat-int.com/cs/integrace-carel-modbus

@martin_triska Thanks a lot!

I had to do some debugging due to incompatible base source deviceTree (which was ultimately resolved by patching the compatible directives and a bit of merging together), but your response helped a ton!

It works like a charm, so again, thanks! We plan to open source parts of the project in the future as well (along with a stable release) ... so hopefully it will help someone else too :)

Sometimes writing stuff down helps with thinking.

The error message is confusing, but I had forgotten to update the vlistfile after making changes to the variable definitions in Mervis.

It now works with integers. Seems to still have problems with strings though, is this a limitation?

OK I have sorted the partition issue thanks to UniPi tech support: manually resizing the SD card partition using gparted on another Linux system.

However I'm still looking for a guide to the 'official' way to upgrade nodeJS, npm and NodeRed on a UniPi Neuron. I'd like nodeJS 18 and Node-RED 3 if possible. The only documentation I came across regarded nodeJS 14 as 'new'!

@marko2276 ,
After using your implementation for more than 2 years without flaw, both of my Unipi V1.1 systems (one with my whole Homeassistant installation) "died" from repeating powerfailures, due to grid loss and active but non functional emergency power. Both USB-sticks were damaged with backups on the same stick. Really bad luck, I should have known better.

This forced me to a new installation using your altered code with unique_ids.
Unfortunately, this code does not work properly having more than one Unipi-device with the same configuration(s).
In this case the "unique_ids" will be identical for e.g. lights or switches on Unipi unit 1 and Unipi unit 2!
Thus, Homeassistant isn't able to determine the targets anymore and will disable them.

It took me some time effort to find this issue.

As I'm using UniPi V1.1 devices, this migth only appear within my setup, but I'm pretty sure, this error will also occure on other unipi devices.

I managed to get around this issue by extending the unique_id property definition(s) like this:

code_text @property def unique_id(self): """Return the unique ID of this light entity.""" return f"{self._device}_{self._port}_at_{self._unipi_hub._name}"

Hope, this will help others with the same issue.
Cheers, Joerg

@AVsetula I'm aware of this guide and about the OW_off_1 switch. The problem is, that it does not solve the problem in my case.
As I wrote before I tried to set OW_off_1 to true and then back to false, but all the temperature sensors kept showing 0 ˚C.
I haven't found any software way how to "restart" the 1W to working state. The only thing which works is restarting whole Neuron by cutting off the power.

If you have any other ideas, I'll appreciate them.

Nobody who knows how to resolve this matter?

It doesn't seem to be possible to get any value in the HMI Web. I always get no values and the values.cgi responds with {"ver":1.0,"code":"error","msg":"No variables from request available. Check device parameters and availability."}

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