apollon77 / iobroker.daikin Goto Github PK

Control Daikin Air Conditioner devices

License: MIT License

HTML 5.39% JavaScript 94.61%

daikin-device iobroker daikin air-conditioner

iobroker.daikin's Introduction

ioBroker.daikin

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.

This adapter connects to a Daikin Air Conditioner device and allows to control the device and to read values from it. The Daikin Device needs to be equipped with a Daikin Wifi controller. Normally all wifi controllers should be supportedthat are supported by the Daikin App.

According to Daikin Support Documents the following devices should be compatible (at least):

Compatible units in combination with BRP069A41: FTXG20LV1BW, FTXG20LV1BS , FTXG25LV1BW, FTXG25LV1BS, FTXG35LV1BW, FTXG35LV1BS, FTXG50LV1BW, FTXG50LV1BS, FTXJ20LV1BW, FTXJ20LV1BS, FTXJ25LV1BW, FTXJ25LV1BS, FTXJ35LV1BW, FTXJ35LV1BS, FTXJ50LV1BW, FTXJ50LV1BS ,

Compatible units in combination with BRP069A42: FTXZ25NV1B, FTXZ35NV1B, FTXZ50NV1B, FTXS35K2V1B, FTXS35K3V1B, FTXS42K2V1B, FTXS42K3V1B, FTXS50K2V1B, FTXS50K3V1B, FTXLS25K2V1B, FTXLS35K2V1B,FTXM35K3V1B, FTXM42K3V1B, FTXM50K3V1B, , FTXS60GV1B, FTXS71GV1B, ATXS35K2V1B, ATXS35K3V1B, ATXS50K2V1B, ATXS50K3V1B, , FTX50GV1B, FTX60GV1B, FTX71GV1B, , FVXG25K2V1B, FVXG35K2V1B, FVXG50K2V1B, , FVXS25FV1B, FVXS35FV1B, FVXS50FV1B, , FLXS25BAVMB, FLXS25BVMA, FLXS25BVMB, FLXS35BAVMB, FLXS35BAVMB9, FLXS35BVMA, FLXS35BVMB, FLXS50BAVMB, FLXS50BVMA, FLXS50BVMB, FLXS60BAVMB, FLXS60BVMA, FLXS60BVMB,

Compatible units in combination with BRP069A43 (?): CTXS15K2V1B, CTXS15K3V1B, FTXS20K2V1B, FTXS20K3V1B, FTXS25K2V1B, FTXS25K3V1B, CTXS35K2V1B, CTXS35K3V1B, FTXM20K3V1B, FTXM25K3V1B, , ATXS20K2V1B, ATXS20K3V1B, ATXS25K2V1B, ATXS25K3V1B, , FTX20J2V1B, FTX25J2V1B, FTX35J2V1B, FTX20J3V1B, FTX25J3V1B, FTX35J3V1B, , FTXL25J2V1B, FTXL35J2V1B, , FTX20KV1B, FTX25KV1B, FTX35KV1B, FTX20GV1B, FTX25GV1B, FTX35GV1B, , ATX20J2V1B, ATX20J3V1B, ATX25J2V1B, ATX25J3V1B, ATX35J2V1B, ATX35J3V1B, ATX20KV1B, ATX25KV1B, ATX35KV1B, , ATXL25J2V1B, ATXL35J2V1B,

Compatible units in combination with BRP069A44 (?): FTX50KV1B, FTX60KV1B

Note: it seems that, according to reports so far, the adapters here keep their local API even when upgraded to the Firmware that allows Daikin Cloud usage. So this adapter should still work with these devices.

Note: For devices with-newer WLAN Adapter like BRP069C4x which can only be used by the Onecta App please use the Daikin-Cloud adapter instead.

Disclaimer

All product and company names or logos are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them or any associated subsidiaries! This personal project is maintained in spare time and has no business goal. Daikin is a trademark of DAIKIN INDUSTRIES, LTD.

Description of parameters

daikinIp

The IP of the Wifi controler from the Device

pollingInterval

Interval in seconds to update the data from the device. Additionally values are updated on each change

Description of the available instance objects/states

After the Adapter has connected to the Daikin Device a structure of objects are created:

deviceInfo.* : General informations about the Daikin device, read-only
control.* : Main controllable values from the Device like target temperature, mode and such, read- and writeable
controlInfo.* : Additional control-informations from the Device, read-only
modelInfo.* : Information about the Device itself and the supported features, read-only
sensorInfo.* : Sensor data from the Device like the measured indoor and outdoor temperature

Todo

enhance testing: state checks and setState's
check model info/supported features
docs for webpage
VIS widget

Changelog

WORK IN PROGRESS

(Apollon77) Prevented some error logs and fix internal flow issues

1.4.2 (2022-07-25)

(Apollon77) Make sure polling still works after setting special mode states

1.4.1 (2022-06-27)

(Apollon77) Prevent crash case reported by Sentry

1.4.0 (2022-06-09)

(Apollon77) Add Connection identifier for Admin and Device
(Apollon77) Optimize unload handling

1.3.3 (2021-06-24)

(Apollon77) Prevent crash case when no temperature was read out (Sentry IOBROKER-DAIKIN-D, IOBROKER-DAIKIN-M)

1.3.2 (2021-06-05)

(Apollon77) Handle modes correctly where no temperature or humidity parameters are required

1.3.1 (2021-05-14)

(Apollon77) Prepare for js-controller 3.3

1.3.0 (2021-01-14)

(Apollon77) Prevent warnings in js-controller 3.2
(Apollon77) Allow overwriting the name in Daikin channel object
(Apollon77) Require at least js-controller 2.0

1.2.0 (2020-12-27)

add compact mode

1.1.3 (2020-11-19)

add experimental support for lpw parameter
crash cases prevented (Sentry IOBROKER-DAIKIN-7)

1.1.2 (2020-08-06)

crash cases prevented (Sentry IOBROKER-DAIKIN-2, IOBROKER-DAIKIN-3, IOBROKER-DAIKIN-4)

1.1.1 (2020-08-02)

better handle case where configuration is missing (Sentry IOBROKER-DAIKIN-1)

1.1.0 (2020-07-21)

Adjust Texts and translate
create daikin.X ads device object and add one role
Update dependencies

1.0.4 (2019-06-25)

Daikin library updated, communication error handling optimized

1.0.3 (2019-02-xx)

Daikin library updated, communication errors optimized

1.0.2 (2018-04-29)

Daikin library updated

1.0.1 (2018-04-13)

Fix Admin

1.0.0 (2018-01-1x)

Admin3 readieness
Support older Daikin-WLAN-Firmwares with special config flag

0.2.3 (2017-04-01)

Add control.lastResult to see if a change was successfull

0.2.2

reduce debug logging

0.2.0

first finalized version

0.1.x

development and first tests

License

The MIT License (MIT)

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.daikin's People

Contributors

Stargazers

Watchers

Forkers

wolfspiritm ic3breaker angelnu ak1de yubik9 drdebian iobrokertranslator enso-media iobroker-archive matze2

