CT100 showing twice?

Configuration Z-Wave
1

I’m still very new to HA, so hopefully I’m not missing something simple here. But I recently setup HA (latest version) on my PINE A64, running dietPi (Debian 8). Using a Aeon Labs Z-Stick Gen 5, and I have my CT100 thermostat connected to via OZWCP. Back in HA, I can see my CT100, but it’s listed twice.

climate.2gig_technologies_ct100_thermostat_usa_cooling_1_2

and

climate.2gig_technologies_ct100_thermostat_usa_heating_1_2

in dev-state. Why does it show both heating and cooling as separate objects(?) under the climate entity(?), or is this expected behavior? From the States page I can do the same thing from either object, turn on heating, cooling, set to auto or turn off, as well as set the temp.

I imagine there is a way in the config to hide an object, as well as rename an object, so I could definitely do that to make it show the way I expected, but I’d rather understand why both are showing and the proper way to handle this.

If any additional information is needed, please let me know and I’ll add.

Thanks!

1 Like
2

Mine does this, too, so I suspect it is expected behavior. The CT100 creates a number of sensors and devices, still unsure what some of them do. I have hidden some, and renamed all.

3

Same here - I only have heating on my CT100s so I use the heating entity but I don’t know why there are 2 different ones - I guess this was a byproduct of merging heating and cooling into the new climate component a couple of releases ago.

4

Thanks for the feedback @mplawner and @aimc.

@mplawner, Could you share how you went about hiding and renaming these sensors? I’ve read that it’s best to do it in the zwcfg…xml file, but I’m not seeing the individual sensors listed in there. I’ve also seen that you can assign friendly names in the configuration.yaml, but then you can’t use those friendly names as an entityID (or something like that).

Any tips would be appreciated!

5

Sorry I didn’t do that earlier. My Mac was updating…
I don’t use the z-wave configuration file to modify. That seemed too… complicated. I configured via HA only.

In the customizations section, I named the different devices found on the CT100 (obviously, you’ll have the Z-wave device id assigned to the CT100, not 23):

climate.2gig_technologies_ct100_thermostat_usa_fan_mode_23:
  friendly_name: Thermostat Mode
climate.2gig_technologies_ct100_thermostat_usa_cooling_1_23:
  friendly_name: Thermostat Settings
climate.2gig_technologies_ct100_thermostat_usa_heating_1_23:
  friendly_name: Thermostat Settings Duplicate
  hidden: true
sensor.2gig_technologies_ct100_thermostat_usa_relative_humidity_23_3:
  icon: mdi:water-percent
  friendly_name: Humidity - Indoor
sensor.2gig_technologies_ct100_thermostat_usa_temperature_23:
  friendly_name: Temperature - Indoor
sensor.2gig_technologies_ct100_thermostat_usa_temperature_23_2:
  friendly_name: Temperature - Indoor Duplicate
  hidden: true

Hope that helps!

6

Thanks @mplawner, that is a huge help!

While I’m familiar with yaml in general, specific commands for HA are still new to me, and now I am seeing how easy it is to configure sensors (or at least hide and rename).

Regarding renaming of Zwave devices, I’ve discovered that this is very easy to do within OZWCP.

  • stop HA
  • start OZWCP
  • input Device name and click Initialize
  • select device to be renamed in the Devices list
  • in the Functions dropdown, select Name
  • input new name and click Submit
  • click Save... in the upper right corner to output new zwcfg_xxx.xml file
  • create symlink from the ozwcp zwcfg_xxx.xml file to HA zwcfg_xxx.xml file
  • start HA

By doing this, my thermostat now has an Entity ID of climate.thermostat_downstairs_cooling_1_2 instead of climate.2gig_technologies_ct100_thermostat_usa_cooling_1_2 which is easier to work with.
Furthermore, by assigning friendly names and hiding duplicates, it has cleaned up my UI and is now starting to look like what I want!

Next task is to get my Yale Real Living deadbolt working right (currently added from OZWCP as a Secure Keypad Door Lock, but nothing happens when I toggle the state).

Thanks again to you both, and hopefully this info can help someone else in the future!

EDIT: And after a little troubleshooting, I was about to get my Yale Real Living Deadbolt added to HA. Turns out I had set the secure key in the config_path options.xml, which was incorrect (since I added from OZWCP). Instead I had to add that in the options.xml file within the openzwave directory (/root/tmp/python-openzwave/openzwave/config for me, which once I have my configs built and everything work I will have this dir in /opt instead of /root/tmp). Anyway, once set there I went back into OZWCP and added the device, and it was just working as expected. Set a friendly name and hid some unnecessary stuff and it’s now working from HA.

Very much liking Home Assistant, and looking forward to adding many more thing to it (mostly Zwave stuff, my Sonos, Plex, and would like to try and add my Vine thermostat, aka Symtek TJ610).

1 Like