Custom Component: Carrier Infinity Touch control via Infinitude

Newms118 · April 6, 2022, 1:55am

In your instructions, why are you setting the network setting to “bridge”, when this set of instructions says to set it to “host”: Installing on Home Assistant · nebulous/infinitude Wiki · GitHub

rmertz3282 · April 6, 2022, 10:21am

The simple answer is I’m not sure. My Docker skill Is pretty limited. All I know is I tried host and it didn’t work. I had a different container running another solution that was set to bridge and working and once I moved the proxy to bridge it worked. Must be my HA environment?

tand86 · April 6, 2022, 8:22pm

I believe the bridge he is talking about is the docker’s bridge device linking it to the HA machines network and not the climate config in HA. Glad you got it working! As for the UI, there is a default climate UI tile you can use.

logistician · April 20, 2022, 2:10pm

Thanks, but I was wondering how you figured out what the property values were? I.e., “outdoor_temperature”, etc? I have a carrier system and I see tons of data on the :3000 web page but have no idea how to get HA to show that.

flutie98 · May 12, 2022, 1:25pm

Thanks @MizterB this custom component is huge game changer for our new carrier heatpump system just installed this week.

I am coming from an Ecobee system with multiple remote sensors and the InfinityTouch thermostat leaves a lot to be desired, HA integration really eases the transition.

I have two questions though…

Is there a way to get the heat pump stage value into HA? I see it in the infinitude web portal but would like that data to be integrated into my HVAC logging in HA.
Have you figured out if its possible to spoof the InfinityTouch internal temperature by pushing values through infinitude? The reason I ask is I am considering keeping my Ecobee and sensors powered for the temp/occupancy data and then using HA to create a “follow me” system to tell the InfinityTouch what room temp to control to.

Thanks again!

lensherm · June 1, 2022, 1:59am

For example, to get the outdoor temperature, you can create a template sensor in your config file, such as below. Of course update per what the zone name, desired unique id, etc. for your respective system.

template:
  - sensor:
      - name: "AC Outdoor Temperature"
        unit_of_measurement: "°F"
        unique_id: "ac_coutdoor_temperature"
        state: >
          {{ states.climate.zone_1.attributes.outdoor_temperature }}

mtwheatley · June 11, 2022, 7:09pm

Thank you sooo much for your post. I have been trying to get this working under HASSIO for days. Your post gave me all of the information to get it going. Particularly important were how to get the Portainer add on and that I had to set the proxy server in my Carrier thermostat wireless settings.

Michael

mtwheatley · June 11, 2022, 10:56pm

I have Infinitude running on my RPi HASSIO 2022.05.3 system and the basic climate card configured as:

climate:

platform: infinitude
host: 192.168.10.21
port: 3000
zone_names:
- ZONE 1

in configuration.yaml. This results in a card showing the Current Temperature on my Overview page – so everything is working.

Now I would like to access other variables like Outdoor Temparature and Current Humidity and create an Entities card showing them. To begin with, I have tried:

template:

sensor:
- name: “ZONE1_current_temperature”
  unit_of_measurement: °F
  unique_id: “ZONE1_Current_Temperature”
  value_template:
  “{{ state_attr(‘climate.ZONE1’, ‘current temperature’) }}”

but this results in an error in the log:

Invalid config for [template]: [value_template] is an invalid option for [template]. Check: template->sensor->0->value_template. (See /config/configuration.yaml, line 73)

Help! Can anyone share with me a section of configuration.yaml that will allow me to create the entities for the items I am looking for.

Thanks in advance

damclarkd · June 12, 2022, 12:41am

Here are a couple of mine.

template:
  - sensor:
      ## These 3 sensors track hvac details for use elsewhere
      - name: "HVAC Action"
        unique_id: hvac_action
        icon: mdi:air-conditioner
        state: >
          {{(state_attr('climate.damac', 'hvac_action') )}}

      - name: "HVAC Fan Speed"
        unique_id: hvac_fan_speed
        icon: mdi:fan
        unit_of_measurement: "cfm"
        state: >
          {{(state_attr('climate.damac', 'airflow_cfm') )}}

      - name: "HVAC Current Temp"
        unique_id: hvac_current_temp
        icon: mdi:thermometer
        unit_of_measurement: "°F"
        state: >
          {{(state_attr('climate.damac', 'current_temperature') )}}

Note: Your ZONE1 is my damac

HTH,
Cheers

mtwheatley · June 13, 2022, 12:24am

Thank you very much – that worked.

mtwheatley · June 13, 2022, 4:37pm