iobroker.daikin's Issues

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')

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

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency nyc was updated from `15.0.1` to `15.1.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 could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

de7baa4 chore(release): 15.1.0
992359a feat(experimental): Support using --all with node.js ESM (#1320)
086fd20 chore: Regenerate package-lock, update source-map-support test (#1314)
b20f751 chore: add bugs (used, e.g., by npmjs) (#1313)
6898e88 chore: Fix CHANGELOG.md version header

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 🌴

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.daikin

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

Websoket Integration für Wärmepumpen

Da die Wärmepumpen mit Cloud-Anbindung diesen Adapter nicht nutzen können wäre eine Integration mit Websocket Kommunikation ein Ansatz.

hier wurden Infos zu den Protokollen/Befehlen veröffentlicht:
https://community.openhab.org/t/how-to-integrate-daikin-altherma-lt-heat-pump/16488/16

und hier:
https://community.openenergymonitor.org/t/hack-my-heat-pump-and-publish-data-onto-emoncms/2551/44

Support DAIKIN Heat Pump / Wärmepumpe

seems that Websockets are used: https://community.openenergymonitor.org/t/hack-my-heat-pump-and-publish-data-onto-emoncms/2551/41

Followup on ioBroker/AdapterRequests#245

Controller bekommt keine Verbindung ins WLAN

Hallo zusammen,
gehört hier eigentlich nicht rein, dachte ich frage trotzdem mal.
Folgendes, habe mein WLAN Equipment von AVM auf Unifi umgestellt. Jetzt bekomme ich den Controller nicht mehr in mein WLAN! Vielleicht hat ja jemand einen Hinweiß woran das liegen könnte?
Danke
Gruß
Thomas

Wrong type by datapoint after update JS-Controller 3.3.x

daikin.0	2021-08-09 21:17:57.831	info	(16121) State value to set for "daikin.0.control.lastResult" has to be type "string" but received type "object"
daikin.0	2021-08-09 21:17:57.825	error	(16121) Error updating data: Error: Error while communicating with Daikin device: ECONNRESET
daikin.0	2021-08-09 21:05:56.749	info	(16121) State value to set for "daikin.0.control.lastResult" has to be type "string" but received type "object"
daikin.0	2021-08-09 21:05:56.745	error	(16121) Error updating data: Error: Error while communicating with Daikin device: ECONNRESET

please reduce information in log

can you please reduce information in log while using loglevel 'info'

daikin.2 | 2021-03-21 17:24:25.899 | info | (4009) Set State sensorInfo.outdoorTemperature: "7"
daikin.3 | 2021-03-21 17:23:54.689 | info | (4243) Set State sensorInfo.outdoorTemperature: "7"
daikin.0 | 2021-03-21 17:23:18.721 | info | (3759) Set State sensorInfo.outdoorTemperature: "7"
daikin.1 | 2021-03-21 17:22:48.681 | info | (3834) Set State sensorInfo.outdoorTemperature: "7"

and similar values aren't necessarily used in this loglevel

Feature request: Support reading of energy consumption data

Some of the Daiking devices provide energy consumption data.
I am using
FTXA25A2V1BW with build-in controller (FW 1.2.51)
and two FVXM25FV1B with controllers BRP069A42 (FW 3.3.6) and BRP069B41 (FW 1.2.51).
For all three combinations energy data is displayed in the Daikin app.
Please see the attached screenshot as an example.

Also support GET to set data for older firmwares

Needed for older firmwares

Update stable version in repo from 1.3.1 to 1.3.3

Think about update stable version to 1.3.3

Version: stable=1.3.1 (55 days old) => latest=1.3.3 (15 days old)
Installs: stable=235 (49.06%), latest=63 (13.15%), total=479
Click to edit

Consider supporting ioBroker.type-detector

I tried to use the daikin device for lovelace but currently it doesn't work.

The reason is that ioBroker.type-detector can't detect it completly.

There are multiple problems:

ioBroker.type-detector is looking for objects in a parent "device". Currently this adapter only creates channels and no parent device. Therefor it's not finding any related objects.
ioBroker.type-detector is looking for switch.boost and switch.power. Currently the adapter only sets "switch".
ioBroker.type-detector is looking for both switches to be a "number". Which might be a bug in ioBroker.type-detector?
ioBroker.type-detector can't find "indoorTemperate" as the actual temperature as it's considering the non-writeable value.temperatures in "controlInfo" as the actual temperature. Maybe using a different role for that would be better?

Update stable version in repo from 1.3.3 to 1.4.0

Think about update stable version to 1.4.0

Version: stable=1.3.3 (366 days old) => latest=1.4.0 (15 days old)
Installs: stable=645 (84.09%), latest=62 (8.08%), total=767
Click to edit

An in-range update of daikin-controller is breaking the build 🚨

Version 1.1.2 of daikin-controller was just published.

Branch	Build failing 🚨
Dependency	daikin-controller
Current Version	1.1.1
Type	dependency

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

daikin-controller is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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 13 commits.

851c290 1.1.2 fixes #6
dbad3c7 fix testing
d170c2c change/fix error handling and tests for it
93892a9 nodejs 10 testing
3b1ca43 Merge branch 'master' of https://github.com/Apollon77/daikin-controller
5db411b add nodejs 10 to testing
8147951 Merge pull request #4 from Apollon77/greenkeeper/sinon-5.0.0
536f841 chore(package): update sinon to version 5.0.0
413cc4c fix testing
14e3dce Merge branch 'master' of https://github.com/Apollon77/daikin-controller
6a93910 Merge pull request #2 from Apollon77/greenkeeper/initial
445df57 docs(readme): add Greenkeeper badge
03f3e14 chore(package): update dependencies

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 🌴

Support for BPR084A42-1

**Is your feature request related to a problem?
I got my Daikin Stylish devices (FXTAxxAW) installed today. They come with the built-in adapter BRP084A42-1. The Android-App is able to communicate with the devices. ioBroker throws a LOG entry like "(16765) Daikin Device initialized with Error :Error: Error while communicating with Daikin device: EHOSTUNREACH" when starting the adapter.

Describe the solution you'd like
Communication with the divices.

Describe alternatives you've considered
None.

Additional context
Host: RasberryPi
Node.js: 12.20.0
NPM: 6.14.9
Daikin adapter: 1.1.3
Daikin FW: 1.2.51

When changing a parameter with JS the command is not sent to the device

I am currently integrating ioBroker into my smart home and just connected the Daikin-KNX group addresses to your Daikin adapter objects using JS/blockly.
Reading and transforming the values works fine, my only problem left is that if I send new values to the daikin objects by JS - for example a new target temperature or ON/OFF - the value displayed in ioBroker is changed though but the new value is not sent to the Daikin device. With the next statusupdate the original values are restored.
If I type in the values directly to the ioBroker object, then the device is instantly updated.

Can you give me some help on this? Many thanks!

Best regards,
Marc

Daikin integrated WIFI Controler BRP069C4x not compatible with IOBroker adapter

Describe the bug
Today a brand new Daikin AC has been installed in our home.
The unit comes with the integrated wificontroler BRP069C4x, Firmware 1.7.22. This is the information what you can get from the Daikin app.
The response in iobroker from the Daikin controler after initializing is

" Daikin Device initialized with Error :Cannot parse response: Page Not Found"

Or do I something wrong?

Versions:

Adapter version: 1.3.0
Node.js: v12.21.0
NPM: 6.14.11
Operating system: Linux

-Andreas

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!

Update stable version in repo from 1.1.3 to 1.2.0

Think about update stable version to 1.2.0

Version: stable=1.1.3 (53 days old) => latest=1.2.0 (15 days old)
Installs: stable=191 (52.62%), latest=51 (14.05%), total=363
Click to edit

An in-range update of daikin-controller is breaking the build 🚨

Version 1.1.1 of daikin-controller was just published.

Branch	Build failing 🚨
Dependency	daikin-controller
Current Version	1.1.0
Type	dependency

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

daikin-controller is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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 1 commits.

7ca1647 1.1.1

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 🌴

Update stable version in repo from 1.2.0 to 1.3.0

Think about update stable version to 1.3.0

Version: stable=1.2.0 (48 days old) => latest=1.3.0 (30 days old)
Installs: stable=176 (46.32%), latest=60 (15.79%), total=380
Click to edit

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

GET required even for new adapters?

Hi,
I have brand new Daikin Emura model: FTXJ-35MW/RXJ-35M (most probably: FTXJ35LV1BW)
It has (most probably) BRP069A41 Wifi Module with firmware 1.2.51 installed

ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_51,rev=D3A0C9F [...]

Daikin Emura modelInfo.model=0D76
Daikin Emura deviceInfo.adapterKind=3
Daikin Emura deviceInfo.adapterVersion=1_2_51

I was getting "Wrong Parameters in request: ret=PARAM NG" errors when I tried to set any control settings, either via admin panel or MQTT.
Until I set sending changes with GET:

But it says only needed for older WLAN Firmwares.
Is my 1.2.51 firmware old?
Seems like sending commands over GET is kind of depracated here..

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.daikin

[E114] No adapter are allowed in the repo without admin3 support
[E605] No actual year found in copyright. Please add "Copyright (c) 2017-2022 Ingo Fischer [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2022 Ingo Fischer [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

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 🌴

Error updating data: Error: Error while communicating with Daikin device: ECONNRESET

No clue what changed, but 2 days ago I started to get this error ~10-15 times per hour. sometimes after 10 minutes, sometimes after 2 minutes.

objects are updated and adapter is green, everything still seems to work as intended. I dind't intentionally change anything network or iobroker related.

Update stable version in repo from 1.3.0 to 1.3.1

Think about update stable version to 1.3.1

Version: stable=1.3.0 (135 days old) => latest=1.3.1 (15 days old)
Installs: stable=274 (62.41%), latest=59 (13.44%), total=439
Click to edit

Integration of WiFi-Connection to Daikin Perfera FVXM35A

The actual adapter ioBroker.daikin doesn´t support the Daikin Prefera FVXM35A. I´d like to integrate the air conditioner in ioBroker but with the ip-address of the air conditioner i can´t connect in ioBroker.

Maybe there is a chance to integrate it with this adapeter. Maybe the same protocol/interface like the other air conditioners?!

Unknown response: ret=LPW NG

Hi,

I was trying to connect ioBroker (4.0.10) to my new Daikin Wifi Adapter (BRP069B41) via the ioBroker.daikin instance. (1.0.5)

The Adapter keeps answering "LPW NG"

I've tried with and without "Send changes with GET" the response remains the same.

Connecting via the Daikin app works.
I don't need to control the AC via ioBroker, I just want to get all the data that I can then forward to an influx database.

Debian GNU/Linux
JS 3.1.6
Node.js v10.22.0
NPM 6.14.6

Recent Logfile

2020-08-09 00:00:04.816 - info: influxdb.0 (963) Connected!
2020-08-09 00:20:32.673 - info: influxdb.0 (963) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 00:20:34.175 - info: discovery.0 (816) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 00:20:32.677 - info: admin.0 (802) terminating http server on port 8081
2020-08-09 00:20:32.671 - info: info.0 (840) cleaned everything up...
2020-08-09 00:20:40.032 - info: admin.0 (802) Got terminate signal TERMINATE_YOURSELF
2020-08-09 00:20:40.036 - info: discovery.0 (816) Got terminate signal TERMINATE_YOURSELF
2020-08-09 00:20:40.039 - info: info.0 (840) Got terminate signal TERMINATE_YOURSELF
2020-08-09 00:20:32.670 - info: host.OVERWATCH received SIGTERM
2020-08-09 00:20:40.019 - info: host.OVERWATCH stopInstance system.adapter.admin.0 (force=false, process=true)
2020-08-09 00:20:40.020 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 (force=false, process=true)
2020-08-09 00:20:40.021 - info: host.OVERWATCH stopInstance system.adapter.info.0 (force=false, process=true)
2020-08-09 00:20:40.021 - info: host.OVERWATCH stopInstance system.adapter.influxdb.0 (force=false, process=true)
2020-08-09 00:20:40.024 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=false)
2020-08-09 00:20:40.027 - info: host.OVERWATCH stopInstance system.adapter.admin.0 send kill signal
2020-08-09 00:20:40.031 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 send kill signal
2020-08-09 00:20:40.032 - info: host.OVERWATCH stopInstance system.adapter.info.0 send kill signal
2020-08-09 00:20:40.064 - info: host.OVERWATCH instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-08-09 00:20:40.074 - info: info.0 (840) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 00:20:40.072 - info: admin.0 (802) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 00:20:40.501 - info: host.OVERWATCH instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 00:20:40.591 - info: host.OVERWATCH instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 00:20:40.593 - info: host.OVERWATCH instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 00:20:40.594 - info: host.OVERWATCH All instances are stopped.
2020-08-09 00:20:40.627 - info: host.OVERWATCH terminated
2020-08-09 00:21:04.963 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 00:21:04.973 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 00:21:04.974 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 00:21:04.977 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 00:21:05.423 - info: host.OVERWATCH connected to Objects and States
2020-08-09 00:21:06.216 - info: host.OVERWATCH 5 instances found
2020-08-09 00:21:06.247 - info: host.OVERWATCH starting 4 instances
2020-08-09 00:21:06.314 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 714
2020-08-09 00:21:14.838 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 750
2020-08-09 00:21:14.922 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 757
2020-08-09 00:21:18.588 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 862
2020-08-09 00:21:20.751 - info: discovery.0 (750) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 00:21:43.712 - info: influxdb.0 (862) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 00:21:43.864 - info: admin.0 (714) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 00:21:43.940 - info: admin.0 (714) requesting all states
2020-08-09 00:21:43.941 - info: admin.0 (714) requesting all objects
2020-08-09 00:21:43.753 - info: influxdb.0 (862) No stored data from last exit found
2020-08-09 00:21:43.757 - info: influxdb.0 (862) Connecting http://127.0.0.1:8086 ...
2020-08-09 00:21:44.127 - error: influxdb.0 (862) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 00:21:44.767 - info: admin.0 (714) received all objects
2020-08-09 00:21:44.875 - info: admin.0 (714) http server listening on port 8081
2020-08-09 00:21:44.876 - info: admin.0 (714) Use link "http://localhost:8081" to configure.
2020-08-09 00:21:46.929 - info: info.0 (757) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 00:21:50.654 - info: info.0 (757) Popup news was read...
2020-08-09 00:21:54.129 - info: influxdb.0 (862) Connecting http://127.0.0.1:8086 ...
2020-08-09 00:21:55.538 - info: influxdb.0 (862) Connected!
2020-08-09 00:51:47.092 - info: info.0 (757) Popup news was read...
2020-08-09 01:21:47.062 - info: info.0 (757) Popup news was read...
2020-08-09 01:43:43.434 - info: host.OVERWATCH received SIGTERM
2020-08-09 01:43:43.438 - info: admin.0 (714) terminating http server on port 8081
2020-08-09 01:43:43.449 - info: info.0 (757) cleaned everything up...
2020-08-09 01:43:43.460 - info: influxdb.0 (862) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 01:43:43.471 - info: info.0 (757) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:43:43.481 - info: admin.0 (714) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:43:43.440 - info: host.OVERWATCH stopInstance system.adapter.admin.0 (force=false, process=true)
2020-08-09 01:43:43.441 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 (force=false, process=true)
2020-08-09 01:43:43.441 - info: host.OVERWATCH stopInstance system.adapter.info.0 (force=false, process=true)
2020-08-09 01:43:43.442 - info: host.OVERWATCH stopInstance system.adapter.influxdb.0 (force=false, process=true)
2020-08-09 01:43:43.444 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=false)
2020-08-09 01:43:43.446 - info: host.OVERWATCH stopInstance system.adapter.admin.0 send kill signal
2020-08-09 01:43:43.467 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 send kill signal
2020-08-09 01:43:43.468 - info: host.OVERWATCH stopInstance system.adapter.info.0 send kill signal
2020-08-09 01:43:43.495 - info: discovery.0 (750) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:43:43.499 - info: admin.0 (714) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:43:43.496 - info: info.0 (757) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:43:43.502 - info: discovery.0 (750) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:43:46.361 - info: host.OVERWATCH stopInstance system.adapter.admin.0 killing pid 714
2020-08-09 01:43:46.362 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 killing pid 750
2020-08-09 01:43:46.363 - info: host.OVERWATCH stopInstance system.adapter.info.0 killing pid 757
2020-08-09 01:43:46.364 - info: host.OVERWATCH stopInstance timeout 2000 system.adapter.influxdb.0 killing pid 862
2020-08-09 01:43:46.387 - info: host.OVERWATCH instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:43:46.387 - info: host.OVERWATCH All instances are stopped.
2020-08-09 01:43:46.388 - info: host.OVERWATCH instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:43:46.389 - info: host.OVERWATCH All instances are stopped.
2020-08-09 01:43:46.389 - info: host.OVERWATCH instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:43:46.390 - info: host.OVERWATCH All instances are stopped.
2020-08-09 01:43:46.390 - info: host.OVERWATCH instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-08-09 01:43:46.390 - info: host.OVERWATCH All instances are stopped.
2020-08-09 01:43:46.564 - info: host.OVERWATCH terminated
2020-08-09 01:44:51.267 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 01:44:51.282 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 01:44:51.283 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 01:44:51.286 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 01:44:51.826 - info: host.OVERWATCH connected to Objects and States
2020-08-09 01:44:53.274 - info: host.OVERWATCH 5 instances found
2020-08-09 01:44:53.297 - info: host.OVERWATCH starting 4 instances
2020-08-09 01:44:53.348 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 748
2020-08-09 01:45:01.237 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 776
2020-08-09 01:45:01.401 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 785
2020-08-09 01:45:22.791 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 962
2020-08-09 01:45:23.623 - info: discovery.0 (776) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 01:45:26.116 - info: admin.0 (748) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 01:45:26.390 - info: admin.0 (748) requesting all states
2020-08-09 01:45:26.391 - info: admin.0 (748) requesting all objects
2020-08-09 01:45:27.255 - info: admin.0 (748) received all objects
2020-08-09 01:45:27.376 - info: admin.0 (748) http server listening on port 8081
2020-08-09 01:45:27.377 - info: admin.0 (748) Use link "http://localhost:8081" to configure.
2020-08-09 01:45:28.606 - info: influxdb.0 (962) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 01:45:28.717 - info: influxdb.0 (962) No stored data from last exit found
2020-08-09 01:45:28.735 - info: influxdb.0 (962) Connecting http://127.0.0.1:8086 ...
2020-08-09 01:45:28.878 - error: influxdb.0 (962) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 01:45:30.540 - info: info.0 (785) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 01:45:37.553 - info: info.0 (785) Popup news was read...
2020-08-09 01:45:38.880 - info: influxdb.0 (962) Connecting http://127.0.0.1:8086 ...
2020-08-09 01:45:38.888 - error: influxdb.0 (962) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 01:45:48.891 - info: influxdb.0 (962) Connecting http://127.0.0.1:8086 ...
2020-08-09 01:45:48.914 - error: influxdb.0 (962) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 01:45:58.932 - info: influxdb.0 (962) Connecting http://127.0.0.1:8086 ...
2020-08-09 01:45:58.948 - info: influxdb.0 (962) Connected!
2020-08-09 01:54:55.108 - info: info.0 (785) cleaned everything up...
2020-08-09 01:54:55.110 - info: influxdb.0 (962) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 01:54:55.105 - info: admin.0 (748) terminating http server on port 8081
2020-08-09 01:54:55.127 - info: host.OVERWATCH received SIGTERM
2020-08-09 01:54:55.150 - info: admin.0 (748) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:54:55.168 - info: discovery.0 (776) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:54:55.141 - info: host.OVERWATCH stopInstance system.adapter.admin.0 (force=false, process=true)
2020-08-09 01:54:55.142 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 (force=false, process=true)
2020-08-09 01:54:55.142 - info: host.OVERWATCH stopInstance system.adapter.info.0 (force=false, process=true)
2020-08-09 01:54:55.143 - info: host.OVERWATCH stopInstance system.adapter.influxdb.0 (force=false, process=true)
2020-08-09 01:54:55.145 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=false)
2020-08-09 01:54:55.147 - info: host.OVERWATCH stopInstance system.adapter.admin.0 send kill signal
2020-08-09 01:54:55.164 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 send kill signal
2020-08-09 01:54:55.175 - info: host.OVERWATCH stopInstance system.adapter.info.0 send kill signal
2020-08-09 01:54:55.188 - info: info.0 (785) Got terminate signal TERMINATE_YOURSELF
2020-08-09 01:54:55.201 - info: discovery.0 (776) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:54:55.196 - info: admin.0 (748) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:54:55.209 - info: info.0 (785) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 01:54:55.628 - info: host.OVERWATCH instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-08-09 01:54:55.725 - info: host.OVERWATCH instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:54:55.730 - info: host.OVERWATCH instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:54:55.734 - info: host.OVERWATCH instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 01:54:55.735 - info: host.OVERWATCH All instances are stopped.
2020-08-09 01:54:55.750 - info: host.OVERWATCH terminated
2020-08-09 01:55:50.123 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 01:55:50.132 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 01:55:50.133 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 01:55:50.136 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 01:55:50.630 - info: host.OVERWATCH connected to Objects and States
2020-08-09 01:55:51.487 - info: host.OVERWATCH 5 instances found
2020-08-09 01:55:51.512 - info: host.OVERWATCH starting 4 instances
2020-08-09 01:55:51.562 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 738
2020-08-09 01:56:00.395 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 772
2020-08-09 01:56:00.459 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 779
2020-08-09 01:56:03.574 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 881
2020-08-09 13:00:03.571 - info: discovery.0 (772) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:00:07.688 - info: admin.0 (738) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:00:07.700 - info: influxdb.0 (881) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:00:07.826 - info: admin.0 (738) requesting all states
2020-08-09 13:00:07.827 - info: admin.0 (738) requesting all objects
2020-08-09 13:00:08.211 - info: admin.0 (738) received all objects
2020-08-09 13:00:07.740 - info: influxdb.0 (881) No stored data from last exit found
2020-08-09 13:00:07.744 - info: influxdb.0 (881) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:00:08.456 - error: influxdb.0 (881) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 13:00:08.402 - info: admin.0 (738) http server listening on port 8081
2020-08-09 13:00:08.402 - info: admin.0 (738) Use link "http://localhost:8081" to configure.
2020-08-09 13:00:10.266 - info: admin.0 (738) Request actual repository...
2020-08-09 13:00:10.314 - info: host.OVERWATCH Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2020-08-09 13:00:12.429 - info: admin.0 (738) Repository received successfully.
2020-08-09 13:00:13.321 - info: info.0 (779) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:00:18.459 - info: influxdb.0 (881) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:00:18.475 - error: influxdb.0 (881) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 13:00:19.881 - info: info.0 (779) Popup news was read...
2020-08-09 13:00:28.477 - info: influxdb.0 (881) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:00:28.483 - error: influxdb.0 (881) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 13:00:38.485 - info: influxdb.0 (881) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:00:38.492 - error: influxdb.0 (881) Error: connect ECONNREFUSED 127.0.0.1:8086
2020-08-09 13:00:48.494 - info: influxdb.0 (881) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:00:48.529 - info: influxdb.0 (881) Connected!
2020-08-09 13:17:05.737 - info: admin.0 (738) terminating http server on port 8081
2020-08-09 13:17:05.740 - info: info.0 (779) cleaned everything up...
2020-08-09 13:17:05.742 - info: influxdb.0 (881) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 13:17:05.774 - info: host.OVERWATCH received SIGTERM
2020-08-09 13:17:05.844 - info: admin.0 (738) Got terminate signal TERMINATE_YOURSELF
2020-08-09 13:17:05.870 - info: discovery.0 (772) Got terminate signal TERMINATE_YOURSELF
2020-08-09 13:17:05.874 - info: info.0 (779) Got terminate signal TERMINATE_YOURSELF
2020-08-09 13:17:05.806 - info: host.OVERWATCH stopInstance system.adapter.admin.0 (force=false, process=true)
2020-08-09 13:17:05.807 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 (force=false, process=true)
2020-08-09 13:17:05.821 - info: host.OVERWATCH stopInstance system.adapter.info.0 (force=false, process=true)
2020-08-09 13:17:05.821 - info: host.OVERWATCH stopInstance system.adapter.influxdb.0 (force=false, process=true)
2020-08-09 13:17:05.839 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=false)
2020-08-09 13:17:05.842 - info: host.OVERWATCH stopInstance system.adapter.admin.0 send kill signal
2020-08-09 13:17:05.843 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 send kill signal
2020-08-09 13:17:05.872 - info: host.OVERWATCH stopInstance system.adapter.info.0 send kill signal
2020-08-09 13:17:05.906 - info: discovery.0 (772) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 13:17:05.922 - info: admin.0 (738) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 13:17:05.923 - info: info.0 (779) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-08-09 13:17:06.263 - info: host.OVERWATCH instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-08-09 13:17:06.424 - info: host.OVERWATCH instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 13:17:06.448 - info: host.OVERWATCH instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 13:17:06.450 - info: host.OVERWATCH instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-08-09 13:17:06.450 - info: host.OVERWATCH All instances are stopped.
2020-08-09 13:17:06.647 - info: host.OVERWATCH terminated
2020-08-09 13:18:53.069 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:18:53.079 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:18:53.080 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:18:53.082 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:18:53.457 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:18:53.964 - info: host.OVERWATCH 5 instances found
2020-08-09 13:18:53.987 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:18:54.035 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 723
2020-08-09 13:19:37.278 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:19:37.287 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:19:37.288 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:19:37.290 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:19:37.679 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:19:39.197 - info: host.OVERWATCH 5 instances found
2020-08-09 13:19:39.221 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:19:39.287 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 747
2020-08-09 13:20:58.179 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:20:58.187 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:20:58.188 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:20:58.191 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:20:58.579 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:20:59.458 - info: host.OVERWATCH 5 instances found
2020-08-09 13:20:59.475 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:21:09.130 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 775
2020-08-09 13:21:10.258 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 782
2020-08-09 13:21:12.216 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 790
2020-08-09 13:22:07.355 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 797
2020-08-09 13:22:12.887 - info: discovery.0 (782) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:22:15.224 - info: influxdb.0 (797) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:22:15.263 - info: influxdb.0 (797) No stored data from last exit found
2020-08-09 13:22:15.267 - info: influxdb.0 (797) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:22:15.948 - info: influxdb.0 (797) Connected!
2020-08-09 13:22:17.920 - info: admin.0 (775) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:22:18.007 - info: admin.0 (775) requesting all states
2020-08-09 13:22:18.008 - info: admin.0 (775) requesting all objects
2020-08-09 13:22:18.434 - info: admin.0 (775) received all objects
2020-08-09 13:22:18.542 - info: admin.0 (775) http server listening on port 8081
2020-08-09 13:22:18.543 - info: admin.0 (775) Use link "http://localhost:8081" to configure.
2020-08-09 13:22:20.186 - info: info.0 (790) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:22:23.310 - info: info.0 (790) Popup news was read...
2020-08-09 13:22:18.314 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:22:18.323 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:22:18.324 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:22:18.326 - info: host.OVERWATCH ip addresses: fe80::8fde:4fa3:8434:eacc
2020-08-09 13:22:18.717 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:22:19.807 - info: host.OVERWATCH 5 instances found
2020-08-09 13:22:19.825 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:22:19.907 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 720
2020-08-09 13:23:42.324 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:23:42.333 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:23:42.334 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:23:42.336 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:23:43.179 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:23:44.431 - info: host.OVERWATCH 5 instances found
2020-08-09 13:23:44.449 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:23:44.499 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 744
2020-08-09 13:25:06.114 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:25:06.122 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:25:06.123 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:25:06.125 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:25:06.488 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:25:07.821 - info: host.OVERWATCH 5 instances found
2020-08-09 13:25:07.843 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:25:07.899 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 726
2020-08-09 13:25:17.430 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 775
2020-08-09 13:25:18.104 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 791
2020-08-09 13:25:21.559 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 813
2020-08-09 13:26:13.506 - info: discovery.0 (775) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:26:16.246 - info: influxdb.0 (813) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:26:16.322 - info: influxdb.0 (813) No stored data from last exit found
2020-08-09 13:26:16.357 - info: influxdb.0 (813) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:26:16.538 - info: influxdb.0 (813) Connected!
2020-08-09 13:26:17.393 - info: admin.0 (726) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:26:17.512 - info: admin.0 (726) requesting all states
2020-08-09 13:26:17.518 - info: admin.0 (726) requesting all objects
2020-08-09 13:26:18.037 - info: admin.0 (726) received all objects
2020-08-09 13:26:18.852 - info: info.0 (791) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:26:19.149 - info: admin.0 (726) http server listening on port 8081
2020-08-09 13:26:19.149 - info: admin.0 (726) Use link "http://localhost:8081" to configure.
2020-08-09 13:26:22.690 - info: info.0 (791) Popup news was read...
2020-08-09 13:26:26.506 - info: host.OVERWATCH received SIGTERM
2020-08-09 13:26:26.512 - info: influxdb.0 (813) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 13:26:26.510 - info: host.OVERWATCH stopInstance system.adapter.admin.0 (force=false, process=true)
2020-08-09 13:26:26.511 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 (force=false, process=true)
2020-08-09 13:26:26.512 - info: host.OVERWATCH stopInstance system.adapter.info.0 (force=false, process=true)
2020-08-09 13:26:26.512 - info: host.OVERWATCH stopInstance system.adapter.influxdb.0 (force=false, process=true)
2020-08-09 13:26:26.541 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=false)
2020-08-09 13:26:26.543 - info: host.OVERWATCH stopInstance system.adapter.admin.0 send kill signal
2020-08-09 13:26:26.550 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 send kill signal
2020-08-09 13:26:26.552 - info: host.OVERWATCH stopInstance system.adapter.info.0 send kill signal
2020-08-09 13:26:27.544 - info: host.OVERWATCH stopInstance system.adapter.admin.0 killing pid 726
2020-08-09 13:26:27.551 - info: host.OVERWATCH stopInstance system.adapter.discovery.0 killing pid 775
2020-08-09 13:26:27.554 - info: host.OVERWATCH stopInstance system.adapter.info.0 killing pid 791
2020-08-09 13:26:28.542 - info: host.OVERWATCH stopInstance timeout 2000 system.adapter.influxdb.0 killing pid 813
2020-08-09 13:26:29.397 - info: host.OVERWATCH instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-08-09 13:26:29.398 - info: host.OVERWATCH All instances are stopped.
2020-08-09 13:26:29.406 - warn: host.OVERWATCH instance system.adapter.admin.0 terminated due to SIGTERM
2020-08-09 13:26:29.406 - info: host.OVERWATCH instance system.adapter.admin.0 terminated with code null ()
2020-08-09 13:26:29.407 - info: host.OVERWATCH All instances are stopped.
2020-08-09 13:26:29.407 - warn: host.OVERWATCH instance system.adapter.discovery.0 terminated due to SIGTERM
2020-08-09 13:26:29.408 - info: host.OVERWATCH instance system.adapter.discovery.0 terminated with code null ()
2020-08-09 13:26:29.408 - info: host.OVERWATCH All instances are stopped.
2020-08-09 13:26:29.408 - warn: host.OVERWATCH instance system.adapter.info.0 terminated due to SIGTERM
2020-08-09 13:26:29.409 - info: host.OVERWATCH instance system.adapter.info.0 terminated with code null ()
2020-08-09 13:26:29.409 - info: host.OVERWATCH All instances are stopped.
2020-08-09 13:26:29.551 - info: host.OVERWATCH terminated
2020-08-09 13:26:59.619 - info: host.OVERWATCH iobroker.js-controller version 3.1.6 js-controller starting
2020-08-09 13:26:59.627 - info: host.OVERWATCH Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-08-09 13:26:59.628 - info: host.OVERWATCH hostname: OVERWATCH, node: v10.22.0
2020-08-09 13:26:59.630 - info: host.OVERWATCH ip addresses: 192.168.10.99 fe80::8fde:4fa3:8434:eacc
2020-08-09 13:27:00.018 - info: host.OVERWATCH connected to Objects and States
2020-08-09 13:27:02.271 - info: host.OVERWATCH 5 instances found
2020-08-09 13:27:02.300 - info: host.OVERWATCH starting 4 instances
2020-08-09 13:27:02.354 - info: host.OVERWATCH instance system.adapter.admin.0 started with pid 747
2020-08-09 13:27:10.660 - info: host.OVERWATCH instance system.adapter.discovery.0 started with pid 765
2020-08-09 13:27:12.013 - info: host.OVERWATCH instance system.adapter.info.0 started with pid 777
2020-08-09 13:27:15.369 - info: host.OVERWATCH instance system.adapter.influxdb.0 started with pid 784
2020-08-09 13:27:40.953 - info: discovery.0 (765) starting. Version 2.3.7 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:27:45.333 - info: influxdb.0 (784) starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.influxdb, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:27:45.371 - info: influxdb.0 (784) No stored data from last exit found
2020-08-09 13:27:45.374 - info: influxdb.0 (784) Connecting http://127.0.0.1:8086 ...
2020-08-09 13:27:46.949 - info: influxdb.0 (784) Connected!
2020-08-09 13:27:49.903 - info: admin.0 (747) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:27:50.032 - info: admin.0 (747) requesting all states
2020-08-09 13:27:50.033 - info: admin.0 (747) requesting all objects
2020-08-09 13:27:50.685 - info: admin.0 (747) received all objects
2020-08-09 13:27:51.457 - info: info.0 (777) starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.info, node: v10.22.0, js-controller: 3.1.6
2020-08-09 13:27:52.061 - info: admin.0 (747) http server listening on port 8081
2020-08-09 13:27:52.062 - info: admin.0 (747) Use link "http://localhost:8081" to configure.
2020-08-09 13:27:55.171 - info: info.0 (777) Popup news was read...
2020-08-09 13:57:51.570 - info: info.0 (777) Popup news was read...
2020-08-09 14:27:51.563 - info: info.0 (777) Popup news was read...
2020-08-09 14:57:51.566 - info: info.0 (777) Popup news was read...
2020-08-09 15:27:51.583 - info: info.0 (777) Popup news was read...
2020-08-09 15:57:51.598 - info: info.0 (777) Popup news was read...
2020-08-09 16:27:51.573 - info: info.0 (777) Popup news was read...
2020-08-09 16:57:51.581 - info: info.0 (777) Popup news was read...
2020-08-09 17:08:59.953 - info: host.OVERWATCH "system.adapter.daikin.0" enabled
2020-08-09 17:08:59.988 - info: host.OVERWATCH instance system.adapter.daikin.0 started with pid 4657
2020-08-09 17:09:01.793 - info: daikin.0 (4657) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.daikin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 17:09:02.721 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:09:02.721 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:10:02.953 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:10:02.954 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:11:03.180 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:11:03.181 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:12:03.411 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:12:03.412 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:13:03.645 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:13:03.646 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:14:03.869 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:14:03.870 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:15:04.094 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:15:04.095 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:16:04.327 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:16:04.328 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:16:54.230 - info: host.OVERWATCH iobroker add daikin --host OVERWATCH
2020-08-09 17:16:56.711 - info: host.OVERWATCH iobroker host.OVERWATCH create instance daikin
2020-08-09 17:16:56.721 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.sigKill created
2020-08-09 17:16:56.751 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.eventLoopLag created
2020-08-09 17:16:56.781 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.outputCount created
2020-08-09 17:16:56.809 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.inputCount created
2020-08-09 17:16:56.838 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.uptime created
2020-08-09 17:16:56.867 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.memRss created
2020-08-09 17:16:56.896 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.memHeapTotal created
2020-08-09 17:16:56.925 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.memHeapUsed created
2020-08-09 17:16:56.953 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.cputime created
2020-08-09 17:16:56.982 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.cpu created
2020-08-09 17:16:57.011 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.compactMode created
2020-08-09 17:16:57.040 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.connected created
2020-08-09 17:16:57.071 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1.alive created
2020-08-09 17:16:57.107 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.1 created
2020-08-09 17:16:58.129 - info: host.OVERWATCH iobroker exit 0
2020-08-09 17:17:04.596 - info: daikin.0 (4657) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:17:04.597 - info: daikin.0 (4657) Retry init in 60 seconds
2020-08-09 17:17:15.070 - info: host.OVERWATCH iobroker del daikin.0
2020-08-09 17:17:16.761 - info: host.OVERWATCH iobroker Delete adapter "daikin.0"
2020-08-09 17:17:16.769 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 1 instances of daikin.0
2020-08-09 17:17:16.786 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 14 states of system.adapter.daikin.0
2020-08-09 17:17:16.796 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 14 states (system.adapter.daikin.0.*) from states
2020-08-09 17:17:17.162 - info: host.OVERWATCH iobroker host.OVERWATCH Deleting 15 object(s).
2020-08-09 17:17:17.482 - info: host.OVERWATCH object deleted system.adapter.daikin.0
2020-08-09 17:17:17.483 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=true)
2020-08-09 17:17:17.488 - info: daikin.0 (4657) Got terminate signal TERMINATE_YOURSELF
2020-08-09 17:17:17.485 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 send kill signal
2020-08-09 17:17:17.490 - info: daikin.0 (4657) terminating
2020-08-09 17:17:17.492 - info: daikin.0 (4657) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 17:17:17.498 - info: host.OVERWATCH iobroker host.OVERWATCH Deleting 14 state(s).
2020-08-09 17:17:18.013 - error: host.OVERWATCH instance system.adapter.daikin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-08-09 17:17:18.013 - info: host.OVERWATCH Do not restart adapter system.adapter.daikin.0 because desired by instance
2020-08-09 17:17:18.608 - info: host.OVERWATCH iobroker exit 0
2020-08-09 17:17:39.147 - info: host.OVERWATCH "system.adapter.daikin.1" enabled
2020-08-09 17:17:39.176 - info: host.OVERWATCH instance system.adapter.daikin.1 started with pid 4756
2020-08-09 17:17:40.401 - info: daikin.1 (4756) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.daikin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 17:17:40.823 - info: daikin.1 (4756) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:17:40.824 - info: daikin.1 (4756) Retry init in 60 seconds
2020-08-09 17:17:56.362 - info: host.OVERWATCH iobroker del daikin.1
2020-08-09 17:17:58.156 - info: host.OVERWATCH iobroker Delete adapter "daikin.1"
2020-08-09 17:17:58.164 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 1 instances of daikin.1
2020-08-09 17:17:58.181 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 14 states of system.adapter.daikin.1
2020-08-09 17:17:58.191 - info: host.OVERWATCH iobroker host.OVERWATCH Counted 14 states (system.adapter.daikin.1.*) from states
2020-08-09 17:17:58.553 - info: host.OVERWATCH iobroker host.OVERWATCH Deleting 15 object(s).
2020-08-09 17:17:59.002 - info: host.OVERWATCH object deleted system.adapter.daikin.1
2020-08-09 17:17:59.002 - info: host.OVERWATCH stopInstance system.adapter.daikin.1 (force=false, process=true)
2020-08-09 17:17:59.004 - info: host.OVERWATCH stopInstance system.adapter.daikin.1 send kill signal
2020-08-09 17:17:59.009 - info: daikin.1 (4756) Got terminate signal TERMINATE_YOURSELF
2020-08-09 17:17:59.011 - info: daikin.1 (4756) terminating
2020-08-09 17:17:59.013 - info: daikin.1 (4756) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-08-09 17:17:59.032 - info: host.OVERWATCH iobroker host.OVERWATCH Deleting 14 state(s).
2020-08-09 17:17:59.569 - error: host.OVERWATCH instance system.adapter.daikin.1 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-08-09 17:17:59.570 - info: host.OVERWATCH Do not restart adapter system.adapter.daikin.1 because desired by instance
2020-08-09 17:18:00.223 - info: host.OVERWATCH iobroker exit 0
2020-08-09 17:27:51.570 - info: info.0 (777) Popup news was read...
2020-08-09 17:35:53.999 - info: host.OVERWATCH iobroker add daikin --host OVERWATCH
2020-08-09 17:35:55.746 - info: host.OVERWATCH iobroker host.OVERWATCH create instance daikin
2020-08-09 17:35:55.756 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.sigKill created
2020-08-09 17:35:55.786 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.eventLoopLag created
2020-08-09 17:35:55.816 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.outputCount created
2020-08-09 17:35:55.845 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.inputCount created
2020-08-09 17:35:55.875 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.uptime created
2020-08-09 17:35:55.905 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.memRss created
2020-08-09 17:35:55.935 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.memHeapTotal created
2020-08-09 17:35:55.964 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.memHeapUsed created
2020-08-09 17:35:55.993 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.cputime created
2020-08-09 17:35:56.022 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.cpu created
2020-08-09 17:35:56.051 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.compactMode created
2020-08-09 17:35:56.083 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.connected created
2020-08-09 17:35:56.113 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0.alive created
2020-08-09 17:35:56.148 - info: host.OVERWATCH iobroker host.OVERWATCH object system.adapter.daikin.0 created
2020-08-09 17:35:57.171 - info: host.OVERWATCH iobroker exit 0
2020-08-09 17:36:13.921 - info: host.OVERWATCH "system.adapter.daikin.0" enabled
2020-08-09 17:36:13.936 - info: host.OVERWATCH instance system.adapter.daikin.0 started with pid 4923
2020-08-09 17:36:15.185 - info: daikin.0 (4923) starting. Version 1.0.5 in /opt/iobroker/node_modules/iobroker.daikin, node: v10.22.0, js-controller: 3.1.6
2020-08-09 17:36:15.951 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:36:15.952 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:37:16.192 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:37:16.193 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:38:16.433 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:38:16.434 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:39:16.672 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:39:16.673 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:40:16.910 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:40:16.911 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:41:17.149 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:41:17.150 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:42:17.384 - info: daikin.0 (4923) Daikin Device initialized with Error :Unknown response: ret=LPW NG
2020-08-09 17:42:17.386 - info: daikin.0 (4923) Retry init in 60 seconds
2020-08-09 17:42:21.577 - info: host.OVERWATCH "system.adapter.daikin.0" disabled
2020-08-09 17:42:21.587 - info: daikin.0 (4923) Got terminate signal TERMINATE_YOURSELF
2020-08-09 17:42:21.579 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 (force=false, process=true)
2020-08-09 17:42:21.581 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 send kill signal
2020-08-09 17:42:22.584 - info: host.OVERWATCH stopInstance system.adapter.daikin.0 killing pid 4923
2020-08-09 17:42:24.242 - info: host.OVERWATCH instance system.adapter.daikin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

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.daikin

[E114] No adapter are allowed in the repo without admin3 support
[E150] No common.connectionType found in io-package.json
[E152] No common.dataSource found in io-package.json
[E802] No topics found in the repository. Please go to "https://github.com/Apollon77/ioBroker.daikin", press the settings button beside the about title and add some topics.
[E605] No actual year found in copyright. Please add "Copyright (c) 2017-2021 Ingo Fischer [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2021 Ingo Fischer [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

Sending commands won´t work

I have 3 different Daikin devices. I can connect and read all data of the devices since years without problems.
Now i want to turn off one device if water was detected by Homematic Watersensor.
In future i want to use the excess energy of my PV system. So i must turn on/off by ioBroker.
Unfortunately the device will not react on sended commands. Not power, not fan speed, no fan direction.
I have try the other devices. No react also.
Switching to HTTP-GET won´t help. No errors or infos in logs.

I have a ATXS35G1V2B (Siesta), a FTXS50K3V1B (Professional) and a new FTXA50B2V1BT (Stylish). WiFi Firmware on all devices 1.2.54
Any idea?

Update: Wifi Firmware Update to 1.14.18 on all devices over Residental App but no change :-(

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.

Status Details

✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ continuous-integration/appveyor/branch: AppVeyor 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 🌴

Update stable version in repo from 1.0.5 to 1.1.2

Think about update stable version to 1.1.2

Version: stable=1.0.5 (423 days old) => latest=1.1.2 (15 days old)
Installs: stable=213 (71.48%), latest=61 (20.47%), total=298
Click to edit

Error while communicating with Daikin device: ECONNRESET

Hallo Ingo!
Leider habe ich jetzt auch immer öfter diese Fehlermeldung, eine Steuerung ist nicht mehr möglich. Erst wenn ich die App am Handy aktiviere, die Anlage damit ein-/ausschalte ist der ioBroker kurzfristig aktuell.
Hier die Logeinträge im ioBroker Log.
`

