ax-led / iobroker.powerfox2 Goto Github PK

Ich habe einen poweropti am Wärmezähler. Der Adapter erkennt diesen fälschlich als Stromzähler und liefert dadurch keine Werte. In der API wird die "Division" korrekt übergeben, aber anscheinend wertet der Adapter das nicht korrekt aus.

Powerfox versucht sich zu verbinden , aber bekommt keine .
Diese Meldung kommt immer

`instance system.adapter.powerfox2.0 already running with pid 1841…

`
Über das App funktioniert alles

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version:
• JS-Controller version:
• Node version:
• Operating system:

Additional context
Add any other context about the problem here.

error message in log file "instance system.adapter.powerfox2.0 already running with PID ".
Looks like a running instance does not get a proper response from the server and remains active.
see log below - PID 2145 started at 21:44, but does not receive a "status:200".
Tries to start again at 21:45 which fails.

Happens from time to time, about every x days.

As long as process is not killed manully (kill -9 ), no further requests will be processed successfully, causing missing data.

log details:
2023-04-14 21:44:02.538 - �[32minfo�[39m: powerfox2.0 (2145) starting. Version 0.0.12 in /opt/iobroker/node_modules/iobroker.powerfox2, node: v14.20.0, js-controller: 4.0.23
2023-04-14 21:44:02.567 - �[34mdebug�[39m: powerfox2.0 (2145) powerfox2 instance started.
2023-04-14 21:44:02.568 - �[34mdebug�[39m: powerfox2.0 (2145) Email: [email protected]
2023-04-14 21:44:02.569 - �[34mdebug�[39m: powerfox2.0 (2145) powerfox2 devices:{"name":"9c9c1fxxxxxx","aws":1659xxxxxx,"active":true}
2023-04-14 21:44:02.570 - �[34mdebug�[39m: powerfox2.0 (2145) device name:9c9c1fxxxxxx
2023-04-14 21:44:02.570 - �[34mdebug�[39m: powerfox2.0 (2145) device active:true
2023-04-14 21:44:02.571 - �[34mdebug�[39m: powerfox2.0 (2145) device aws:1659xxxxxx
2023-04-14 21:44:02.571 - �[34mdebug�[39m: powerfox2.0 (2145) device url:https://backend.powerfox.energy/api/2.0/my/9c9c1fxxxxxx/current
2023-04-14 21:44:02.689 - �[35msilly�[39m: powerfox2.0 (2145) States system redis pmessage system.adapter.powerfox2.0.logLevel/system.adapter.powerfox2.0.logLevel:{"val":"silly","ack":true,"ts":1681501442657,"q":0,"from":"system.adapter.powerfox2.0","lc":1681142282926}
2023-04-14 21:45:00.004 - �[33mwarn�[39m: host.iob instance system.adapter.powerfox2.0 already running with pid 2145

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!

As it now happened several times on my installation that there was no response but open http request to powerfox (which caused that the next request was not able as old process still alive) it would be great to add the timeout feature to the axios request to "kill it":
timeout: x

like:
await axios({
method: 'post',
url: '/',
timeout: 10000 // only wait for 10s
})

Ideally the timeout is configurable in Admin UI (or e.g. alternatively set to 10000?)

thx
Norbert

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/Ax-LED/ioBroker.powerfox2

• [E405] Icon must be in the following path: https://raw.githubusercontent.com/Ax-LED/ioBroker.powerfox2/main/
• [E407] Meta URL(latest) must be equal to https://raw.githubusercontent.com/Ax-LED/ioBroker.powerfox2/main/io-package.json

I have also found warnings that may be fixed if possible.

• [W801] .npmignore not found

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