Skip to main content

Daikin FT aircon and Remotec ZXT 120

In the quest to make the existing appliances "smart" or otherwise enabling dumb devices to be even dumber with unnecessary initiative.

I got the reputed bad review Remotec ZXT 120. As I already expected it to be bad, my expectations were clearly exceeded.

This isn't the first attempt I've tried to get IR blasters to work. I vaguely remembered early attempts at trying to program the IR on my Palm 3 and Palm V. Needless to say, this went a lot better than expected.

Tip 1:

After reading the instructions first (rare occasion) , being a bit more careful. I discovered you need to change the mode of the Remotec first before joining the Z-wave bridge, in my case Fibaro. This is important as you cannot change the mode once connected. If you forget to do so, you need to exclude the device and do the setup again.


Tip 2:

The temperature is wrong.  Well, there is an offset that can be configured on the z-wave bridge. There is a parameter to allow for the offset. The short of it is that the thermostat is slow and inaccurate, but you can muck around with it until you get fairly average temp readings over a long averaged period which isn't that bad.

Tip 3:

I use a Daikin FT25DVM. The Remotec site have a serious number of codes for Daikin and I must have spent at least 2 hours trying codes in a tikam tikam approach. Noted not the best, hence I never got the code until I did a google and find a forum response of yet another pettson complaining about the Remotec and Daikin, But the silver lining was that he gave the code. Much thanks there.

It's Code 6 !!

If I did start from 1 and went on to the 2nd number instead  of jumping around, it might have been faster. I was also misled by the Fibaro HCL to say a soft reset is needed before the code is implemented, which was not true. You can just set the numbers in and save and it is immediately usable in the controls.

Actual Use

So I can now turn on my air-con from my phone in any room without any knowledge if it's actually on or not from a thermostat that might tell me an hour or so later. Is there any good stuff out of this? Now I can add the air-con to scenes for Alexa. So "Alexa, turn on sleep", it actually can turn on the AC. Just in time for hot weather when the Fan just isn't enough.


Comments

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…