Since I am planning to build a house, I am naturally also considering smart home solutions. As this topic is completely new to me, I first need to do some research. I would therefore like to clarify some basic questions and facts before proceeding. I will simply write down my thoughts as if they were facts and would ask you to correct me where I am wrong 🙂
I want to leave KNX or BUS systems aside for now and focus only on wireless solutions, so please do not discuss which makes more sense or is "better." One step at a time; this is purely about understanding :p
There are many different wireless protocols. Open ones like Z-Wave, ZigBee; "semi-open" like eNet; and proprietary ones like Somfy io.
Somfy has the advantage that everything comes from one source and it should be plug and play. The ideal solution for beginners—you simply put together what you need, install it, and it works right away. The big disadvantage, of course, is that you can only integrate Somfy or Somfy-approved sensors and actuators and are dependent on Somfy continuing to develop new products and supporting the current protocol.
eNet is a protocol from a few premium manufacturers, and as such, the devices are quite expensive. Although it is an open protocol, it is supported by only a few providers and products. So it has the same disadvantage as Somfy: limited selection and dependency on a small number of providers.
The open protocols, which are basically standards, have the advantage of many providers. However, this is also the biggest disadvantage because it’s easy to lose oversight, you end up assembling the whole system yourself without it all coming from one source, and there are likely to be significant differences in quality.
Is this roughly correct?
I want to leave KNX or BUS systems aside for now and focus only on wireless solutions, so please do not discuss which makes more sense or is "better." One step at a time; this is purely about understanding :p
There are many different wireless protocols. Open ones like Z-Wave, ZigBee; "semi-open" like eNet; and proprietary ones like Somfy io.
Somfy has the advantage that everything comes from one source and it should be plug and play. The ideal solution for beginners—you simply put together what you need, install it, and it works right away. The big disadvantage, of course, is that you can only integrate Somfy or Somfy-approved sensors and actuators and are dependent on Somfy continuing to develop new products and supporting the current protocol.
eNet is a protocol from a few premium manufacturers, and as such, the devices are quite expensive. Although it is an open protocol, it is supported by only a few providers and products. So it has the same disadvantage as Somfy: limited selection and dependency on a small number of providers.
The open protocols, which are basically standards, have the advantage of many providers. However, this is also the biggest disadvantage because it’s easy to lose oversight, you end up assembling the whole system yourself without it all coming from one source, and there are likely to be significant differences in quality.
Is this roughly correct?
untergasse432 Mar 2021 09:26K1300S schrieb:
I would also like to point out that KNX-RF exists. 🙂That's correct. However, the effort required for RF is similar to wired KNX and therefore significantly higher than for other wireless solutions, which ultimately also control blinds and lighting.Once again: I still consider KNX to be the only real solution 🙂
bauenmk20202 Mar 2021 10:17I believe it is perfectly reasonable to install conventional electrical wiring with a standard switch system in a new build and then retrofit it later with wireless solutions as a "comfort layer."
With wireless systems, it is important to know the "quasi-standard." Similar to how STEREO was and still is probably the most future-proof format for music playback, for wireless it could be: Zigbee??? EnOcean??? I’m not sure, but it definitely helps if the wireless signal is “standardized.”
It is also important to understand the availability and compatibility of actuators and control units, as well as the “software.” Personally, I use a Raspberry Pi as “base hardware,” partly because it is easier to obtain replacement boards for it in the future. For this reason, I would never use a NAS with virtualization or similar solutions. The guiding principle should be: “Keep it simple.” For example, we have exhaust fans with built-in humidity sensors. Initially, I wanted to control these manually, but now I’m somehow “glad” that they turn on and off automatically, regardless of whether a control unit is currently online or offline.
The only reason that might lead me to install a switching actuator in front of them would be to visualize the status or to switch them manually.
With wireless systems, it is important to know the "quasi-standard." Similar to how STEREO was and still is probably the most future-proof format for music playback, for wireless it could be: Zigbee??? EnOcean??? I’m not sure, but it definitely helps if the wireless signal is “standardized.”
It is also important to understand the availability and compatibility of actuators and control units, as well as the “software.” Personally, I use a Raspberry Pi as “base hardware,” partly because it is easier to obtain replacement boards for it in the future. For this reason, I would never use a NAS with virtualization or similar solutions. The guiding principle should be: “Keep it simple.” For example, we have exhaust fans with built-in humidity sensors. Initially, I wanted to control these manually, but now I’m somehow “glad” that they turn on and off automatically, regardless of whether a control unit is currently online or offline.
The only reason that might lead me to install a switching actuator in front of them would be to visualize the status or to switch them manually.
H
HansDampf13112 Mar 2021 11:52bauenmk2020 schrieb:
I find it completely reasonable to install conventional electrical wiring with a standard switch system in a new build and later add wireless solutions as a "comfort layer".This is more or less my approach and why I tend to prefer wireless, fully aware that a BUS system is better. I want to start with simple things like centrally operable/programmable shutters and lighting, then gradually evaluate which features make sense for me and progressively build a full smart home. Many options are possible, whether I will actually need or want them is another matter.
Which software do you use? I have looked into ioBroker, IP Symcon, and similar platforms—they seem great conceptually, but I’m unsure if I have enough time to really dive into them.
T
T_im_Norden2 Mar 2021 12:12If you are sure that you really want a smart home, I would always recommend having an electrical installation suitable for it.
Run all wiring to the electrical panel and include KNX cables, using 5-wire electrical cables.
This way, you can operate everything with regular switches (push buttons) and still have the option to make everything smart if you want. However, you will then need a larger panel and/or sub-distribution boards.
Wireless solutions are always problematic due to range issues; some smart wireless devices fail to connect from the first floor to the room below in my case.
Concrete ceilings and densely installed underfloor heating cause significant interference.
Run all wiring to the electrical panel and include KNX cables, using 5-wire electrical cables.
This way, you can operate everything with regular switches (push buttons) and still have the option to make everything smart if you want. However, you will then need a larger panel and/or sub-distribution boards.
Wireless solutions are always problematic due to range issues; some smart wireless devices fail to connect from the first floor to the room below in my case.
Concrete ceilings and densely installed underfloor heating cause significant interference.