Closed galak closed 2 years ago
Thanks for that. I've compared it with my own file and it's not all that different. You have 'unconfigured': True,
and I have a non-None unitType
though.
I don't have a KumoStation to verify what those look like. Maybe @brgaulin can chime in here. What we need is to be able to distinguish valid indoor units like this one from the KumoStation units. unitType
seems good when it works, but evidently we need something else too -- maybe if the unit has a non-empty fan_speed_stages
in reportedProfile
? That would indicate it's at least a device that moves air.
Thanks for that. I've compared it with my own file and it's not all that different. You have
'unconfigured': True,
and I have a non-NoneunitType
though.
I tried re-configuring the unit with Kumo App yesterday, and got pretty much the same JSON. Not sure what the unconfigured: True
is coming from. Odd that this changed recently. In the Kumo App it shows the unit as 'Ducted' which is clearly not correct. Do you have any older JSON dumps? Wondering if something new/different with a newer firmware version (what firmwareVersion do you have) ?
Do you mind posting your sanitized JSON?
I don't have a KumoStation to verify what those look like. Maybe @brgaulin can chime in here. What we need is to be able to distinguish valid indoor units like this one from the KumoStation units.
unitType
seems good when it works, but evidently we need something else too -- maybe if the unit has a non-emptyfan_speed_stages
inreportedProfile
? That would indicate it's at least a device that moves air.
Would be nice to see a JSON dump for the KumoStation case.
Here's the dump of my json output. Reporting unitType: mvz
kumo_cache.json.txt
From the https://community.home-assistant.io/t/mitsubishi-kumo-cloud-integration/121508/368 chain:
For the unit with unitType of mvz, what does that represent in your installation?
Not sure I understand the question, but I have but one single zone indoor central ducted unit.
Apologies if this is unrelated, upgrading to 3.0a today in HACs broke my dashboards, reverting to 2.8 brought them back. I have a 5 ton MXZ VRF system with 5 air handlers, unitTypes are an mvz, 3 of sez and a pead. I have the wall temp sensors, no thermostats. The JSON file was updated 6/4/22. kumo_cache.json.txt
Apologies if this is unrelated, upgrading to 3.0a today in HACs broke my dashboards, reverting to 2.8 brought them back.
I ran into a similar issue when updating to 0.3.0a. I could see the data being retrieved for my SVZ air handler, but no associated entity was created.
@J-T-W and @EricE thanks for those. I'd still like to see what a kumo_cache.json looks like in a system with a Kumo Station, but it seems to me that looking for units with fan_speed_stages
will cover all the cases reported in this thread. If a unit has fan speed stages it's very likely to be a head unit of some kind so I think this is a decent solution.
Hmm examining the code more closely it's easier than that: it's already assuming in one spot that unidentified units are indoor units. It's just when retrieving the list of indoor units, it's making a different assumption.
@galak @J-T-W @EricE please update your pykumo library to v0.2.3 (pushed today) and report back if that fixes the problem for you. Assuming it does I'll make a new hass-kumo release to pick it up.
Sorry if I', being dense here - what files under HA's .\ config\custom_components\kumo am I to download and replace?
If you don't know how to upgrade a Python package manually in whatever install type you have, you can edit manifest.json to require 0.2.3 ("requirements": ["pykumo==0.2.3"],
) and restart HA.
Updated file, restarted HA, and now climate
object is back and reporting as expected.
Looks like 0.2.3 works for me.
Great, thanks guys. I have tagged a new version of hass-kumo for HACS and am closing this issue.
Here's dump of my json output in which it's reporting
'unitType': None
. Not seeing anything obvious w/regards to determine its aductless
unit.