The Vera drivers are not the only ones to offer full compatibility with this super Remotec module. eedomus has been faithful to the way you work and integrated it quickly in one of their recent updates.
At the risk of being heavy, I will repeat something that perhaps I have read on several occasions lately: the eedomus driver is one very interesting solution. It is a very lively, open platform, which constantly offers new stuff and has great potential. I stress this because it is the typical product when using it for the first time and see their features, think it’s an interesting product but do not see everything offered until time passes and start using in depth.
It’s just what’s happening with me eedomus. Every day we are more modules migrating to this platform. It was forced at first, when we wanted to try Z-Wave modules that are not yet integrated or in Fibaro or in Vera, as for example the bulb Zipato RGBW, or the multisensor Philio that we present in this post.
A root integrate these modules supporting eedomus, I’ve been slowly discovering everything offered by this platform, which is a lot. I will not say here that its interface is great and it outperforms Fibaro that would be a lie. It’s probably its weak point, aesthetically speaking, because from the point of view of functionality, it seems a good interface. And the interface of the app, being simple, I think is not bad. But its strengths are so many that I would say that the interface is not all there is to know and look beyond.
Passive location in eedomus
It is not my intention in the article today, trying to convince anyone of the merits of this eedomus platform. The purpose is different but I am reluctant to tell in a few words all I’m slowly discovering: remote access works really well, is very fast and, last but not least, do not need 3G mobile as a connection GRPS enough, you can connect a 3G eedomus skewer, which allows a redundant connection as eedomus automatically switches to 3G when it detects a problem with the connection for Ethernet / ADSL (soon to talk about it in another article) has interesting options geolocation via a dedicated device or mobile apps (ability to run home automation scenes depending on where we are), and even passive location without impact on the battery life of the mobile device, using ping, great possibilities for customization of the interface, a wiki on eedomus very complete with all the information needed by any user of the mark, recent or not possible to include and exclude modules from the mobile application; compatibility with Z-Wave modules emerging market very early (the new Motion Sensor 4 in 1 Fibaro, for example, not fully yet integrated into the Home Center brand and yet is fully functional with vibration sensor included in eedomus).
Integration of the module Remotec ZXT-120 IR in eedomus
The integration process is actually very simple. In the web interface, we have to go to Settings / Add or remove a peripheral / Add a peripheral Z-Wave. When the controller enters eedomus inclusion mode (we indicated on the screen and produces a sound), we have to press the button once inclusion of Remotec ZXT-120 module IR (called PROG Button at the instructions of the module). Then appear on the web interface and we will have to assign it to a room in the house, after which we will have to set # 27 parameter with the appropriate value and adapted to our split air conditioning, as explained in our previous review on this product.
Configuring of the module Remotec ZXT-120 IR in eedomus
Change a setting in eedomus is not complicated, although not as simple as in Fibaro, I must say. In the settings of the module, we have to go to “Radio Settings” tab. In the “type command” box choose “Command_Class_Configuration” and “Command Name” select “Configuration_Set”. In the “parameter number” box will “27”, because we know that this is the parameter that allows us to configure our split, in “Size” 1 and “value” in my case I put 25 because that is the code Fujitsu to control my split. After saving the changes, they will appear in the bottom places of the screen.
Using of the module Remotec ZXT-120 IR in the interface Web
In the web interface eedomus after including this module Remotec ZXT-120 IR, we will have 4 new modules. The first is the mode or split state (on, off, heat pump, air conditioning, ventilation, etc..) the second is the set temperature; the third is the ambient room temperature and ventilation mode (auto, low, medium and high). The management options offered by these four modules are extremely simple, with buttons whose design and text are fully customizable.
Use of the module Remotec ZXT-120 GO in the App eedomus for iOS
The App that allows you to “drive” from your iPhone or iPad your home theater eedomus-based installation, management of the module Remotec ZXT-120 IR is also extremely simple and orders, despite being a cloud-based system running with a latency time really very short. The interface is not great, I know, but it is very clear and functional and also, as we have recently seen in another article, this module is fully accessible to blind people eedomus using Voice Over on your iPhone.