Copilot
Copilot
Fixes #723 ## Overview Admin 5 no longer supports `custom_m.html` for custom state settings and requires a JSON-based configuration format instead. This PR replaces `custom_m.html` generation with the new `jsonCustom.json`...
This PR implements support for creating TypeScript adapters that run directly without transpilation, leveraging the native TypeScript execution feature added in JS-Controller 3.3 and now stable in JS-Controller 4. ##...
## Problem When using `npx @iobroker/create-adapter`, npm may cache an outdated version of the tool, leading users to unknowingly use old versions with potentially outdated templates or missing features. This...
## Summary This PR addresses a recurring issue during adapter reviews by adding proper `ack` flag handling to the `onStateChange` method in both JavaScript and TypeScript adapter templates. ## Problem...
## Overview Expands the dev-server installation question from a simple yes/no choice to three distinct options, allowing users to choose between global installation, local installation, or no dev-server at all....
Closes #XXX (related to https://github.com/ioBroker/testing/issues/421) ## What Changed Enhanced `.github/create_templates.ts` to execute the actual test scripts of generated adapter templates during CI runs, not just lint and type-check them. ##...
## Overview This PR converts the bug report template from Markdown format to GitHub issue forms (YAML) and adds a new feature request template, following the pattern used in [ioBroker.trashschedule](https://github.com/klein0r/ioBroker.trashschedule/blob/687a05d5cee39534136999d2525a4b27275f64e7/.github/ISSUE_TEMPLATE/bug_report.yml)....
This PR updates the create-adapter templates to use the modern `@iobroker/types` package instead of the deprecated `@types/iobroker` package. ## Changes The implementation follows the pattern used in `@iobroker/adapter-core` to ensure...
This PR addresses all warnings and suggestions identified by the ioBroker Check and Service Bot to ensure the adapter follows current best practices and requirements. ## Changes Made ### Fixed...
This PR fixes an issue where using `getHistory` with `removeBorderValues: true` and `count: 1` would return empty results even when datapoints existed in the database. ## Problem When users specified...