Right now they are sold out, but I do have an cc1101 868 with esp8266 connected
Can that work?
Also have this
Can that work?
Great! I didn’t think to ask existing users!
Rather than hijack this thread, let’s move discussions to the evohome_cc thread.
The first step would be for you to send me a very recent packet log, and info about your Itho kit. Would you expect it to be implemented as a Fan, or Climate entity, or both?
From evohome_cc’s point of view - you specify a serial port. Just try it and see.
As to if you can load evofw3 on it, you’ll have to ask at GitHub - ghoti57/evofw3: Major overhaul of evofw2 Evohome listening software to use asynchronous radio mode, I’m afraid.
Did you manage to solve this error? I’ve exactly the same error when using the new updated code.
Nope sorry, i cant get my head around it. If you solved please update here! 
I got it working again. My pacakages/itho.yaml:
fan:
- platform: mqtt
name: Badkamer Ventilatie
command_topic: "ITHO/Fan/cmd"
state_topic : "ITHO/Fan/State"
state_value_template: "{% if value|float==0 %}State 0{% endif %}{% if value|float >0 %}State 1{% endif %}"
payload_on: "State 1"
payload_off: "State 0"
optimistic: true
preset_modes:
- "off"
- "low"
- "medium"
- "high"
- "full"
preset_mode_command_topic: "ITHO/Fan/cmd"
preset_mode_command_template: >
{% if value == 'low' %}
State 1
{% elif value == 'medium' %}
State 2
{% elif value == 'high' %}
State 3
{% elif value == 'full' %}
State 4
{% else %}
State 0
{% endif %}
preset_mode_state_topic: "ITHO/Fan/State"
preset_mode_value_template: >
{% if value_json.fan == low %}
State 1
{% elif value_json.fan == medium %}
State 2
{% elif value_json.fan == high %}
State 3
{% elif value_json.fan == full %}
State 4
{% else %}
State 0
{% endif %}
sensor:
- platform: mqtt
name: Badkamer Fan Tijd
state_topic: "ITHO/Fan/Timer"
value_template: "{{value}}"
unit_of_measurement: 's'
- platform: mqtt
name : Badkamer Fan Snelheid
state_topic: "ITHO/Fan/State"
value_template: >
{% if value|float==0 %}Standby{% endif %}
{% if value|float==1 %}Laag{% endif %}
{% if value|float==2 %}Medium{% endif %}
{% if value|float==3 %}Hoog{% endif %}
{% if value|float==4 %}Full{% endif %}
{% if value|float>=11 %}Hoog(T){% endif %}
group:
Ventilator:
entities:
- fan.badkamer_ventilatie
- sensor.badkamer_fan_snelheid
- sensor.badkamer_fan_tijd
3 Likes
Wow, did not see this.
Thanks! at least no errors for now, time to check where the fan controls have gone.
1 Like
Hello guys, currently running a NodeMcu V3 with a CC11010 module connected to it, running the code of @jodur with ESPHome. Works like a charm together with my CVE-S OPTIMA with external CO2 sensor.
But now I have installed a second Itho box for upstairs, off course I want to be able to control it the same way as the first box. So, I soldered a second ESP together with the same code in ESPhome. But the issue I’m having now is that both the boxes react to commands of both ESP’s. I think it is because the code is the same and therefore also the device ID for communicating with boxes.
So my question is, is it possible to make each device unique? If yes, what do I need to change in the code?
Hi all,
First of all thank you to everyone that helped making this possible.
I used to run everything via domoticz, but now I switched to home assistant.
Using the latest packages/itho.yaml script here I got the current status of my Itho showing correctly on my dashboard.
In domoticz I used a virtual switch to control the Itho by sending http commands (state,2 / state,3 etc).
I followed the documentation of the (renewed) Google docs sheet.
But failed to find how to send commands from HA to the Itho.
Can someone please tell me how to do this in HA?
Thanks in advance.
here same issue comming from domoticz and migrating to Hassio
Martin, finally had some time to play arround again. This should now be possible. They have released a new library (https://github.com/arjenhiemstra/IthoEcoFanRFT)were you coud specify the send ID of you device, I will try to integrate this new library so we can use this in the future. Meanwhile i first implemented to long waiting “fix” for OTA updates.
Just released a new verion for ESPHOME
https://github.com/jodur/ESPHOME-ITHO
Changes:
- New ITHO LIB is used, so the sendID can can be set, so it is possible to use this for several units, as long the sendID differs
- OTA can now be done without any problems
2 Likes
@jodur, thank you so much! Works great! Now i can control both fans separately. I use a external C02 meter to ramp the fan up when the value gets to high.
My lovelace interface:
Hi All,
Is there a option that you can add HA as a virtual Remote into the ITHO ESP?
I have now 2 remotes in ESP added. But want HA also in to this. So when I use HA to control the remote, I see in MQTT the unit back in the payload.
Hi,
I ran into 2 warnings during compile. One related to a deprecated function and one related to missing IthoStandby/DucoStandby.
Fixed them with partial success. Warnings are gone, Standby switch visible, but result for the switch is same as using the low setting.
I know there is a setting to switch it off (it works from my remote, and also worked in the ESPEasy version I was using before swithching to ESPHome)
Any idea where to look to figure out the right setting?
Is it possible to add the fan as a fan instead of a switch?
Hi @Hiker,
I am at the exact same point now you were in November last year. I can turn the ITHO on/off through Home Assistant, but the speed will remain low and I haven’t found a way yet to change this to be used in automation.
Have you found a solution in the meanwhile?
Thanks
Alright, it’s fixed. Checked the dupont cables, one was maybe not properly connected, was able to gather the RF id of the remote, added it in ESPEasy, then calling services through HomeAssistant to control fan speed. Works perfectly!
Thanks for the code! I was able to control my Itho fan with your code via Home Assistant after soldering a C1101 to a Wemos D1 mini. A few small questions and things that don’t work:
- I have an Itho fan with a humidity sensor, so the fan ramps up after someone takes a shower. With the current code I can only set the fan to low/medium/high, not to auto. Ideally I would like to be able to set the fan to high when the living room CO2 gets too high, but revert to auto instead of low. Do you have an idea what would be required to implement that? I’m happy to write code and test to make it work, but guidance would definitely be appreciated.
- When I change the fan speed with the Itho remote, or when the Itho sensor adjusts the speed, I don’t see this reflected in Home Assistant. Is this to be expected, is this only supposed to work when you have multiple boards with your code running on it? I can see the fan speed reflected on one of the Itho sensors, so the unit does send out its current state, but it might just not be processed by your program?
Thanks in advance!
The ESPEasy repo shared in this thread does not work with older ECO FAN units, it seems to only work with ECO RTF units (built after 2012).
I have an ECO-FAN 2 at home, and after a lot of debugging, and even going as far as looking at the different protocols that the included fan controller, and the esp8266-c1101 combo, through a signal analyzer, i can say that mine uses a different frequency and protocol.
I can copy-paste from some websites, but TLDR, there exists two variants of the same protocol.
(Dutch comment talking about this, and similar comment, but in english)
Edit: Looking further, there are upgrade boards available to update the fan to receive commands from the new protocol (and remotes), but they’re pricy, around 70 euros here. (The dutch site where I got them had two variants, for slightly newer ones, and for slightly older ones, check the exact product number on the fan before you buy either of them)
Edit 2: Nevermind, that “older one” is about an upgrade from no-remote to the older RF standard, its not the upgrade to RFT that in mind.
Because of this, i’ve made an issue in the ESPeasy repo to add support for the older standard.
1 Like