apollon77 / iobroker.nut

NUT (network UPS Tools) Adapter for ioBroker

ioBroker.nut

This adapter for ioBroker connects to a defined NUT server to provide the status and details of a connected UPS/USV as ioBroker states, so that it can be used there.

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Description of parameters

host_ip

IP address of the NUT server. NUT needs to run in server mode and needs to be accessible by the computer the iobroker NUT adapter runs on. So check firewall settings if you have problems and allow the access. If the UPS is connected locally you can also use 127.0.0.1 or localhost.

host_port

Port of NUT. The default port is 3493

ups_name

Name of the UPS as defined in the NUT configuration of the NUT server.

Hints:

• If you want to connect to an UPS connected to a Synology diskstation the name is simply "ups".
• If you want to connect to an UPS connected to a QNAP NAS the name is simply "qnapups".

update_interval

Interval in Seconds to update the data. Default is 300s

UPS-Monitor Notifies

Included is a small linux shell-script at scripts/nut-notify.sh which can be configured in upsmon.

The script needs execute rights (chmod +x nut-notify.sh).

It should be added to /etc/nut/upsmon.conf like:

NOTIFYCMD "cd /opt/iobroker/;./nut-notify.sh"

Additionally configure all relevant notify messages like:

NOTIFYFLAG ONLINE       SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT       SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT      SYSLOG+WALL+EXEC
NOTIFYFLAG FSD          SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK       SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD      SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN     SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT     SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM       SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT     SYSLOG+WALL+EXEC

Important is the added "EXEC" flag.

One simple example for a nut-notify.sh script is:

#! /bin/sh
# NUT adapter notify script.

logger -t nut-notify "Notify iobroker $UPSNAME -> $NOTIFYTYPE"
/opt/iobroker/iobroker message nut notify "{\"upsname\":\"$UPSNAME\",\"notifytype\":\"$NOTIFYTYPE\"}"

Troubleshooting

If you have problems and the adapter do not deliver the data you can use the two scripts in directory "test" of the adapter installation (so normally in node_modules/iobroker.nut/test relative to your iobroker installation directory) to try it out on the commandline. Call the scripts using "node filename.js" to see the awaited parameters.

• test_upslist.js: Connects to the NUT server and returns a list of available UPS names
• test_upsvars.js: Connects to the NUT server for a defined UPS and returns a list of available UPS variables

Todo

• docs for webpage

Changelog

1.6.0 (2022-12-09)

• IMPORTANT: js-controller 3.0 is now needed at least
• (Apollon77) Delay adapter initialization when USV is not reachable on adapter start

1.5.1 (2022-02-19)

• (simatec) jsonConfig added
• (simatec) test and release updated

1.5.0 (2021-05-08)

• (Apollon77) Add connection states
• (Apollon77) Optimize for js-controller 3.3
• (foxriver76) we fixed the state value type set to battery.charge

1.4.3 (2021-02-04)

• (Apollon77) Enhance the port check

1.4.2 (2021-01-23)

• (Apollon77) Check configured port before using it (Sentry IOBROKER-NUT-3)

1.4.1 (2021-01-21)

• (Apollon77) Optimize stop handling (Sentry IOBROKER-NUT-1)

1.4.0 (2021-01-14)

• (Apollon77) Prevent warnings in js-controller 3.2
• (Apollon77) Require at least js-controller 2.0

1.3.0 (2020-12-27)

• (Apollon77) adjust connection close handling
• (Apollon77) add compact mode

1.2.0 (2020-12-26)

• (Apollon77) update dependencies
• (Apollon77) Add Sentry error reporting

1.1.3 (2018-04-13)

• Fix Admin

1.1.2 (2018-03-28)

• Fix status parsing

1.1.1

• Enhance error handling

1.1.0

• Add possibility to call commands on the UPS

1.0.0

• change mode from schedule to deamon
• implement message support to receive messages from upsmon
• add status.severity to get one status about the USV with values idle, operating, operating_critical, action_needed, unknown

