-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Issue
Skyport accounts with multiple thermostats in a home result in the integration adding all systems in the home to a single HA device instead of creating separate devices for each system.
Desired Outcome
Separate HA devices should be created per thermostat.
As a point of discussion, I think we may want to consider going further and creating separate devices for each component of the system, e.g. thermostats, air handlers, heat pumps. Doing so might provide better clarity regarding some of the sensors such as power draw instead of solely relying on the indoor/outdoor naming. The may not be feasible depending on the Skyport API schema though. Assuming we can see equipment serials and the API data structures provide clean association between entity data sources and equipment serials, then I'd propose creating a new HA devices per serial and associated the respective entities to each device.
More Information
We have a two story house with separate downstairs and upstairs HVAC units. The upstairs unit was replaced with a Daikin FIT unit a couple years back, and we started using this integration at that time. Fast forward and we have now replaced the downstairs unit with a second Daikin FIT unit. After added the new thermostat to the SkyportHome app and reloading the integration within Home Assistant, the new HA entities were successfully created. However, these HA entities for the new system were surprisingly added to the existing HA device for the upstairs system instead of creating a second HA device for the new system.
Downstairs system:
- Thermostat: ONETOUCH
- Heat Pump: DH6VSA2410
- Air Handler: DFVE24BP1300AA
Upstairs system:
- Thermostat: ONEPLUS
- Heat Pump: DZ17VSA181AA
- Air Handler: DV24FECB14AA
Happy to provide any other data that would be beneficial.