daikin.0	2019-06-24 00:24:46.816	info	Retry init in 60 seconds
daikin.0	2019-06-24 00:24:46.816	info	Daikin Device initialized with Error :Error: Error while communicating with Daikin device: ECONNRESET
daikin.0	2019-06-24 00:24:46.816	debug	null
daikin.0	2019-06-24 00:24:45.802	debug	Call GET http://192.168.0.15/common/basic_info with undefined
daikin.0	2019-06-24 00:24:45.693	info	starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.daikin, node: v8.15.0
daikin.0	2019-06-24 00:24:45.664	debug	statesDB connected
daikin.0	2019-06-24 00:24:45.623	debug	objectDB connected
host.iobroker-master-tb	2019-06-24 00:24:44.901	info	instance system.adapter.daikin.0 started with pid 29968

Support for Daikin FTXM20N and FTXM35N (Perfera) requested

I just installed new Perfera units. As far as I see only the on/off power command works with the present version 1.1.2 (GET on or off). Indoor and outdoor temperatures are shown. What details of the Wifi module and firmware are needed to extend the adapter for these models? Thanks for any efforts

Update stable version in repo from 1.1.2 to 1.1.3

Think about update stable version to 1.1.3

Version: stable=1.1.2 (120 days old) => latest=1.1.3 (15 days old)
Installs: stable=143 (43.2%), latest=58 (17.52%), total=331
Click to edit