0.3.0

• add better usable status states under "status" channel

0.2.1

• finalizied initial version

0.1.0

• initial release for testing

License

The MIT License (MIT)

Copyright (c) 2016-2022 Apollon77 [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.nut's Issues

No or wrong info after click "?" for Adapter Info

Hi Ingo,

allready discussed at https://forum.iobroker.net/viewtopic.php?f=36&t=3253&start=60#p138011

Maybe same problem as for Smartmeter Adapter : Apollon77/ioBroker.smartmeter#11 !?

Br

Please check ioBroker.nut with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

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!

Release script: Action required

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

Log info

Hallo,

ist es möglich die Infomeldung:

nut.0 | 2019-12-01 13:16:25.002 | info | (4210) All Nut values set
nut.0 | 2019-12-01 13:16:24.890 | info | (4210) Start NUT update

die mit dem Aktualisierungsintervall von 300s immer im Log steht auf einem andere Log-Stufe zu verschieben? Ich finde das diese Meldung nicht alle 300s im Log stehen muss.

Datenabfrageintervall

Hallo, ich habe mein USV über ioBroker laufen,
und habe keine clients intalliert auf anderen Rechnern.

Ich fahre die Rechner per ssh herunter, je nach Akkus stand der USV.

Was richtig gut wäre, wenn man das Pollingintervall per Datenpunkt steuern könnte,
sodass wenn das USV auf Batteriebetrieb umschaltet, man es in geringeren Abständen abfragen kann.

Ich hoffe Ihr haltet das auch für eine gute Idee...

Support info.connection in state traffic light of instance

Is your feature request related to a problem? Please describe.
Currently the nut adapter does not display the connection state in the instance state traffic light. Thus the state of the adapter is green even if it has no connection to the nut server. This problem occurs on start or restart of the adapter (see log in Additional context below) as well as in situations where the adapter looses connection to the nut server after some time. Thus it can happen that connection losses go by unnoticed for a long time with resultant data loss.

Describe the solution you'd like
If the adapter is not able to connect to the nut server or looses the connection, the state traffic light of the instance should be turned yellow (as defined in the iobroker adapter developers documentation) and not turn or stay green.
This should be signalled via the object: info.connection which is defined in io-packages.json
and subsequently changed in the adapter according to the current connection state.

Describe alternatives you've considered
None

Additional context
`nut.0 2021-04-16 12:26:45.198 error (15034) Error happend: Error: connect ECONNREFUSED 192.168.1.XXX:3493

nut.0 2021-04-16 12:26:45.014 info (15034) starting. Version 1.4.3 in /opt/iobroker/node_modules/iobroker.nut, node: v12.21.0, js-controller: 3.2.16

host.xxxxxx-iob 2021-04-16 12:26:42.258 info instance system.adapter.nut.0 started with pid 15034`

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/Apollon77/ioBroker.nut

• [E114] No adapter are allowed in the repo without admin3 support
• [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2022 Ingo Fischer [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2022 Ingo Fischer [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

Probleme mit Nut unter windows 10

Moin,

ich hab den Nut dienst unter win 10 laufen aber der adapter schmeißt nach dem start folgende meldung aus und
folglich auch keine Meldung.

`

nut.0	2021-03-21 12:40:41.270	error	(1244) Err while getting NUT values: DATA-STALE
nut.0	2021-03-21 12:40:41.258	error	(1244) Err while getting all commands: DATA-STALE
nut.0	2021-03-21 12:40:41.171	info	(1244) starting. Version 1.4.3 in C:/ioBroker neu/SmartHome/node_modules/iobroker.nut, node: v10.17.0, js-controller: 3.1.6
host.ioBroker(SmartHome)	2021-03-21 12:40:36.765	info	instance system.adapter.nut.0 started with pid 1244

`

Update stable version in repo from 1.5.0 to 1.5.1

Think about update stable version to 1.5.1

Version: stable=1.5.0 (303 days old) => latest=1.5.1 (15 days old)
Installs: stable=1290 (76.83%), latest=283 (16.86%), total=1679
Click to edit

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

• #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

• #3766: Make reporter constructor support optional options parameter (@plroebuck)
• #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

• #3719: Deprecate this.skip() for "after all" hooks (@juergba)

🐛 Fixes

• #3829: Use cwd-relative pathname to load config file (@plroebuck)
• #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
• #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

• #3848: Fix Suite cloning by copying root property (@fatso83)
• #3816: Guard against undefined timeout option (@boneskull)
• #3814: Update "yargs" in order to avoid deprecation message (@boneskull)
• #3788: Fix support for multiple node flags (@aginzberg)

📖 Documentation

• mochajs/mocha-examples: New repository of working examples of common configurations using mocha (@craigtaub)
• #3850: Remove pound icon showing on header hover on docs (@jd2rogers2)
• #3812: Add autoprefixer to documentation page CSS (@Munter)
• #3811: Update doc examples "tests.html" (@DavidLi119)
• #3807: Mocha website HTML tweaks (@plroebuck)
• #3793: Update config file example ".mocharc.yml" (@cspotcode)

🔩 Other

• #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
• #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)

Commits

The new version differs by 28 commits.

• f4fc95a Release v6.1.0
• bd29dbd update CHANGELOG for v6.1.0 [ci skip]
• aaf2b72 Use cwd-relative pathname to load config file (#3829)
• b079d24 upgrade deps as per npm audit fix; closes #3854
• e87c689 Deprecate this.skip() for "after all" hooks (#3719)
• 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
• 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
• 586bf78 Update JS-YAML to address security issue (#3845)
• d1024a3 Update doc examples "tests.html" (#3811)
• 1d570e0 Delete "/docs/example/chai.js"
• ade8b90 runner.js: "self.test" undefined in Browser (#3835)
• 0098147 Replace findup-sync with find-up for faster startup (#3830)
• d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
• a3089ad update package-lock
• 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Deactivate Log entry on update

It would be nice to offer a checkbox in the configuration to enable or disable the log entries on update ('Start NUT update' & 'All Nut values set')!
Reason: When setting the update interval very short (30-60 sec) you'll get more than thousand log entries per day which is not needed in my opinion.

Etaon USV Ellipse 1200 ECO Ordner Status

Wie oben geschrieben, habe ich folgende USV:
Eaton Ellipse 1200 Eco
Treiber: usbhid-ups Version 2.7.4

Im Ordner Status bleibt bei mir leider alles auf false, oder Error.

Vielleicht wenn du mal Zeit hättest wäre hier was möglich, wäre cool wenn das Boosting, charging, discharging usw auch gefüllt werden. Danke dir.

Make adapter ready for Admin v3

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

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!

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/Apollon77/ioBroker.nut

• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: Network UPS Adapter
• [E109] desc in io-package.json should be an object for many languages. Found only Read all data from your UPS/USV via nut protocol
• [E114] No adapter are allowed in the repo without admin3 support
• [E802] No topics found in the repository. Please go to "https://github.com/Apollon77/ioBroker.nut", press the settings button beside the about title and add some topics.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2021 Ingo Fischer [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2021 Ingo Fischer [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

Verbosity level

Hi,
just something minor: I get flooded (compared to all other adapters I run) by these messages (every 90s):

2019-01-04 00:01:22.792  - info: nut.0 Start NUT update
2019-01-04 00:01:22.801  - info: nut.0 All Nut values set

Would you consider lowering the verbosity level to "debug" on these two messages? I usually get a few messages per hour on level info but it is important for me to monitor the UPS quite close so I need to have 90s set.

connect EHOSTUNREACH

The adapter has stopped working. I get the following error in the log:
(29087) Error happend: Error: connect EHOSTUNREACH 192.168.1.38:3493
my version of DSM 6.2-23739
Internet searches have led to this page, but failed to verify everything described there (connection via telnet).

---

System data:

Platform: linux
Distribution: Debian GNU/Linux
Architecture: x64
Model: Intel(R) Celeron(R) CPU G1610T @ 2.30GHz
RAM: 9.73 GB
Node.js: v12.17.0
NPM: 6.14.5
Model: unknown
RAM: 987.98 MB
Node.js: v12.17.0
NPM: 6.14.4
Model: ARMv7 Processor rev 4 (v7l)
RAM: 975.6 MB
Node.js: v12.17.0
NPM: 6.14.5
JS-Controller (1): 3.1.4
Admin: 4.1.1
Network UPS Adapter: 1.1.3

created by ioBroker.info

An in-range update of nyc is breaking the build 🚨

The devDependency nyc was updated from 13.1.0 to 13.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 17 commits.

• 29e6f5e chore(release): 13.2.0
• e95856c chore: Update dependencies. (#978)
• 921d386 fix: Create directory for merge destination. (#979)
• df2730d feat: Option Plugins (#948)
• 35cd49a feat: document the fact that cacheDir is configurable (#968)
• ff834aa feat: avoid hardcoded HOME for spawn-wrap working dir (#957)
• 35710b1 build: move windows tests to travis (#961)
• 93cb5c1 tests: coverage for temp-dir changes (#964)
• d566efe test: stop using LAZY_LOAD_COUNT (#960)
• f23d474 chore: update stale bot config with feedback (#958)
• 62d7fb8 chore: slight tweak to position of test
• 28b6d09 fix: missing command temp-directory (#928)
• 40afc5f fix: nyc processing files not covered by include when all is enabled. (#914)
• ba22a26 docs(readme): Update to reflect .nycrc.json support (#934)
• 2dbb82d chore: enable probot-stale

There are 17 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Bitte in Description aufnehmen...

...dass bei QNAP NAS der Name der USV "qnapups" lauten muss.

Danke

An in-range update of mocha is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.0.2 of mocha was just published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	5.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

---

Release Notes

v5.0.2

5.0.2 / 2018-03-05

This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!

🐛 Fixes

• #3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:

  it('should actually fail, sorry!', function (done) {
    // passing assertion
    assert(true === true);
  // test complete & is marked as passing
  
  done();
  // ...but something evil lurks within
  
  setTimeout(() => {
  
  throw new Error('chaos!');
  
  }, 100);
  
  });

  Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.

  Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').

• #3093: Fix stack trace reformatting problem (@outsideris)

:nut_and_bolt Other

• #3248: Update browser-stdout to v1.3.1 (@honzajavorek)

Commits

The new version differs by 13 commits.

• f2ee53c Release v5.0.2
• ff1bd9e update package-lock.json
• 6a796cb prepare CHANGELOG for v5.0.2 [ci skip]
• 0542c40 update README.md; closes #3191 [ci skip]
• afcd08f add MAINTAINERS.md to .fossaignore [ci skip]
• 3792bef add opencollective header image to assets/
• 5078fc5 persist paths in stack trace which have cwd as infix
• 2c720a3 do not eat exceptions thrown asynchronously from passed tests; closes #3226
• 3537061 Update to correctly licensed browser-stdout version
• ec8901a remove unused functionality in utils module
• f71f347 rename wallaby.js -> .wallaby.js
• c4ef568 fix PR url
• 73d55ac fix typos in changelog [ci skip]

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Some values are not updated, only at restart

Values such as runtime, charge, load etc. are not updated on change, the values are only updated when the nut adapter is restarted. If the values change during operation, they are not updated. The values are read in once by the UPS (Synology) when the nut adapter is started. All other operating states are displayed correctly, even if changes are made.

JS-Controller 3.3 - LOG-Eintrag State value to set for "nut.0.battery.charge" has wrong type "string"

nut.0 | 2021-04-30 10:08:23.595 | warn | (19229) State value to set for "nut.0.battery.charge" has wrong type "string" but has to be "number"

[Security] Workflow test-and-release.yml is using vulnerable action actions/checkout

The workflow test-and-release.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Adapter aktuell nutzbar mit Synology Diskstation und JS-Controller 3.x?

Moin zusammen,

kann ich diesen Adapter gefahrlos in einem aktuellen ioBroker System einsetzen mit JS-Controller 3.x?
Die Daten der USV kommen von einer Synology Diskstation.

Danke für die Antwort
Leif

UPS Network Management Card 2

Hallo.

Ich hätte versucht meine APC UPS mittels eingebauter UPS Network Management Card 2 über den Adapter auszulesen.
Ist das überhaupt möglich? Gibt es hier hinsichtlich Name, Port und Zugangsdaten Besonderheiten?

Danke

Daten werden nach Update des NAS (Synology DS218J) nicht mehr aktualisiert

Hallo,
ich habe nach dem updaten des NAS (aktuell DSM 6.2.4-25556) festgestellt, d. die Daten im Iobroker nicht mehr aktualisiert werden und die Verbindung mit folgende Fehlermeldung fehl schlägt:

Im NAS wurden keine Veränderungen vorgenommen.

Ist das Problem bekannt oder kann man es eventuell durch eine andere Einstellung beheben?

Some datapoints are string, but number would be better

Datapoints, e.g. battery.voltage, input.voltage,... , are type string, but number would make more sense (IMHO).

Writing datapoints of type string to InfluxDB works, but makes live just complicated.

BR
Stefan

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/Apollon77/ioBroker.nut

• [E114] No adapter are allowed in the repo without admin3 support
• [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2022 Ingo Fischer [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2022 Ingo Fischer [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

An in-range update of nyc is breaking the build 🚨

Version 12.0.1 of nyc was just published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	12.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
• ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

---

Commits

The new version differs by 2 commits.

• 9fc20e4 chore(release): 12.0.1
• 3e087d4 chore: upgrade to version of istanbul with optional catch binding (#851)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Question: How does UPS-Monitor Notifies work?

I tried to use UPS-Monitor Notifies as described. But it does not work / I don't know what should happen. Can I see the message anywhere in ioBroker?

I tried it manually - can it be tested that way?
pi@raspberrypi:~ $ /opt/iobroker/iobroker message nut notify "{"upsname":"$UPSNAME","notifytype":"$NOTIFYTYPE"}"
The command "notify" was sent to "system.adapter..nut" with the message "[object Object]".
pi@raspberrypi:~ $ /opt/iobroker/iobroker message nut notify "Test"
The command "notify" was sent to "system.adapter..nut" with the message "Test".

But I can't see anything in ioB / log.

In my system the following file can be found here: /opt/iobroker/node_modules/iobroker.nut/scripts/nut-notify.sh
From docu: NOTIFYCMD "cd /opt/iobroker/;./nut-notify.sh"
Is this statement correct for my configuration? Or should it be: NOTIFYCMD "cd /opt/iobroker/;/opt/iobroker/node_modules/iobroker.nut/scripts/nut-notify.sh" ?

Thank you for your help

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!

Update stable version in repo from 1.1.3 to 1.3.0

Think about update stable version to 1.3.0

Version: stable=1.1.3 (1002 days old) => latest=1.3.0 (15 days old)
Installs: stable=573 (69.96%), latest=238 (29.06%), total=819
Click to edit

No connection on Pi bookworm

Hi Mister.

I recently updated to bookworm.
Everything was working fine on bullseye.

No connection to nut.
`

nut.0	2023-06-24 04:07:15.304	error	USV not available - Delay initialization
nut.0	2023-06-24 04:07:15.300	error	Error happened: Error: connect ECONNREFUSED 127.0.0.1:3493
nut.0	2023-06-24 04:06:45.295	error	USV not available - Delay initialization
nut.0	2023-06-24 04:06:45.292	error	Error happened: Error: connect ECONNREFUSED 127.0.0.1:3493
nut.0	2023-06-24 04:06:15.287	error	USV not available - Delay initialization
nut.0	2023-06-24 04:06:15.284	error	Error happened: Error: connect ECONNREFUSED 127.0.0.1:3493

`

Pls help!

Driver needs to be activated with console after reboot

Hi.
Always, after restarting iobroker on proxmox I get this error message and there is no connection to the UPS:

Err while getting NUT values: DRIVER-NOT-CONNECTED

After starting the driver manually with sudo upsdrvctl start it works fine again.

Is this a bug from the adapter? I thought the driver would be started automatically?

Thanks!

Update stable version in repo from 1.5.1 to 1.6.0

Think about update stable version to 1.6.0

Version: stable=1.5.1 (308 days old) => latest=1.6.0 (15 days old)
Installs: stable=1575 (77.85%), latest=259 (12.8%), total=2023
Click to edit

Instance not listening

Hi,
I added ioBrokers IP to the list of slave devices in my qnap nas but the Nut instanz doesn't react to the alarm. I see there is a poll time in the settings but I wonder if there couldn't be a real "slave" mode which is triggered externally?

Update stable version in repo from 1.4.3 to 1.5.0

Think about update stable version to 1.5.0

Version: stable=1.4.3 (107 days old) => latest=1.5.0 (15 days old)
Installs: stable=623 (62.36%), latest=226 (22.62%), total=999
Click to edit

Reconnect adapter

Is your feature request related to a problem? Please describe.
The UPS is connected to the remote server, which is sometimes unavailable. NUT driver indicates then no connection to the device. It is ok. But this driver doesn't try to reconnect the device

Describe the solution you'd like
Add the possibility of reconnecting to UPS periodically

Describe alternatives you've considered
Create a script that pings the device and restarts a driver.

Add Support for Compact mode (js-Controller 2.0 Feature)

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

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

Please see the result of the check below.

ioBroker.nut

-

ERRORS:

• ❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
• ❗ [E033] @iobroker/adapter-core 2.6.7 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
• ❗ [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
• ❗ [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script-plugin-license:3.5.9"
• ❗ [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.
• ❗ [E184] "common.subscribe" will be removed with js-controller >= 6. Please remove from io-package.json and adapt code if required.

WARNINGS:

• 👀 [W040] "keywords" within package.json should contain "ioBroker"
• 👀 [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
• 👀 [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
• 👀 [W170] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
• 👀 [W173] Potential sensitive data "password" not listed at "protectedNative" in io-package.json
• 👀 [W174] Potential sensitive data "password" not listed at "encryptedNative" in io-package.json
• 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
• 👀 [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
• 👀 [W510] "/admin/i18n/uk/translations.json" or "admin/i18n/uk.json" not found, but admin support is declared. Please add.
• 👀 [W519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
• 👀 [W853] .npmignore found - consider using package.json object "files" instead.

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

Ubuntu VM Err while getting all commands: UNKNOWN-UPS

Hallo

ich habe folgendes problem:

ich habe den nuts server auf einer vm im proxmox eingerichtet und den usb mittels usb angeschlossen.
Einrichtung alles kein problem Daten werden auslesen (local).

aber die Weiterleitung an den iobroker klappt nicht.

der adapter verbindet sich.
aber alle werte sind false

`

nut.0	2023-08-22 16:46:20.203	error	Err while getting NUT values: UNKNOWN-UPS
nut.0	2023-08-22 16:46:20.202	error	Err while getting all commands: UNKNOWN-UPS
nut.0	2023-08-22 16:46:20.037	info	starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.nut, node: v18.17.1, js-controller: 4.0.

`

Versions:

• Adapter version: 1.6.0
• Operating system: ubuntu server 22 auf proxmox