I have successfully set up my Carrier Infinity thermostat in Home Assistant and created sensors for the values I am interested in. But three of the sensors: HVAC Mode, Setpoint Cool and Setpoint Heat report “Unknown”. Here is my configuration

climate:
  - platform: infinitude
    host: 192.168.10.21
    port: 3000
    zone_names:
      - "ZONE 1"
      
template:
  - sensor:
      - name: "Current Temperature"
        unique_id: zone1_current_temperature
        icon: mdi:thermometer
        unit_of_measurement: "°F"
        state: >
          {{(state_attr('climate.zone_1', 'current_temperature') )}}
          
  - sensor:          
      - name: "Current Humidity"
        unique_id: zone1_current_humidity
        icon: mdi:thermometer
        unit_of_measurement: "°F"
        state: >
          {{(state_attr('climate.zone_1', 'current_humidity') )}}
          

  - sensor:          
      - name: "HVAC Mode"
        unique_id: zone1_hvac_mode
        icon: mdi:air-conditioner
        state: >
          {{(state_attr('climate.zone_1', 'hvac_mode') )}}
                 
  - sensor:          
      - name: "HVAC Action"
        unique_id: zone1_hvac_action
        icon: mdi:air-conditioner
        state: >
          {{(state_attr('climate.zone_1', 'hvac_action') )}}
                 
  - sensor:
      - name: "Setpoint Heat"
        unique_id: zone1_setpoint_heat
        icon: mdi:thermometer
        unit_of_measurement: "°F"
        state: >
          {{(state_attr('climate.zone_1', 'setpoint_heat') )}}
          
  - sensor:
      - name: "Setpoint Cool"
        unique_id: zone1_setpoint_cool
        icon: mdi:thermometer
        unit_of_measurement: "°F"
        state: >
          {{(state_attr('climate.zone_1', 'setpoint_cool') )}}
                  ```

What am I doing wrong?

damclarkd · June 14, 2022, 2:26pm

Michael, You likely have a different thermostat from me as I don’t show ‘setpoint_heat’ ‘setpoint_cool’. Or maybe because I am currently just in cool mode.
Maybe check your States in Developer to ensure you have the correct attribute naming?

Also, I am not a yaml or HA config expert by any means but I believe in your config you can eliminate the redundant - sensor:'s. Keep the first one and just list out the different - name: as a list.

- template:
    -sensor:
        - name:

        - name:

Sorry can’t be more help on the 3 errant sensors.
Cheers

mtwheatley · June 14, 2022, 3:52pm

Thank you. Once again you are right. The three sensors I am looking for do not seem to be supported despite the fact that they are shown on the Infinitude server page (Homeassistant.local:3000).

Michael

bretton.wade · June 15, 2022, 1:31pm

I think that’s probably because the HA climate component doesn’t track the setpoints separately by mode. Think of this integration as an adaptor more than just a raw interface. What you can see is what the setpoint is for the current mode. I track this in my thermostat:

    - name: "Main Hall Target Temperature"
      unique_id: "main_hall_target_temperature"
      unit_of_measurement: "°F"
      state: "{{ state_attr('climate.main_hall', 'temperature') }}"

If you are trying to run in dual mode, I recall the HA Climate entity has a low and high… (see Climate - Home Assistant).

If what you really want is just the raw variables, you can connect to the Infinitude instance directly and get the json. The path is: http://:3001/api/status

Also, I believe @damclarkd is correct, you should only have one ‘sensor’ section under your template section.

tand86 · July 24, 2022, 4:12pm

Sorry for the late reply, if you go to the Dev Tools page, on the States tab, you can search for your climate entity (mine is carrier) and it will show you all attributes and the corresponding states.

philgrocks · August 19, 2022, 4:28pm

Did you find the “dummies guide”. Crawling thru 4 years of messages is not the easy way to get started

raphs · October 27, 2022, 3:37pm

also trying to figure out how to implement this… looks like running infinitude as a portainer add-on in HA is no longer functional. How are people deploying this? or is the solution to just run the proxy somewhere else? would hate to spin up another VM just for this but will do it if it’s the only option. thanks so much for any help!

moto2000 · October 28, 2022, 2:31am

It still works running the proxy in portainer, that’s how I’ve been doing it for about 2 years now. You just need to use a portainer addon that works.

I use alexbelgium’s: hassio-addons/portainer at master · alexbelgium/hassio-addons · GitHub

Just an FYI, doing so will make HA say that you are running an unsupported installation, but that is still fine.

raphs · November 17, 2022, 4:57pm

thanks for all the help, got this running and it’s quite nice!

silly question… i want to make the outside temperature available to HA… how can I do this?
this value:

moto2000 · November 18, 2022, 2:58am

It was actually just mentioned a few posts up!