Please check ioBroker.daikin 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.

Make adapter ready for Admin v3

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

ECONNRESET Error

Hello,

got the problem on my adapter (V1.0.5) on ioBroker in regular time.

JS 3.1.6
Node.js v12.17.0
NPM 6.14.4

"Error updating data: Error: Error while communicating with Daikin device: ECONNRESET"

Try different actualisation times, but it didn't work.
100s, 300s, 600s

May you got an ideo how I can solve this problem?

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.

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 🌴

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!

Keine Luftfeuchtigkeitsanzeige

Leider wird der Datenpunkt "sensorInfo.indoorHumidity" nicht beschrieben. Es steht nur "null%" drin.
Im Log leider keine Ausgabe.
Meine Anlage: FTXP20M5V1B

Versions:

Adapter version: 1.3.0
JS-Controller version: 3.2.16
Node version: 12.21.0

postpone state changes because last change not finished

check why and fix

Adapter sends event triggers only for changed values

Hey Apollon77,

I use your adapter to controll and update the daikin data on my smarthome server. When rebooting the smarthome server the daikin data is missing and it is only updated when the data has changed.
I use the javascript adapter to get the data and transfer it to the smarthome server, there I can trigger on "on refresh" or "on changed". Currently only "on changed" data is sent by your adapter.
It would be really nice if you could also send data to the "on refresh" trigger (which means that the data can be the same or has changed) each time the data from the daikin controller has been read.

