arteck
Please consider fixing issues detected by repository checker
Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter fullybrowser for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main branch) of the adapter repository
Please see the result of the check below.
ioBroker.fullybrowser
- 
ERRORS:
- [ ] :heavy_exclamation_mark: [E157] admin 6.0.0 listed as dependency but 6.17.14 is required as minimum, 7.4.10 is recommended. Please update globalDependency at io-package.json.
- [ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,sm,md,lg,xl] for password at admin/jsonConfig.json/items/_tab_Start/mqttPassword
- [ ] :heavy_exclamation_mark: [E511] invalid size attributes "md":"16" for staticText at admin/jsonConfig.json/items/_tab_Start/text_MQTT-info. Value must be 1 to 12.
- [ ] :heavy_exclamation_mark: [E511] invalid size attributes "sm":"16" for staticText at admin/jsonConfig.json/items/_tab_Start/text_MQTT-info. Value must be 1 to 12.
- [ ] :heavy_exclamation_mark: [E511] invalid size attributes "xs":"16" for staticText at admin/jsonConfig.json/items/_tab_Start/text_MQTT-info. Value must be 1 to 12.
- [X] :heavy_exclamation_mark: [E804] Please process issue [#256] "Compatibility check and testing for node.js 22"
WARNINGS:
- [ ] :eyes: [W508] attribute "xs" for staticText should specify a value of "12" at admin/jsonConfig.json/items/_tab_Start/text_MQTT-info
SUGGESTIONS:
- [ ] :pushpin: [S184] "common.singletonHost" detected for non onlyWWW adapter. Is this really desired?
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users. Let's work together for the best user experience.
your ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Thu, 17 Apr 2025 20:55:47 GMT based on commit a2e6dffc96111991a33413d808607b7d83c6d1f6 ioBroker.repochecker 3.5.4
This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed [E804] Please process issue [#256] "Compatibility check and testing for node.js 22"
:thumbsup:Thanks for fixing the issues.
This issue has been updated by ioBroker Check and Service Bot
The following issues are new and have been added [W028] Minimum node.js version 20 recommended. Please adapt "{'engines' : { 'node' >= '18' } }" at package.json. [W037] @iobroker/adapter-dev 1.3.0 specified. 1.4.0 is recommended. Please consider updating devDependencies at package.json [W037] @iobroker/testing 5.0.0 specified. 5.0.4 is recommended. Please consider updating devDependencies at package.json
Thanks for processing and closing this issue.
I will recheck for new issues later. So it's no problem if this issue has been closed premature.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged. Let's work together for the best user experience.
your
ioBroker Check and Service Bot