"Sly House" - choice of equipment

Question

Do it yourself

Good day!

After reading all sorts of articles on the topics of smart and not so smart at home, all sorts of automation and other things, I also wanted to do my own thing . So. We allocate some funds for the test set (1 sensor + center) and…

there is a long boring text, but I still came up with a shorter question:

Вместо вступления: тема весьма неоднозначная, готового решения нет и вряд ли будет.
Задачи на первое время такие:

1. Самое простое из хотелок — мониторинг температуры во всех помещениях, а заодно и влажности. (DHT22 вроде рулят) + уличный
2. датчики освещенности в помещении (эти вроде подойдут)
3. детекторы движений (этот решил попробовать)
4. В каждой комнате управляемая система колонок (примерно как в этой статье)
5. Плюс кухня/ванна/туалет — датчики залития
6. Дополним датчиками (герконами) на, хотя бы, входную дверь
7. И пульты с тачскринами для управления со стены например
8. GSM сигнализация.
9. Расширяемость.

Для начала хватит. Это по части оконечных устройств. Теперь как все это чудо собирать/управлять. Нужен какой-то центр.
Из всяких одноплатных компов и контроллеров выбор пал на BeagleBone Black и Raspberry PI B. Разница в 10 баксов но! В одном есть звук и мало GPIO в другом много выводов и нет звука (я имею ввиду 3.5 стерео джек, через hdmi есть)…
Отсутствие звука лечится USB звуковухой вроде этой, а малое количество выводов… сложно, но тоже лечится… (платы расширения, или i2c ...).

Читал интересный блог www.ab-log.ru, однако там автор использует комп дома, я еще одного сервака полноценного в квартире не выдержу) Видел на хабре разные статьи по автоматизации. Но почти все они «локальные» если можно так сказать. Решают узкий круг задач.

Есть еще CubieBoard, дороговат но вроде подходит.

Собственно вопросы:

1. Как лучше организовать всю связку датчиков/точек управления?
2. Какую среду для передачи лучше использовать? Само собой поменьше проводов, но точно не радио. Видел варианты 1-wire, i2c, думал даже про Ethernet 100Mbit + POE например или просто в витуху пару с питанием. Ничего из этого не подходит на 100%
3. Кто-нибудь держал в руках BeagleBone Black? Как оно?

I wanted to make sensors/buttons networked on ab-log.ru + touchscreens for control and information in each of the rooms + BeagleBone extreme ala control center, but if you hang LCD + touch + ethernet, atmega328 does not have enough outputs on the Pro Mini board (or enough ?), and atmega2560 saw only large ones (is it really only to breed?), and hanging BeagleBone in each room is too fat like ... although ...

How to be?
Maybe I'm giving up on 1-wire, i2c, T10 and others like that for nothing? What I argue - ethernet is more universal.

PS: do not kick hard. but in a week I went through about 5 different options, re-read a bunch of docks, articles, mana, datasheets. the main problem is that I can’t stop at something specific and because of this I can’t place an order. And the soldering iron is already getting cold ...

ZYY: Maybe I don't want to start with that?

Answer 1

Vitukha, in short, to lay.
And then figure out what will be there.
Ethernet or RS485 or whatever.

Answer 2

> atmega328 does not have enough outputs
, this can be easily increased. Using the i2c protocol, you connect mikruhi that give up to 16 more outputs, and you can connect several of them.
> RS485
is definitely not a suitable option. in your case, everything, like mine, rests on a regular customer survey. and the more clients, the greater the delay in polling.
i2c is for in-circuit connection
I think the best option for you is ethernet. This is a ready-made and debugged protocol on top of which it will be easier for you to implement your own protocol.
Another plus for him is that if you choose him, then it will be easier for you to get to your dream, because while you smoke different mana and fill your forehead, you will understand that your idea is eating up your time or will become uninteresting to you for another reason.
In general, I think for home affairs Ethernet is better for you.
As for clients, I would implement data collectors on the Arduino platform or stm, and put the logic on the RPi, which interrogates the collectors via Ethernet.
Sound: uniquely on a separate controller.
To summarize: make as many independent modules as possible. Although the system will look more cumbersome in terms of architecture, it will be more convenient to debug. For my projects, I think it's worth starting with simplicity.

Answer 3

I am building a similar Tricky House on Raspberry.
I started with the Cunning Door:
- monitors whether the door is closed, whether the lock is closed (a mic that presses the lock tongue),
- monitors the temperature-humidity in the hallway,
- a motion sensor (any arduino ones are suitable),
- a light sensor for not turned off lights . devices (arduino).
- monitors the neighboring bathroom for flooding.
The whole thing is displayed on the WEB server raised on Raspberry.
+ sending e-mail in case of problems (flooding, doors not closed for a long time, etc),
I didn’t bother with GSM - I considered it inappropriate for myself (although technically it’s not very difficult).
In principle, this is the most necessary thing that I needed.
Further, everything scales well according to the "one monitoring point - one Raspberry" scheme.
All data from each Raspberry is wrapped on one web server.
I have wifi.
So far, there are only two Malins - one is the aforementioned Sly Door, the second in the common room.
On it, in addition to sensors, there are a pair of relays that can switch 220V (in my case, one of the lighting in the room and a kettle in the kitchen) and a pair of LEDs that command air conditioning, TV and music via IR.
You can, in principle, pile up more different bows and wrappers.
One way or another, everything is configured based on desires and fantasies.

Answer 4

Maybe I'm giving up on 1-wire, i2c, T10 and others like that for nothing? What I argue - ethernet is more universal.

do not forget that at least I2C should have no more than 400pF bus, and this is 2-3 meters in total. It is good if several sensors need to be connected to the controller. Or install a bus booster.
3.5k rubles - not so much, given the circuitry, protection, and so on. It will be more expensive at the most (unless, of course, there is time for a car).
Protocol - SNMP is good, especially because of the traps. And if you use SNMPv3, then the issue of protection is practically removed.

Answer 5

Ideas in the protocol of the KNX standard, something similar to 485 or closed standard.
You can get materials on the net ( see here )

Answer 6

thanks for the detailed answer. Approximately such thoughts were when I chose Ethernet.
about clients, I ordered sets of sensors, programmers, I found a store with atmegas in the city. Only there from mikruh only atmegas and that's it (but there are even 2560 and 328 in deep). There are quartz, capacitors, resistors and other small things. I will try to sculpt a network client powered by ethernet. I don’t know whether to implement the POE standard, or just put 5V on a pair, it’s not the point yet ...
Laurent saw a ready-made board (ethernet control web + telnet + tsal outputs to sensors, inputs / outputs and several relays 230V 7A) 3.5k asking for it. Horror. I will collect myself.
The only question that bothers me. How about security. All sorts of things in LAN are a potential hole. Yes, you can come up with passwords, limit by IP, and so on. It is also impossible to completely protect from LAN with tyrnet. We will do VLAN and think about something further ...
Sound is also a separate issue. I want the music to play in such a way that when I move from the room to the kitchen, it also turns on in the kitchen by a motion sensor, for example.
In general, darkness problems. Something at least ideologically can be seen on the sites ab-log.ru and MajorDomo. There is nothing ready-made. You have to make your own moped.
Tell me, have you done something similar? can i read it somewhere?

Answer 7

guys are engaged in industrial and street lighting on this site https://rusest.com/katalog/dlya_proizvodstva/