Thanks!
Marc

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!

Provide read/write access to the daily/weekly time plan (Timer)

Is your feature request related to a problem? Please describe.
I have setup a weekly plan for my indoor device(s) and want to enable/disable it dependent on my (Homematic) "atHome" status.

Describe the solution you'd like
A way to enable/disable the weekly or daily plan by changing the objects in the adapter, similar to the app.

Describe alternatives you've considered
Simulating a schedule by a combination of ioBroker scripts considering my (Homematic) "atHome" status.

Additional context
Host: RasberryPi 3B
Node.js: 12.20.0
NPM: 6.14.9
Indoor device: FXTA (Stylish)
Adapter type: BRP084A42-1
Adapter HW: 1.1.3
Adapter FW: 1.2.51
Controller App: 2.5.1

https://user-images.githubusercontent.com/30027622/104690147-2d835700-5704-11eb-8e41-9eeb997bf252.jpg
https://user-images.githubusercontent.com/30027622/104579183-f0638a00-565b-11eb-8559-47637a240421.jpg

Compatibility with other Daikin WiFi Modules?

Dear Maintainer,
Is your module also compatible to the devices called BRP069B41, BRP069B42 and BRP069B43?

Regards

please make the common.name configurable

I have 4 instances for 4 Units in 4 rooms.

