[DEPRECATED] Daikin OnePlus Thermostat Legacy Systems [Incompatible with New API]

Looks like the attribute you want is geofencingAway. Added it to v0.0.8

1 Like

Thanks

The attribute fanCirculateSpeed is always 0, no matter the actual fan speed (low, med, high). The fan speed is normally associated with fan=on (not fanCirculate which seems mean " fan schedule"). I wonder if this could be part of the problem it isn't reading correctly. The API is somewhat vague in this regard:

UPDATE: The enumeration of 0=low. So that makes sense. Is there a way to show the enum in the attribute value?

1 Like

v0.0.9 should change this from the numeric to a string value on the next refresh after update

1 Like

I just had a Daikin One+ Therm installed and am having issues with getting it to integrate with Hubitat. I have everything setup on my wifi, working with the daikin app on my phone and installed the driver in Hubitat. I added my Daikin login username and password. But it's doesn't seem to be connecting and just stays in a pending state. Any thoughts?

Did you request and get the API key?

Yes, and I got a key via email. Do I need to add that to the driver?

Actually not the key but this url in the preferences.

Daikin

And make sure you're using this driver

Daikin OnePlus Single Thermostat

Yep. I have that driver. installed it manually and then using HPM. It defaults to that Server Path and I double checked my log in info. I am getting these logs

Not sure. Let's ping @thebearmay

Love how you just develop a Thermostat driver on a whim at the request of another Community member.... who else would do that.... :wink: Nice work....

3 Likes

Just a thought, did you hit configure and initialize after entering your information?

Yeah, I tried that. I am going to uninstall everything and they try again from the beginning. Will report back.

And the thermostat is registered and controlling the other Daikin equipment ok?

That error is saying that the device initialization failed and the driver doesn’t have the device ID. This usually occurs after you hit the Configure button. Might try re-entering reentering your email and password (make sure both agree in capitalization with what you registered with) clicking off to the side, and then hit Save followed by the Configure button. If successful down in the device Data section you should see an entry for daiID followed by a string value.

1 Like

Speaking of credentials matching I often will find an extra space following a username and/or password on saved credentials.

1 Like

Thanks for all the help. I removed all the drivers, devices and rebooted the hub. Then reinstalled and configured everything again. All is working! Thanks again and thanks for such a great driver.

2 Likes

@thebearmay I've had this work for over a year, but now Daikin cloud is returning gigantic JSON data strings that are causing hubitat to slow down whenever a refesh occurs. Have you noticed this? The strings include all sorts of internal parameters that I don't think Daikin wants to be giving out. So maybe it's a Daikin mistake that they haven't noticed yet. It's very strange.

Don't have a device, so not running the app on a regular basis. Can you PM a sample of the return, depending on what is coming back I may be able to change the parsing logic to gain some efficiency (probably not but doesn't hurt to look(

1 Like