Has anyone noticed the estimated power usage being off by about a factor of ten?
As much as I’d like to think my heat pump can keep my house warm in -20C weather with a mere 3 kWh/day, I know my insulation isn’t that good. 
Hi Brandon,
Are you monitoring both your outdoor unit and indoor unit for consumption? I’ve got GreenEye CTs on both, I live on the West Coast of Canada in an older house. I re-insulated the main attic this past Fall to R28 (was a mix of R12/R7), my heat pump only services my main floor however. I don’t have GreenEye integrated with HA properly yet as I’m waiting on the revamped integration to be complete. I do have it presenting total consumption entities to HA, they just don’t show up in the Energy portion of HA yet. The past 24 hours look like this for me:
My indoor unit (air handler) is an FXTQ36 which is capable of 40,000 BTU of heating and my outdoor unit is an RSXQ48 (49,000BTU).
Do these numbers help you rationalize your power factor at all? Outdoor temperature has been:
I have an IotaWatt sitting at the post office, so I’m hoping I’ll soon be able to get some proper measurements to compare to what the DaikinOne+ is telling me. But your graphs match up well with what I think is going on: the web api reporting decawatts instead of plain watts.
I’m in Nova Scotia, and my One+ is managing my whole-home Fit (DZ17VSA301AA outdoor, DV36FECC14 indoor) 30k BTU unit.
Looking at the past 24h, If I straight multiply the wattages reported I end up with:
I won’t know for sure until I get the clamps on, but it looks like a good start.
Just got this component installed this week after an equipment upgrade switched me from Ecobee to One+. I’m still trying to figure out what is useful vs chaff in the One+ supplied data.
Do any of the sensors tell me the systems’ current state? I want to be able to track how often it turns on and for how long, and over the course of the year how long is it in cool vs heat.
The state tells you the state. There are also attributes that tell you the load for heating and cooling. Some units show power consumption as well.
Has something changed since this was released? I recently got a DaikinOne+ thermostat doesn’t seem to show up anywhere (no error logs), and I can’t add it to the skyportcloud. The thermostat seems to be only pairable with the phone app.
It still uses an older integration method, so you will only see the entities. No integration under Integrations, or devices under Devices. If you’ve configured it properly in your configuration.yaml and you’re not seeing any errors, you should have some entities.
1 Like
I’ve been looking for it in Config > Devices & Services > Entities and they haven’t appeared.
The only thing in the log for ‘daikinskyport’ is the expected “We found a custom integration daikinskyport which has not been tested by Home Assistant”
I’m looking through the docs & code, when I try to hit the endpoint https://api.daikinskyport.com/devices with the proper header, it returns an empty array. This is kind of expected because my thermostat doesn’t show up in skyportcloud.com.
I can’t get my thermostat added there, it simply doesn’t have the option anywhere? When I try to add a thermostat using the ‘6 digit code’ the thermostat gives, it fails. It does mention the app on the thermostat, nothing about Skyport.
Do I need to add my One+ thermostat to Skyport for this to work? If so, how?
3 Likes
Courtesy of a sensor template and the new history-explorer-graph card, I was able to create the tracker I wanted. If anyone needs an example, I documented what I did here:
I think I’m having the same issue. What is the difference between skyport cloud and the DaikinOneHome app? I think you and I are having the same issue here…
I did create a skyport account, but, since I already paired my thermostat with my phone app (which in the thermostat it says online account) it doesn’t seem like I can also now pair it with skyport cloud. Because in order to do this I have to get the 6 digit code which I don’t think I can without unpairing it from my app. And if I had to choose I’d choose the app for wife factor…
2 Likes
similar issue and unsure how to address, have you logged an issue in the GitHub?
1 Like
Hey SmartKyle,
I just wanted to tell you that I just installed and I was initially having your problem, but then it eventually worked. I just wanted you to know that a fellow newbie was successful. I feel like the Daikin cloud services were really slow to initially connect with my thermostat, so I would try time and a couple of restarts, mine seemed to just magically work after a few days.
Thanks everyone who worked on this, the ability to know that I could integrate my new Daikin Fit heat pump was a big comfort for when I had it installed, and this forum gave me that confidence.
2 Likes
This integration does not use Daikin’s OpenAPI; it was reverse engineered from their Android app. I don’t think the OpenAPI has all the same info you can get from the app’s API. It’s at least not documented. The OpenAPI should work just fine, though. I registered a token, but never actually used it since this still works fine.
The integration daikinskyport is using the deprecated forecast attribute. getting this on the latest version of HA
1 Like
I am trying to get this working and am getting the 400 error in the logs.
I have used the curl commands at https://github.com/apetrycki/daikinskyport/blob/2dd7929a6bce02aa90807d98d7e8390f680fbfa5/API_info.md
and the “get bearer token” does return a token.
Everything else i have tried there returns:
{"message":"Unauthorized"}
Anyone have any ideas? I created the skyport account but no info there. So not sure.
Thanks
Tim
1 Like
Having the same issue “{“message”:“Unauthorized”}”. However I don’t think the skyport account is valid for the One+ remotes…created one as well, however its separate from the onecloud account and none of the info on that site matches with the One+ menu structure.
Can you provide more information on the One+ Remote you’re talking about?
Daikin One+ (screen + big silver dial): on the thermostat: Model: ONEPLUS, software version: v.2.8.2
That’s the same thermostat, so it should work. Some have said it takes a couple days for their account to work after creating it. If you can sniff the network traffic for the app, you can see if something has changed. Look for DNS queries from the app and see where it’s trying to hit.
yeah saw that mentioned as well, which might explain why my wife was unable to login to the app on her phone while mine worked directly (first after install). Then again not really seeing the logic why there would be a wait as it’s the same connection. Anyways thanks for responding back and providing this solution if you are running the same thermostat it will likely work (eventually!).