I had renamed the common name of the device to "Daikin RoomName".
The today's update overwrote them with "Daikin device"

It would be nice if at least the common name of the device could stay the same if altered by user, or could be configured in the instances settings

Is Emura Series supported?

Hi, is the Emura Series supported by this adapter?
I am thinking about an FTXJ35MW - R32.

TypeError: Cannot read property 'power' of null

Sentry Issue: IOBROKER-DAIKIN-P

TypeError: Cannot read property 'power' of null
  File "/opt/iobroker/node_modules/iobroker.daikin/daikin.js", line 442, in storeDaikinData
    if (basicInfo.power !== undefined) {
  File "/opt/iobroker/node_modules/iobroker.daikin/daikin.js", line 357, in null.<anonymous>
    storeDaikinData(err);
  File "/opt/iobroker/node_modules/daikin-controller/lib/DaikinAC.js", line 142, in null.<anonymous>
    if (callback) callback(errFinal, daikinGetResponse);
  File "/opt/iobroker/node_modules/daikin-controller/lib/DaikinAC.js", line 119, in null.<anonymous>
    if (callback) callback(err, daikinResponse);
  File "/opt/iobroker/node_modules/daikin-controller/lib/DaikinACRequest.js", line 424, in parseResponse
    callback(null, ret, mappedResponse);
...
(5 additional frame(s) were not displayed)

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.

apollon77 / iobroker.daikin Goto Github PK

iobroker.daikin's Introduction

ioBroker.daikin

Disclaimer

Description of parameters

daikinIp

pollingInterval

Description of the available instance objects/states

Todo

Changelog

WORK IN PROGRESS

1.4.2 (2022-07-25)

1.4.1 (2022-06-27)

1.4.0 (2022-06-09)

1.3.3 (2021-06-24)

1.3.2 (2021-06-05)

1.3.1 (2021-05-14)

1.3.0 (2021-01-14)

1.2.0 (2020-12-27)

1.1.3 (2020-11-19)

1.1.2 (2020-08-06)

1.1.1 (2020-08-02)

1.1.0 (2020-07-21)

1.0.4 (2019-06-25)

1.0.3 (2019-02-xx)

1.0.2 (2018-04-29)

1.0.1 (2018-04-13)

1.0.0 (2018-01-1x)

0.2.3 (2017-04-01)

0.2.2

0.2.0

0.1.x

License

iobroker.daikin's People

Contributors

Stargazers

Watchers

Forkers

iobroker.daikin's Issues

The devDependency nyc was updated from 15.0.1 to 15.1.0.

Think about update stable version to 1.3.3

Think about update stable version to 1.4.0

Version 1.1.2 of daikin-controller was just published.

Think about update stable version to 1.2.0

Version 1.1.1 of daikin-controller was just published.

Think about update stable version to 1.3.0

The devDependency mocha was updated from 6.0.2 to 6.1.0.

6.1.0 / 2019-04-07

🔒 Security Fixes

🎉 Enhancements

📠 Deprecations

🐛 Fixes

📖 Documentation

🔩 Other

Think about update stable version to 1.3.1

The devDependency nyc was updated from 13.1.0 to 13.2.0.

Think about update stable version to 1.1.2

Think about update stable version to 1.1.3

Version 12.0.1 of nyc was just published.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency nyc was updated from `15.0.1` to `15.1.0`.

The devDependency mocha was updated from `6.0.2` to `6.1.0`.

The devDependency nyc was updated from `13.1.0` to `13.2.0`.