The iobroker.weatherflow_udp from woessmich

Not receiving any data on adapter.

Port 50222 is working through a node-red device but I don't get any data in iobroker with the same port number. No helpful error messages. Running a docker image. Is UPD blocked somehow that I need to open?

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 weatherflow_udp for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.weatherflow_udp

-

ERRORS:

❗ [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '8.0.0' } }" at package.json.
❗ [E033] @iobroker/adapter-core 2.5.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
❗ [E036] @iobroker/testing 2.5.4 specified. 4.1.3 is required as minimum, 4.1.3 is recommended. Please update devDependencies at package.json
❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
❗ [E605] No actual year found in copyright. Please add "Copyright (c) 2024 womi [email protected]" at the end of README.md
❗ [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 womi [email protected]" at the start of LICENSE
❗ [E145] Missing mandatory translation into de of some "common.news" in io-package.json.

WARNINGS:

SUGGESTIONS:

📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

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
@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 Fri, 06 Sep 2024 11:35:21 GMT

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 weatherflow_udp for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.weatherflow_udp

-

ERRORS:

❗ [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '8.0.0' } }" at package.json.
❗ [E033] @iobroker/adapter-core 2.5.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
❗ [E036] @iobroker/testing 2.5.4 specified. 4.1.3 is required as minimum, 4.1.3 is recommended. Please update devDependencies at package.json
❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
❗ [E605] No actual year found in copyright. Please add "Copyright (c) 2024 womi [email protected]" at the end of README.md
❗ [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 womi [email protected]" at the start of LICENSE

WARNINGS:

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 considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

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

State value has to be type "number" but received type "object"

Hello,
since the upgarde to JS 3.3 I'm receiving the following warning message every 5 seconds:
State value to set for "weatherflow_udp.0.xxx.hub_status.timestamp" has to be type "number" but received type "object"

In the Internet I found the following remark for such a message:
Ab Version 3.3 des js-controllers sollen keine Objekte / Arrays mehr in Datenpunkte geschrieben werden, sondern nur noch per JSON.stringify(obj) gewandelte Objekte.
https://forum.iobroker.net/topic/45009/fehler-nach-update-js-controller-3-3-9

Not sure if this helps but at least it looks like that what I observed as well.

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/woessmich/ioBroker.weatherflow_udp

[E605] No actual year found in copyright. Please add "Copyright (c) 2021 womi [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 womi [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Login data / credentials configurable

Could you explain how to configure

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/woessmich/ioBroker.weatherflow_udp

[E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Adapter spams syslog at night

Hey,

I've been using the adapter pretty much since day 1, and it is working fine. There is one inconvenience: At night (with brightness being very low), I keep seeing these messages, one every minute as long as it is dark enough.

I did verify that the messages appear only if

the reported Brightness is 0
the adapter is running.

Jan 3 19:22:09 groenlund bash[17776]: [Groenlund E62D@Tempest@@Current Ambient Light Level] characteristic was supplied illegal value: number 0 exceeded minimum of 0.0001

In winter, these messages alone generate approx. 150 kb data (per Log) in 2 logs:

syslog.log
daemon.log

In order to minimise sd card writes, I would very much like to get rid of them, but looking through the code I could not identify any possible cause.

A.

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

woessmich / iobroker.weatherflow_udp Goto Github PK

iobroker.weatherflow_udp's People

Contributors

Stargazers

Watchers

Forkers

iobroker.weatherflow_udp's Issues

Notification from ioBroker Check and Service Bot

This check is based the current head revisions (master / main branch) of the adapter repository

Notification from ioBroker Check and Service Bot

Recommend Projects

Recommend Topics

Recommend Org