Where to start (Z-Wave, Arduino, RPI, RF 433MHz, ...) in order not to "wander"

I would like to automate my home and am wondering where to start. Or maybe I should ask the question the other way around -- where not to err and what not to use ?

Going with the advancement of technology/electronics I consider the possibilities as in the table
My so-called boundary conditions (validity from top to bottom):

* reasonable number of cables --> preferred wireless connections
* simple to expand
* possibility of remote control from PC/smartphone
* easy addition of simple devices with RF communication (433.92MHz) due to price and simplicity

Below is my small comparison:

[/b]

HW/SW	+++	---
Z-Wave: a-la FIBARO	wireless configurable from WEB interface(simple)	price, not all Z-Wave modules compatible
Z-Wave: a-la Vera 3/Lite from MicasaVerde	easy to configure less aesthetically pleasing UI than FIBARO lots of compatible Z-Wave modules, popular	manufacturer loyalty
Z-Wave + Indigo ( Link )	wireless, support for large number of communication standards	OSX only, manufacturer tie-in
Z-Wave: USB Z-Wave (Aeon) + OpenRemote	open-source software, support for large number of z-Wave modules	forum seems to be not very popular...?
Raspberry PI + GPIO + RaZberry ( Link )	price, high popularity, open-source	?
Raspberry PI + FHEM ( Link )	jw + operation of almost "everything"	documetation mostly in German
PLC	solid, sturdy	tachment to manufacturer

I am curious which solutions are worth considering and future-proof according to you.
Certainly my table is not complete--I would be happy to add the missing scenarios with your help.

I would advise against PLC, this is just my opinion. The main problem is the price. You can buy a simple PLC cheaply, but you will need output blocks, input blocks, an interface, a nice panel, etc. I like Z-wave as an idea, the Z-wave alliance is an organisation that brings together all the manufacturers of these devices and makes sure that everything is built according to the specifications. You wrote that FIBARO has a flaw because not all modules are compatible. It seems that this is FIBARO's problem, because that is what the Z-Wave organisation is for, so that all devices work according to the charted specification. But there is also a new generation Z-Wave Plus specification where the old controllers will not be able to cooperate with the new generation modules, while all the Z-Wave Plus controllers should be compatible with the old generation Z-Wave. Remember also that in a Z-Wave network each receiver/transmitter i.e. each device is also a transmitter in order to amplify the radio signal to the modul furthest away from the controller. This is just my 2 cents.
Sorry for the lack of Polish characters but I am writing from a work PC.

heh but the inaccuracies have crept in here
@meak : there is no controller in the world that supports all Z-wave devices and this is not due to compatibility but due to the lack of templates supplied with the controller (or device) that indicate how the device is to be handled or the lack of support for a particular type of frame.
With manual entry of parameters specifying how the controller should handle a device, in theory Vera should handle them all.

By far the friendliest UI and the most well-developed templates are provided by Fibaro; unfortunately, the number of devices supported by Vera is still a long way off.

The top three is rounded off by Indigo, but this software requires a MAC computer and a Z-wave stick.

The other controllers mostly only support simple commands (basic frames) and require manual definition of devices.

Another group of controllers is open software on e.g. Raspberry etc.
Leaders in this group include OpenHAB, Domoticz, Jeedom.

Multifunctional devices that use extended frames pose considerable "compatibility" problems for controllers. The more "sophisticated" the device, the greater the implementation problem.
Here, the majority of Fibaro devices must be clearly indicated, as they have rich functionality. I will show this using an example.
The Fibaro Dimmer has the following functionalities: on/off, level, reaction to alarm frames (fire, flooding, general), energy measurement, overload detection, no-load detection (burnt bulb), and all this is transmitted to the controller via Z-wave.
Only 2 controllers(Vera, HC2) have implemented templates for handling all these events, the others handle this dimmer in a simplified on/off/level manner.

I for starters would choose Vera because of its reasonable price, large number of "compatible" devices and hundreds of different types of integration.
A layman should choose Fibaro, unfortunately paying a much higher price for the friendly interface.

Commercial systems are worth looking into: Tellstick, for example, uses RF 433 and a central controller linked to the cloud. A newer version of Tellstick already uses z-wave. The disadvantage of the latter: high price.

What about http://www.openhab.org/ or https://home-assistant.io/
They are free and the amount of hardware supported is huge, we are not reliant on one manufacturer / topologies

Homeassistant on RaPi works for me. Lighting control via MQTT, extra-duplex switches ( Sonoff and Tuya with replaced firmware on Tasmota), temperature sensors and thermostatic heads via ZigBee (zigbee2mqtt). Gate gate push button flood and smoke sensors rf433mhz via Sonoff gate with Tasmota firmware uploaded. Old sony tower control via IR gateway on MQTT Tuya with firmware changed to Tasmota. DSC alarm plans to connect via Envisalink card. Overall very wide integration possibilities. Free open source software. A lot of freedom of logic programming, both in the assistant itself and through the node-red add-on, virtually unlimited scope for fun for someone who likes to program and is not afraid of the soldering iron