![]() We needed 4 pins for the ethernet connection & 1 pin for the on-board LED. It was a challenge to get 40 I/O available on the teensy 2.0. Each sub board has it's own 5v 5 port switch, and a POE splitter - the whole board being run by 1 port on my POE switch. In our build we have 2 sub-boards each with 4 nodes - making a total of 8 nodes with a capacity for 320 i/o. The boards have a web interface which is really important for setting up and diagnostics as you have feedback showing which inputs or outputs are active. The software and interface to the loxone does not use any polling at all- so all the double/triple clicks work flawlessly with the loxone system. I'm not a hardware expert at all! But the system we have made is bullet proof reliable. We did consider using I2C io extension boards, but physical size is a factor and it was easier for us to make it compact using the teensy. I chose the teensy 2.0++ as it had a large number of digital IO on the board. Add to that 20 door & window sensors, plus blind controls, PIR sensors, under floor heating actuators and pumps. We have 43 light switches - but each light switch has 4 contacts - making 172 inputs just for the light switches. When specifying the server, we quickly realised we would have to find another solution for all the digital io. I would recommend Loxone to everyone who’s looking for a mature and modern home automation system, that allows to be extended through some DIY connections.I've nearly completed building my own home, and have used the loxone mini-server to supply the home automation. By using cheap, but kickass DMX dimmers, DMX relays and DMX LED controllers, I saved a lot of money. DMX is a protocol that is often used to control stage lighting and effects. The solution was to leverage the Loxone DMX extension. Because I have foreseen a huge number of lights, I needed a way to limit the price. Some examples: lights, blinds, irrigation, valves, wall sockets, ventilation… These outputs are mostly limited to switching on/off the right voltage signals. Incoming events should result in automated actions, so a lot of outputs are required. A very simple and cheap solution, without any notable latency. The miniserver decodes the incoming binary data and determines which switches or inputs are active. Each 50ms, the state of the inputs (0/1) is sent through UDP, in a binary format, to the Loxone miniserver. This component can handle 72 low voltage input signals. In my case I needed around 100 inputs, which means many Loxone extensions, so I would end up with an expensive setup.Īfter some good advice that I received on several forums, I decided to buy the Elexol Ether IO72 TCP component. Most of them originate from switches, but also presence detectors, motion sensors, push buttons, window sensors, rain sensors… require input signals. In home automation solutions, you need a lot of input signals. These are the two cost-efficient solutions I’ve implemented: Cheap inputs In this way, I was able to have all capabilities I was looking for, within an affordable budget. This setup is rather limited, because I’ve extended Loxone with some other components. ![]() From a technical perspective, these are the Loxone components I’ve used:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |