{"id":15140401,"url":"https://github.com/clemlatz/homebridge-tiko","last_synced_at":"2026-01-20T02:47:10.656Z","repository":{"id":214722649,"uuid":"736364036","full_name":"clemlatz/homebridge-tiko","owner":"clemlatz","description":"Homebridge plugin to integrate Tiko / Mon Pilotage Elec devices into HomeKit","archived":false,"fork":false,"pushed_at":"2024-02-26T17:30:02.000Z","size":411,"stargazers_count":1,"open_issues_count":1,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-09-23T03:53:21.774Z","etag":null,"topics":["engie","homebridge","homebridge-plugins","homebridge-tiko","homekit","mon-pilotage-elec","siri","tiko"],"latest_commit_sha":null,"homepage":"","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/clemlatz.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":".github/FUNDING.yml","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null},"funding":{"custom":"https://fund.clemlatz.dev"}},"created_at":"2023-12-27T17:36:24.000Z","updated_at":"2025-06-20T14:13:27.000Z","dependencies_parsed_at":"2024-09-12T03:30:45.624Z","dependency_job_id":"094e2a21-27c2-498a-b47a-816fef727d93","html_url":"https://github.com/clemlatz/homebridge-tiko","commit_stats":null,"previous_names":["clemlatz/homebridge-tiko"],"tags_count":11,"template":false,"template_full_name":"homebridge/homebridge-plugin-template","purl":"pkg:github/clemlatz/homebridge-tiko","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/clemlatz%2Fhomebridge-tiko","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/clemlatz%2Fhomebridge-tiko/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/clemlatz%2Fhomebridge-tiko/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/clemlatz%2Fhomebridge-tiko/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/clemlatz","download_url":"https://codeload.github.com/clemlatz/homebridge-tiko/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/clemlatz%2Fhomebridge-tiko/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28594958,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-20T02:08:49.799Z","status":"ssl_error","status_checked_at":"2026-01-20T02:08:44.148Z","response_time":117,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["engie","homebridge","homebridge-plugins","homebridge-tiko","homekit","mon-pilotage-elec","siri","tiko"],"created_at":"2024-09-26T08:20:25.305Z","updated_at":"2026-01-20T02:47:10.639Z","avatar_url":"https://github.com/clemlatz.png","language":"TypeScript","funding_links":["https://fund.clemlatz.dev"],"categories":[],"sub_categories":[],"readme":"\u003cp align=\"center\"\u003e\n   \u003ca href=\"https://github.com/clemlatz/homebridge-tiko\"\u003e\u003cimg alt=\"homebridge-tiko logo\" src=\"homebridge-tiko.png\" width=\"600px\"\u003e\u003c/a\u003e\n\u003c/p\u003e\n\n\u003cspan align=\"center\"\u003e\n\n# homebridge-tiko\n\nHomebridge plugin to integrate [Tiko](https://www.tiko.fr) / [Mon Pilotage Elec](https://particuliers.engie.fr/landing/mon-pilotage-elec-sea.html) devices into HomeKit\n\n[![npm](https://img.shields.io/npm/v/homebridge-tiko/latest?label=latest)](https://www.npmjs.com/package/homebridge-tiko)\n[![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)\n[![build status](https://github.com/clemlatz/homebridge-tiko/actions/workflows/build.yml/badge.svg)](https://github.com/clemlatz/homebridge-tiko/actions/workflows/build.yml)\n[![npm](https://img.shields.io/npm/dt/homebridge-tiko)](https://www.npmjs.com/package/homebridge-tiko)\n\n\u003c/span\u003e\n\n## Plugin Information\n\nThe **homebridge-tiko** plugin allows you to control Tiko-connected heaters\nusing Siri or the Apple Home app, by connecting the [Tiko](https://www.tiko.fr)\n(a.k.a. [Mon Pilotage Elec](https://particuliers.engie.fr/landing/mon-pilotage-elec-sea.html))\nplatform to HomeKit through Homebridge.\n\nThis plugin allows you to do the following using Siri \nor the Home app on an iPhone, an iPad, an Apple Watch or a Mac:\n- Display current and target temperature for each room\n- Set target temperature for each room\n- Put a heater in \"frost\", \"absence\", \"boost\" or scheduled mode\n\n### ![French flag](france.png) \u0026nbsp;Vous parlez français ?\n[Guide d'installation et de configuration du plugin en français](https://blog.clemlatz.dev/blog/gerer-ses-radiateurs-tiko-avec-siri-et-apple-home/)\n\n## Prerequisites\n\n- To use this plugin, you will need to already have:\n  - [Node](https://nodejs.org): latest version of `v18` or `v20` - any other major version is not supported.\n  - [Homebridge](https://homebridge.io): `v1.6` - refer to link for more information and installation instructions.\n\n## Usage\n\nTiko modes cannot be displayed in the Home app because Homekit thermostat's state cannot be personalised.\nHere's the equivalence between an HomeKit instruction and a Tiko state:\n\n| Apple Home instruction | Tiko mode                |\n|------------------------|--------------------------|\n| Off (Éteint)           | Frost (Hors-gel)         |\n| Cool (Refroidir)       | Absence                  |\n| Heat (Chauffer)        | Boost                    |\n| Auto (Autom.)          | Schedule (Programmation) |\n\n## Setup\n\n1. [Install and configure Homebridge](https://github.com/homebridge/homebridge/wiki)\n2. Search for \"homebridge-tiko\" in Homebridge's \"Plugins\" tab\n3. Install plugin\n4. Configure plugin by filling login (e-mail) and password\n\n### Optional `endpoint` option\n\nEndpoint defaults to `https://particuliers-tiko.fr/api/v3/graphql/` but can be changed to\nanother url (eg. https://portal-engie.tiko.ch/api/v3/graphql/).\n\n### Optional `propertyId` option\n\nIf your Tiko account is linked to multiple properties, homebridge-tiko\nwill use the first property by default. You can specify another property id\nusing the `propertyId` option.\n\nYou can find the correct property id in the Tiko dashboard url:\n\n```\nhttps://particuliers-tiko.fr/dashboard/{propertyId}\n```\n\n## Acknowledgments\n\nSpecial thanks to [paulchartres](https://github.com/paulchartres) whose project [hass-tiko](https://github.com/paulchartres/hass-tiko/tree/master) helped \nme a lot to understand Tiko's Api without doing a lot of retro-engineering.\n\n## Development documentation\n\n### Setup Development Environment\n\nTo develop Homebridge plugins you must have Node.js 18 or later installed, and a modern code editor such as [VS Code](https://code.visualstudio.com/). This plugin template uses [TypeScript](https://www.typescriptlang.org/) to make development easier and comes with pre-configured settings for [VS Code](https://code.visualstudio.com/) and ESLint. If you are using VS Code install these extensions:\n\n- [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)\n\n### Install Development Dependencies\n\nUsing a terminal, navigate to the project folder and run this command to install the development dependencies:\n\n```shell\nnpm install\n```\n\n### Update package.json\n\nOpen the [`package.json`](./package.json) and change the following attributes:\n\n- `name` - this should be prefixed with `homebridge-` or `@username/homebridge-`, is case-sensitive, and contains no spaces nor special characters apart from a dash `-`\n- `displayName` - this is the \"nice\" name displayed in the Homebridge UI\n- `repository.url` - Link to your GitHub repo\n- `bugs.url` - Link to your GitHub repo issues page\n\nWhen you are ready to publish the plugin you should set `private` to false, or remove the attribute entirely.\n\n### Update Plugin Defaults\n\nOpen the [`src/settings.ts`](./src/settings.ts) file and change the default values:\n\n- `PLATFORM_NAME` - Set this to be the name of your platform. This is the name of the platform that users will use to register the plugin in the Homebridge `config.json`.\n- `PLUGIN_NAME` - Set this to be the same name you set in the [`package.json`](./package.json) file. \n\nOpen the [`config.schema.json`](./config.schema.json) file and change the following attribute:\n\n- `pluginAlias` - set this to match the `PLATFORM_NAME` you defined in the previous step.\n\n### Build Plugin\n\nTypeScript needs to be compiled into JavaScript before it can run. The following command will compile the contents of your [`src`](./src) directory and put the resulting code into the `dist` folder.\n\n```shell\nnpm run build\n```\n\n### Link To Homebridge\n\nRun this command so your global installation of Homebridge can discover the plugin in your development environment:\n\n```shell\nnpm link\n```\n\nYou can now start Homebridge, use the `-D` flag, so you can see debug log messages in your plugin:\n\n```shell\nhomebridge -D\n```\n\n### Watch For Changes and Build Automatically\n\nIf you want to have your code compile automatically as you make changes, and restart Homebridge automatically between changes, you first need to add your plugin as a platform in `~/.homebridge/config.json`:\n```\n{\n...\n    \"platforms\": [\n        {\n            \"name\": \"Config\",\n            \"port\": 8581,\n            \"platform\": \"config\"\n        },\n        {\n            \"name\": \"\u003cPLUGIN_NAME\u003e\",\n            //... any other options, as listed in config.schema.json ...\n            \"platform\": \"\u003cPLATFORM_NAME\u003e\"\n        }\n    ]\n}\n```\n\nand then you can run:\n\n```shell\nnpm run watch\n```\n\nThis will launch an instance of Homebridge in debug mode which will restart every time you make a change to the source code. It will load the config stored in the default location under `~/.homebridge`. You may need to stop other running instances of Homebridge while using this command to prevent conflicts. You can adjust the Homebridge startup command in the [`nodemon.json`](./nodemon.json) file.\n\n### Customise Plugin\n\nYou can now start customising the plugin template to suit your requirements.\n\n- [`src/platform.ts`](./src/platform.ts) - this is where your device setup and discovery should go.\n- [`src/platformAccessory.ts`](./src/platformAccessory.ts) - this is where your accessory control logic should go, you can rename or create multiple instances of this file for each accessory type you need to implement as part of your platform plugin. You can refer to the [developer documentation](https://developers.homebridge.io/) to see what characteristics you need to implement for each service type.\n- [`config.schema.json`](./config.schema.json) - update the config schema to match the config you expect from the user. See the [Plugin Config Schema Documentation](https://developers.homebridge.io/#/config-schema).\n\n### Versioning Your Plugin\n\nGiven a version number `MAJOR`.`MINOR`.`PATCH`, such as `1.4.3`, increment the:\n\n1. **MAJOR** version when you make breaking changes to your plugin,\n2. **MINOR** version when you add functionality in a backwards compatible manner, and\n3. **PATCH** version when you make backwards compatible bug fixes.\n\nYou can use the `npm version` command to help you with this:\n\n```shell\n# major update / breaking changes\nnpm version major\n\n# minor update / new features\nnpm version update\n\n# patch / bugfixes\nnpm version patch\n```\n\n### Publish Package\n\nWhen you are ready to publish your plugin to [npm](https://www.npmjs.com/), make sure you have removed the `private` attribute from the [`package.json`](./package.json) file then run:\n\n```shell\nnpm publish\n```\n\nIf you are publishing a scoped plugin, i.e. `@username/homebridge-xxx` you will need to add `--access=public` to command the first time you publish.\n\n#### Publishing Beta Versions\n\nYou can publish *beta* versions of your plugin for other users to test before you release it to everyone.\n\n```shell\n# create a new pre-release version (eg. 2.1.0-beta.1)\nnpm version prepatch --preid beta\n\n# publish to @beta\nnpm publish --tag=beta\n```\n\nUsers can then install the  *beta* version by appending `@beta` to the install command, for example:\n\n```shell\nsudo npm install -g homebridge-example-plugin@beta\n```\n\n### Best Practices\nConsider creating your plugin with the [Homebridge Verified](https://github.com/homebridge/verified) criteria in mind. This will help you to create a plugin that is easy to use and works well with Homebridge.\nYou can then submit your plugin to the Homebridge Verified list for review.\nThe most up-to-date criteria can be found [here](https://github.com/homebridge/verified#requirements).\nFor reference, the current criteria are:\n\n- The plugin must successfully install.\n- The plugin must implement the [Homebridge Plugin Settings GUI](https://github.com/oznu/homebridge-config-ui-x/wiki/Developers:-Plugin-Settings-GUI).\n- The plugin must not start unless it is configured.\n- The plugin must not execute post-install scripts that modify the users' system in any way.\n- The plugin must not contain any analytics or calls that enable you to track the user.\n- The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.\n- The plugin must be published to npm and the source code available on GitHub.\n  - A GitHub release - with patch notes - should be created for every new version of your plugin.\n- The plugin must run on all [supported LTS versions of Node.js](https://github.com/homebridge/homebridge/wiki/How-To-Update-Node.js), at the time of writing this is Node.js v16 and v18.\n- The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.\n- If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.\n\n### Useful Links\nNote these links are here for help but are not supported/verified by the Homebridge team\n- [Custom Characteristics](https://github.com/homebridge/homebridge-plugin-template/issues/20)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fclemlatz%2Fhomebridge-tiko","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fclemlatz%2Fhomebridge-tiko","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fclemlatz%2Fhomebridge-tiko/lists"}