Check that a Daikin SkyportHome developer API key and integration token work, see every
thermostat on the account with its live readings, then generate a QuickServer
config.json and config.csv for them.
curl commands
for you to run in a terminal on your own computer; you paste the output back here.
Every command only reads — none can change a thermostat. Nothing you type is saved.
The commands contain the API key and integration token: do not paste them into tickets,
email or chat.
Need the keys? Download the Chipkin guide How to get the Daikin Developer API key and integration token (PDF, 2 MB) — both come from the Daikin One Home app.
Enter the credentials
Check the developer API key
This sends the key with a deliberately fake token. A good key gets past Daikin's front door and is then refused for the token; a bad key is refused at the door.
Check the email and integration token
List the thermostats
Access tokens last about 15 minutes, so this command gets a fresh one itself before asking for the list.
Read every thermostat
One command reads them all. Temperatures are in °C.
Generate the QuickServer configuration
Output is for QuickServer firmware .
Project
Writes to Daikin
Untick for a monitor-only site: config.json gets no write driver
(httpTriggerDriver) and every point is published read-only.
Building-side protocols
Turn on any mix. Every protocol publishes the same values.
Thermostats
The tag is the short name used in every point name
(DA_<tag>, <tag>_Temp_Indoors): up to 7 letters or digits, unique.
| Include | Thermostat | Location | Tag | Indoor °C |
|---|
Extra points
The thermostats also report these values, which the standard 18-point map does not include. Ticked extras are added as read-only points.
config.json and config.csv. Import it as is on the
QuickServer's configuration page; there is no need to unzip it. config.json contains
the API key and integration token, so treat the file like a password.