Integration of modules with RS485 interface in Home Assistant, Blynk, openHAB systems

Welcome.

I'm starting this thread because one of the electrode users made me aware that there are ready-made systems and I don't need to create everything from scratch. This person mentioned solutions such as Home Assistant, Blynk, openHAB. I would like some advice on what to choose? What should I be interested in? I would like to build a home automation system based not only on some ready-made modules, but I would also like to use my own projects. The only catch is that most of the modules I am designing would have to communicate with the server via RS485. And I would like to set up the server itself for any of the above systems at home. Will any of the systems allow me to integrate with modules with an RS485 interface? Do they have to be WiFi modules like the ESP8266?

I would be very grateful for any advice .

Michal_212 wrote:

The only catch is that most of the modules I design would have to communicate with the server via RS485.

.
For this reason I would consider Node-Red. You can easily create your own communication protocols and automations. All the "intelligence" stored in it, you can easily show in one of these systems (e.g. using MQTT) , using it mainly as a "frontend". You can also use the panel of NR itself.
HA and OH are comparable, but it seems to me that HA is easier to learn (choice on a "what suits someone better" basis). I don't know about the others, but in HA you can Node-Red and MQTT can easily be run as an add-on.
In this configuration and in this way, I was able to attach several devices that there was no ready integration (e.g. gas boiler, video intercom , weather station...), as well as easily change my mind and choose another system.

In that case, I will opt for Home Assistant .
So ideally I would also use Node-RED for this? But then build the logic of the whole thing on Node-RED, and only the interface on HA? Do I use Node-RED for the software logic to operate my modules, and HA for the finished devices, such as air conditioning etc.?
Somehow after the weekend I'll put HA and Node-RED on Linux and play around with it a bit to see what it's all about .

I'm no expert on HA installation, I've only done it twice .
If you are going in that direction then look for a ready-made image for your hardware, as far as I can tell installing HA on Linux is no longer supported. HA has its own Hassio system. To avoid the hassle of installation and configuration, start with HA.
Then install the NR add-on and MQTT in HA itself - you will avoid many problems (which is important for a beginner).

Michal_212 wrote:

Is it best if I also use Node-RED for this? But then build the logic of the whole thing on Node-RED, and only the interface on HA?

.
... both yes and no - it is sometimes not worth breaking down an open door and sometimes it is better to add a ready-made intergration in HA.
In NR integrate only devices without HA support.
What hardware do you want to install this on?

As far as NR is concerned, it can completely replace HA because there is the possibility of installing a dashboard.
The fact is that NR works very nicely with HA. As for installing HA on Linux, there are two schools:
Installing Proxmox and then a virtual HassOS or installing docker and then installing containers with hassOS and additional ones.
I prefer the second method, as it is a waste of RAM wasted on virtual systems.

xury wrote:

because I pity the RAM wasted on virtual systems.

.
It's when you declare a certain size of RAM in the VM that you permanently lose it, even if the machine doesn't use it?
I have a VM on a Qnap NAS, on average HA shows 20% RAM occupancy - do you think I can safely reduce the allocation?

This is not what I meant. In docker the "guest system" uses host resources to the maximum extent it can e.g. kernel, libraries etc.
As I only have 8GB of RAM on my NUC and a lot of services, I prefer docker.
If everything works fine for you then there is no point in rearranging anything. RAM not used is RAM wasted.
I save because I have Domoticz, HA, NR, Plex, Grafana, influx-db and many more less important ones on one machine.

xury wrote:

If everything is working fine at your place then there is no point in rearranging anything.

That's basically it, but it wouldn't hurt to know more.
Thanks

starob wrote:

What hardware do you want to install this on?

.

I have a 3.5" minicomputer with a dual-core Intel processor, 4GB RAM and a 32GB SSD, so I'd like to put it on it.
Do you want me to put Linux on it? Because I guess you have to run docker on Linux anyway? Is there a guide to installing the whole thing?

Because of the ability to easily create snapshots (easy after a failure to restore from a backup) I would normally recommend Proxmox and HA on it, but a little short on RAM and SSD.
https://hejdom.pl/blog/22-home-assistant/383-...-assistant-supervisor-instalacja-proxmox.html
Analyse w/ https://www.home-assistant.io/installation/ for requirements.

starob wrote:

this installation on Linux already HA is not supported

.
However, they have changed their mind and it is possible on debian [sic!]
https://hejdom.pl/blog/22-home-assistant/309-...-assistant-debian-supervisor-instalation.html
For now, bet on what you have and see if "THAT" suits you at all, even if it should work a bit "squarely".

OMG, I'm already lost in this Here some Dokers, here containers, still some Hassio and Proxmox....
The basic question is whether I will be able to install the drivers for the USB-RS485 converter there somewhere?
And on the Home Assistant website, where there are various installations to choose from there is also something like Generic x86-64, isn't it better to be interested in that? Then maybe you wouldn't need any virtual machine?

Michal_212 wrote:

Here some Dockers, here containers, still some Hassio and Proxmox...

.
Look at the Docker logo it will explain where the containers come from .

Michal_212 wrote:

Basic question will I be able to install the drivers for the USB-RS485 converter in there somewhere?

.
If it is a converter with automatic control of the transmission direction then no special drivers are required.

Michal_212 wrote:

And on the Home Assistant website where there are various installations to choose from there is also something like Generic x86-64, isn't that better to be interested in?

.
It's not better, but it can be.
I have two virtual machines. One for normal work and the other for testing e.g. if updates work properly.
I switch off the main one, switch on the test one updates and tests.
It may also happen that you need 'real' Linux - what then? ..buy a second computer?

starob wrote:

Look at the Docker logo and it will explain where the containers come from

.

Well, yes, only that when I click on the installation of at least on Raspberry (on the Home Assistance website), there in the installation instructions there is also something about containers and Docker, while it seems that Docker is mainly used in the case of installation on Debian .

I would understand if it was still the case that I wanted to install it on Windows, then I would expect to need a virtual machine.

starob wrote:

It could also happen that you need "real" Linux - what then? ..buy a second computer?

.

But for example installing Home Assistant on a Raspberry then I wouldn't have access to "real" linux either no? Or would I?

By the way, it is not known whether installing this Generic x86-64 version would then be able to back up Home Assistant and whether support for this method of installation would cease after some time.

HA always allows you to take your own snapshots, but everything has to be set up from scratch and only then can you restore it from within HA (provided you have copied it somewhere externally)

Michal_212 wrote:

But for example installing Home Assistant on a Raspberry then I wouldn't have access to "real" Linux either, no?

.
.. well no, because it's not the kind of Linux you're used to
With virtualisation you take snapshots of the whole system and restore everything with one click.

Try different methods and you can judge for yourself. You don't lose anything because you are just starting out.