I configured the viessman connector ad can read the values from vcontrold using a local vito.xml. If i get positive values from the Kolektor Temperature it is working with sql history adapter, becasue the values are shown as numbers only. but if vcontrold returns a negative temperature, the number and a string "Grad Celsius" is shown, which isnt only a number anymore. This is occurs only on negative temperture values:
Error in iobroker.log:
sql.0 2018-10-31 06:11:55.005 info Do not store value "-1.500000 Grad Celsius" for viessmann.0.get.TempKol because no number

Is this a problem within the adapter or in vcontrold ?

Think about update stable version to 1.3.1

Version: stable=1.3.0 (40 days old) => latest=1.3.1 (30 days old)
Installs: stable=186 (35.23%), latest=72 (13.64%), total=528
Click to edit

Dear Adapter develop,

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

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

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

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

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

Please close the issue after you checked it.

Thank you very much for your support!

Think about update stable version to 1.3.1

Version: stable=1.3.0 (41 days old) => latest=1.3.1 (31 days old)
Installs: stable=183 (34.72%), latest=76 (14.42%), total=527
Click to edit

Ich bekomme immer wieder diese Meldung bei iobroker im Log.
Und meine Daten bei den Objekten stimmen dann nicht mehr (siehe Bild):

Was mache ich falsch ?

viesman_adapter.log

vcontrold.log

vcontrold.xml.txt

vito.xml.txt

For no reasons- suddently Viessmann adapter is not working any longer. Iam using pihole with various security setting (DNS over TLS etc.). My credentilas are working in the app. Is there any website to test the credentials? I deletet the refresh token, put in my email and password... tried to reconnect... Today i changed the fritzbox security-settings from "wpa2(ccmp)" to "wpa2+wpa3". Vitaconnect is still connected with WPA2. The vitaconnect is still im my router and has internet access.
-> i dont thinks this is the problem. Just tried login via website and personal hotspot- still no success.

I tried login at (found it somewhere, think clientID is maybe wrong)
https://iam.viessmann.com/idp/v1/authorize?client_id=79742319e39245de5f91d15ff4cac2a8&scope=openid&redirect_uri=vicare://oauth-callback/everest&response_type=code
I can input my email and passwort but nothing happens.

If i try this with my oauth token:
https://iam.viessmann.com/idp/v1/authorize?client_id=VtDTal7nzhHUAsP2DOLyv9SqWeI3e2a8&scope=openid&redirect_uri=vicare://oauth-callback/everest&response_type=code
{"error":"Client not registered."}

Any ideas?

Hi,

I've already seen #41, but may request is different. Would it be possible to log the command, that produced "command unknown"? I have several entries - more than 50 entries in less than 1 hour - in my log, but don't know which command triggered this warning. Most log lines contain the same message. For now I see two different codes in front of the message: (1952) and (32413). I don't know, if that code has any meaning regarding the issue itself.

Thanks for your help!

Hallo,

Adapter läuft bei mir mit einigen Werten und Lesen funktioniert .

Ich würde allerdings gerne die 1xWW Funktion triggern, also setzen.

Sehe aber in der Oberfläche keine Setzdatenpunkte.

Habe auch schon mehrere Vito.xml versucht...

If you do not use www and widgets, you can delete it completely.

Einlesen der Vito.xml über ssh funktioniert, jedoch werden Abfrage- und Setzdatenpunkte nicht in der Instanzkonfiguration aktualisiert.

A JSON with only one entry cannot be imported. Hitting import in the admin interface seems to do nothing. Tested with Chrome v56.0 and Firefox v.51.0.1 .

{
  "vito": {
    "devices": {
      "device": {
        "-ID": "20CB",
        "-name": "V200KW2",
        "-protocol": "KW2"
      }
    },
    "commands": {
      "command": {
        "-name": "getTempA",
        "-protocmd": "getaddr",
        "addr": "5525",
        "len": "2",
        "unit": "UT",
        "error": "05 05",
        "description": "Aussentemperatur"
      }
    }
  }
}

Was mache ich, wenn vcontrold auf einem Raspberry läuft
und die Verbindung kann nur mit einem RSA Key aufgebaut werden?

The states, that are created for this adapter, do not have the 'type' property.
This leads to an unclear definition and can cause problems for other adapters, e.g. Statistics.
Current:

{
  "from": "system.adapter.viessmann.0",
  "ts": 1543693154688,
  "common": {
    "name": "VitoTempVLSoll",
    "desc": "Vorlaufsolltemperatur in °C",
    "custom": {
      "sql.0": {
        "enabled": true,
        "changesOnly": true,
        "debounce": "1000",
        "maxLength": 10,
        "retention": 0,
        "changesRelogInterval": 0,
        "changesMinDelta": 0,
        "storageType": "",
        "aliasId": ""
      }
    }
  },
  "native": {},
  "acl": {
    "object": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1636
  },
  "_id": "viessmann.0.get.VitoTempVLSoll",
  "type": "state"
}

Better:

{
  "from": "system.adapter.viessmann.0",
  "ts": 1543693154688,
  "common": {
    "name": "VitoTempVLSoll",
    "desc": "Vorlaufsolltemperatur in °C",
    "type": "number",
    "custom": {
      "sql.0": {
        "enabled": true,
        "changesOnly": true,
        "debounce": "1000",
        "maxLength": 10,
        "retention": 0,
        "changesRelogInterval": 0,
        "changesMinDelta": 0,
        "storageType": "",
        "aliasId": ""
      }
    }
  },
  "native": {},
  "acl": {
    "object": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1636
  },
  "_id": "viessmann.0.get.VitoTempVLSoll",
  "type": "state"
}

Seit dem Update auf js-controller 3.3.x kommen solche Warnungen im log:
warn: viessmann.0 (19188) Read-only state "viessmann.0.info.timeout_connection" has been written without ack-flag with value "false"
warn: viessmann.0 (19188) Read-only state "viessmann.0.info.lastPoll" has been written without ack-flag with value "1620048828"

I love this adapter. For me, it works nearly flawlessly over years. However, there is one thing I would like to see.

After a restart of my Raspberry with vcontrold installed on it the adapter loses its connection and the respective ioBroker "light" turns yellow. Therefore, I would appreciate it when the adapter automatically does at least one restart after e.g. 10 minutes of losing its connection to vcontrold. Would this be possible?

Cheers,

Thorsten

Die Adpater Config Seite sollte einen Reiter "Changelog" enthalten.

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/misanorot/ioBroker.viessmann

• [E603] NO "## Changelog" found in README.md

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

• [W113] Adapter should support compact mode

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

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

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/misanorot/ioBroker.viessmann

• [E603] NO "## Changelog" found in README.md

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

• [W113] Adapter should support compact mode

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

Guten Tag,
ich bekomme öfters die o.g. Fehlermeldung im log von iobroker.
Danach geht nichts mehr.
Der Adapter ist aber weiterhin grün. Es kommen aber keine Daten mehr an.
Der Raspi ist auch weiterhin erreichbar per winscp.

siehe auch:
https://forum.iobroker.net/viewtopic.php?f=20&t=13671

Es wäre schön wenn es hier eine Lösung geben würde.
Ich weiß jedenfalls nicht mehr weiter.

mfg
Dieter

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/misanorot/ioBroker.viessmann

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.viessmann"

ERR:["E201"]:ERR

Thanks,
your automatic adapter checker.

I can help you if you want to upload vito.xml file into the dialog and all values will be automatically taken from this file.

Please delete the widget dir if no widgets implemented. It will create the unneeded load on vis.

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

iobroker and the Viessmann adapter (0.2.4) are running on a RPi3 together with vcontrold (r107).

vcontrold works and is responding to "telnet 127.0.0.1 3002" just fine.
In iobroker I can't get the Viessmann adapter running, it immediately quits with:

piheizung	2017-01-23 19:57:35.871	error	host.piheizung instance system.adapter.viessmann.0 terminated with code 1 ()
piheizung	2017-01-23 19:57:35.506	info	host.piheizung instance system.adapter.viessmann.0 started with pid 23376
piheizung	2017-01-23 19:57:27.486	info	host.piheizung Restart adapter system.adapter.viessmann.0 because enabled

I tried to run with my full blown vito.xml as well as a reduced json version:

{
  "vito": {
    "devices": {
      "device": {
        "-ID": "20CB",
        "-name": "VScotHO1",
        "-protocol": "KW2"
      }
    },
    "commands": {
      "command": [
        {
          "-name": "getTempA",
          "-protocmd": "getaddr",
          "addr": "0800",
          "len": "2",
          "unit": "UT",
          "description": "Außentemperatur in °C"
        },
        {
          "-name": "getTempATp",
          "-protocmd": "getaddr",
          "addr": "5525",
          "len": "2",
          "unit": "UT",
          "description": "Außentemperatur in °C (Tiefpass)"
        }
      ]
    }
  }
}

It always ends with this error. As the error message is rather unspecific, I do not know what else to check. Any hint would be appreciated.

I currently have a strange problem: After an indefinite time the vcontrold seems to report a read error and then the Viessmann adapter hangs up:

2018-05-25 03:10:37.397  - �[34mdebug�[39m: viessmann.0 Wait for next run: 31 in ms
2018-05-25 03:10:37.429  - �[34mdebug�[39m: viessmann.0 Next poll: getLeistungIst
2018-05-25 03:10:37.491  - �[35msilly�[39m: viessmann.0 redis publish io.viessmann.0.get.LeistungIst {"val":0,"ack":true,"ts":1527210637491,"q":0,"from":"system.adapter.viessmann.0","lc":1527208866356}
2018-05-25 03:10:37.494  - �[34mdebug�[39m: viessmann.0 Wait for next run: 9435 in ms
2018-05-25 03:10:45.263  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.alive {"val":true,"ack":true,"ts":1527210645262,"q":0,"from":"system.adapter.viessmann.0","lc":1527025532172}
2018-05-25 03:10:45.266  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.connected {"val":true,"ack":true,"ts":1527210645265,"q":0,"from":"system.adapter.viessmann.0","lc":1527025532174}
2018-05-25 03:10:45.267  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.memRss {"val":32.2,"ack":true,"ts":1527210645267,"q":0,"from":"system.adapter.viessmann.0","lc":1527210645267}
2018-05-25 03:10:45.268  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.memHeapTotal {"val":14.98,"ack":true,"ts":1527210645268,"q":0,"from":"system.adapter.viessmann.0","lc":1527025757250}
2018-05-25 03:10:45.270  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.memHeapUsed {"val":11.54,"ack":true,"ts":1527210645269,"q":0,"from":"system.adapter.viessmann.0","lc":1527210645269}
2018-05-25 03:10:45.271  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.uptime {"val":185115,"ack":true,"ts":1527210645271,"q":0,"from":"system.adapter.viessmann.0","lc":1527210645271}
2018-05-25 03:10:45.272  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.inputCount {"val":0,"ack":true,"ts":1527210645272,"q":0,"from":"system.adapter.viessmann.0","lc":1527108724068}
2018-05-25 03:10:45.274  - �[35msilly�[39m: viessmann.0 redis publish io.system.adapter.viessmann.0.outputCount {"val":14,"ack":true,"ts":1527210645273,"q":0,"from":"system.adapter.viessmann.0","lc":1527210645273}
2018-05-25 03:10:46.933  - �[34mdebug�[39m: viessmann.0 Next poll: getTempKist
2018-05-25 03:10:46.936  - �[33mwarn�[39m: viessmann.0 Vctrld send ERROR: ERR: <RECV: read eof
>FRAMER: read failure 1
Error in send, terminating
Error executing getTempKist
vctrld>
2018-05-25 03:10:46.937  - �[34mdebug�[39m: viessmann.0 Wait for next run: 110 in ms
2018-05-25 03:10:47.048  - �[34mdebug�[39m: viessmann.0 Next poll: getTempAbgas
2018-05-25 03:10:47.050  - �[33mwarn�[39m: viessmann.0 Vctrld send ERROR: ERR: <RECV: read eof
>FRAMER: read failure 1
Error in send, terminating
Error executing getTempAbgas

2018-05-25 03:10:47.051  - �[34mdebug�[39m: viessmann.0 Wait for next run: 67 in ms
2018-05-25 03:10:47.118  - �[34mdebug�[39m: viessmann.0 Next poll: getTempKsoll
2018-05-25 03:10:47.121  - �[33mwarn�[39m: viessmann.0 Vctrld send ERROR: ERR: <RECV: read eof
>FRAMER: read failure 1
Error in send, terminating
Error executing getTempKsoll

It does not seem to be a be a problem (at least not a permanent one) of vcontrold. When I restart the adapter it again connects fine to vcontrold and resumes operation.

Is there a way to make the adapter handle such errors more gracefully?

Please let this adapter working with the viessmann api.
Check: https://github.com/thetrueavatar/Viessmann-Api/blob/develop/README-en.md

Thanks!

Dear folks,

I have a strange error here. Vcontrold is setup up correctly, I can connect to it via telnet, issue commands and receive values. Converting the vito.xml into JSON worked and the adapter said everything was fine. All functions can be accessed via the admin interface. For testing purposes, I wanted to read out only one value each minute. But when using iobroker, the daemon hangs and the following lines are plotted to the log

viessmann.0 2017-02-20 15:47:41.680 warn viessmann.0 No states found for {"type":"state","common":{"name":"","desc":"Testabfrage, Adresse eingeben"},"native":{},"_id":"viessmann.0.get."}' 'viessmann.0 2017-02-20 15:47:41.430 warn vctrld>' 'viessmann.0 2017-02-20 15:47:41.430 warn Vctrld send ERROR: vctrld>ERR: command unknown

Any ideas?

Hallo,
hab hier mal eine allgemeine Frage zur Anbindung einer Viesmann Gastherme Vitodens 300-W BH3HF mit internen RF-Modul WiFi Modul. Die Anlage hängt im internem WLAN mit Freigabe und kann auch über die APP ViCare über die Viesmann Cloud bedient und überwacht werden.

Kann über einen io-Broker diese Gastherme auch direkt ausgelesen und bedient werden ohne den Umweg über Internet und Viessmann Cloud/anmeldung?

Hat damit jemand damit Erfahrung? Die Gastherme ist gerade 1 Jahr alt und wurde im Rahmen einer Heizungserneuerung eingebaut.

fragend....

RaGoos

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

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

Hallo,

wenn ich die Option "Datenpunktwerte kürzen" auswähle wird mir bei den Fehlerspeicher Einträgen nur das Datum angezeigt.
Schalte ich die Option aus passen die Error Datenpunkte, aber der Rest ist natürlich kacke.

Kann man das irgendwo umkonfigurieren?

Protokoll: KW2

https://github.com/ioBroker/ioBroker.discovery/tree/master/lib/adapters

Or am I just cannot find it?
#12

Apparently the development of vcontrold continues: https://github.com/openv/vcontrold

Unfortunately I cannot get this daemon to work with ioBroker.viessmann. The connection is reset after a few seconds

[2450] Sat Jan 27 23:18:06 2018 : Client connected 127.0.0.1:33610 (FD:6)
[2450] Sat Jan 27 23:18:06 2018 : Error reading from socket
[2450] Sat Jan 27 23:18:06 2018 : Received SIGPIPE
[2450] Sat Jan 27 23:18:06 2018 : Process 2450 released lock
[2450] Sat Jan 27 23:18:06 2018 : Closed connection (fd:6)

I had no luck in finding the problem. Maybe you could have a look.

Some scripts expects ioBroker as name in repository.
Npm will still stay as iobroker.viessmann.
Rename only github repository.

Change adapter to read vito.xml from vcontrold configuration (/etc/vcontrold/vito.xml) as the adapter presumes a running vcontrold (really not necessary to have the vito.xml twice).

In addition, add function to reload configuration while instance is already present (it's really awful if you have to change something within the vito.xml and have to delete the instance first and reconfigure everything afterwords!)

Like here: https://github.com/ioBroker/ioBroker.discovery/blob/master/io-package.json#L78

Hallo der Adapter läuft soweit.
Wenn ich aber die VITO.XML ändere, etwas hinzufüge bricht die Verbindung ab.

Ich gehe so vor.

1. XML ändern.
2. Über Telnet in Vcontrold die neue XML einlesen.
3. Im IObroker Adapter neue XML einlesen.
4. Neu configurieren.
   Sobald die erste Abfrage kommt. --> Disconnect.

Ich muss den Raspi neu starten.
Vcontrold mit Telnet kann ich noch die Daten abrufen.

Kann wer helfen?

mfg Manuel

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.

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/misanorot/ioBroker.viessmann

• [E802] No topics found in the repository. Please go to "https://github.com/misanorot/ioBroker.viessmann" and press "Manage topics"

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

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!

There are some russian users who wants to use it. But there is no any description, except german.

Add tests. At least basic from https://github.com/ioBroker/ioBroker.template

I upgrade from 0.7.x to 1.0.1 several weeks ago. Since then the adapter stps reading data or writing to the objects. After restarting the adapter continues working. There are no error messages in the log. I have now setup the cron so the adapter is restarted ever x hours. That would be ok if the adapter reads and transmits the send data to the heater. Is it like this? Does the adapter read and transmit the send-data with startup?

Moin Moin,
ich kämfe schon seit Tagen mit dem Adapter.
Er zeigt immer wieder diesen Fehler im log an:

(18695) check vito.xml structure TypeError: Cannot read property '0' of undefined

Ich habe die Datei schon neu formatiert etc, aber nichts geht.
Ich habe auch schon gegoogelt und getestet, komme aber zu keiner Lösung.

Hallo,
ich habe den Adapter auf meinem iobroker installiert. Ich kann auch problemlos die beidem xml Dateien über ssh laden und er erstellt alle Datenpunkte.
Leider verbindet er sich nicht mit der Heizung. Der Adapter bleibt immer gelb und im log kommt ein Timeout.
Auslesen der Heizung über telnet und vclient geht problemlos.
Habe ich irgendwas vergessen um dem Adapter mitzuteilen, dass vcontrold auf einem anderen Rechner läuft? Finde dazu aber nichts in der config.

Viele Grüße

viessmann.0 (19255) State "viessmann.0.get.Dummy" has no existing object, this might lead to an error in future versions

Einige Adapter werden Warnungen ausgeben wenn State-Werte gesetzt werden VOR dem Anlegen von Objekten. Bitte bei den Adapter-Repos melden - was hiermit geschehen ist ;-)

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/misanorot/ioBroker.viessmann

• [E802] No topics found in the repository. Please go to "https://github.com/misanorot/ioBroker.viessmann" and press "Manage topics"

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

EDIT:

Fehler gefunden.

<unit name="SetReturnStatus"> <abbrev>SR</abbrev> <type>enum</type> <enum bytes="00" text="OK"/> <enum bytes="05" text="SYNC (NOT OK)"/> <enum text="NOT OK"/> </unit>

darf nicht verändert werden !!!!

Moin Moin,

Der Adapter stürzt immer nachdem Befehle gesendet wurden sind.

Als Beispiel Partybetrieb:

<unit name='ReturnStatus B0'> <abbrev>RT</abbrev> <type>enum</type> <enum bytes='00' text='0'/> <enum bytes='01' text='1'/> <enum text='?'/> </unit>

<command name='setPartybetrieb' protocmd='setaddr'> <addr>2303</addr> <len>1</len> <unit>RT</unit> <description>'00'='0'; '01'='1'; Setze Partybetrieb</description> </command>

2020-10-05 13:53:37.780 - debug: viessmann.0 (10682) Next poll: heartbeat (For Object: heartbeat)

2020-10-05 13:53:37.794 - debug: viessmann.0 (10682) Received: ERR: command unknown
2020-10-05 13:53:37.838 - debug: viessmann.0 (10682) Next poll: getBetriebsartAnlage (For Object: BetriebsartAnlage)
2020-10-05 13:53:39.922 - debug: viessmann.0 (10682) Received: Abschalt
2020-10-05 13:53:39.968 - debug: viessmann.0 (10682) Next poll: getBetriebsartHK (For Object: BetriebsartHK)
2020-10-05 13:53:40.027 - debug: viessmann.0 (10682) Received: Normal
2020-10-05 13:53:40.078 - debug: viessmann.0 (10682) Next poll: getBetriebsartHKReduziert (For Object: BetriebsartHKReduziert)
2020-10-05 13:53:40.137 - debug: viessmann.0 (10682) Received: 0
2020-10-05 13:53:40.188 - debug: viessmann.0 (10682) Next poll: getBetriebsartHKNormal (For Object: BetriebsartHKNormal)
2020-10-05 13:53:40.244 - debug: viessmann.0 (10682) Received: 1
2020-10-05 13:53:40.288 - debug: viessmann.0 (10682) Next poll: getPartybetrieb (For Object: Partybetrieb)
2020-10-05 13:53:40.347 - debug: viessmann.0 (10682) Received: 1
2020-10-05 13:53:40.399 - debug: viessmann.0 (10682) Wait for next run: 57383 in ms
2020-10-05 13:53:58.517 - info: viessmann.0 (10682) state viessmann.0.set.BetriebsartAnlage changed: Wasser (ack = false)
2020-10-05 13:54:37.809 - debug: viessmann.0 (10682) Set command: setBetriebsartAnlage Wasser
2020-10-05 13:56:37.948 - error: viessmann.0 (10682) Timeout connection error!
2020-10-05 13:56:37.955 - info: viessmann.0 (10682) Connection with Viessmann system disconnected!
2020-10-05 13:59:39.323 - info: host.bro "system.adapter.viessmann.0" disabled
2020-10-05 13:59:39.324 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 13:59:39.329 - info: viessmann.0 (10682) Got terminate signal TERMINATE_YOURSELF
2020-10-05 13:59:39.325 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 13:59:39.330 - info: viessmann.0 (10682) cleaned everything up...
2020-10-05 13:59:39.331 - info: viessmann.0 (10682) terminating
2020-10-05 13:59:39.333 - info: viessmann.0 (10682) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 13:59:39.853 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:00:00.048 - info: host.bro instance system.adapter.daswetter.0 started with pid 20682
2020-10-05 14:00:01.735 - info: daswetter.0 (20682) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.daswetter, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:00:03.193 - info: daswetter.0 (20682) Terminated (NO_ERROR): Without reason
2020-10-05 14:00:03.705 - info: host.bro instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)
2020-10-05 14:02:38.702 - info: tankerkoenig.0 (1141) Reading data from tankerkoenig ...
2020-10-05 14:04:48.159 - info: host.bro "system.adapter.viessmann.0" enabled
2020-10-05 14:04:48.195 - info: host.bro instance system.adapter.viessmann.0 started with pid 27015
2020-10-05 14:04:49.280 - debug: viessmann.0 (27015) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:04:49.318 - debug: viessmann.0 (27015) Objects client ready ... initialize now
2020-10-05 14:04:49.322 - debug: viessmann.0 (27015) Objects create System PubSub Client
2020-10-05 14:04:49.324 - debug: viessmann.0 (27015) Objects create User PubSub Client
2020-10-05 14:04:49.324 - debug: viessmann.0 (27015) Objects client initialize lua scripts
2020-10-05 14:04:49.340 - debug: viessmann.0 (27015) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:04:49.348 - debug: viessmann.0 (27015) objectDB connected
2020-10-05 14:04:49.351 - debug: viessmann.0 (27015) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:04:49.358 - debug: viessmann.0 (27015) States create User PubSub Client
2020-10-05 14:04:49.360 - debug: viessmann.0 (27015) States create System PubSub Client
2020-10-05 14:04:49.371 - debug: viessmann.0 (27015) States connected to redis: 127.0.0.1:9000
2020-10-05 14:04:49.372 - debug: viessmann.0 (27015) statesDB connected
2020-10-05 14:04:50.077 - info: viessmann.0 (27015) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:04:50.161 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 14:04:50.163 - debug: viessmann.0 (27015) try to read xml files
2020-10-05 14:04:50.166 - debug: viessmann.0 (27015) try to create a ssh session
2020-10-05 14:04:50.179 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 14:04:50.182 - info: viessmann.0 (27015) Got terminate signal TERMINATE_YOURSELF
2020-10-05 14:04:50.185 - info: viessmann.0 (27015) cleaned everything up...
2020-10-05 14:04:50.185 - info: viessmann.0 (27015) terminating
2020-10-05 14:04:50.187 - info: viessmann.0 (27015) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 14:04:50.512 - debug: viessmann.0 (27015) FTP session ready
2020-10-05 14:04:50.638 - debug: viessmann.0 (27015) Try to read Vito from: /etc/vcontrold/vito.xml to: /opt/iobroker/node_modules/iobroker.viessmann
2020-10-05 14:04:50.673 - debug: viessmann.0 (27015) Copy vito.xml from server to host successfully
2020-10-05 14:04:50.721 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:04:53.764 - info: host.bro instance system.adapter.viessmann.0 started with pid 27052
2020-10-05 14:04:54.872 - debug: viessmann.0 (27052) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:04:54.923 - debug: viessmann.0 (27052) Objects client ready ... initialize now
2020-10-05 14:04:54.929 - debug: viessmann.0 (27052) Objects create System PubSub Client
2020-10-05 14:04:54.930 - debug: viessmann.0 (27052) Objects create User PubSub Client
2020-10-05 14:04:54.931 - debug: viessmann.0 (27052) Objects client initialize lua scripts
2020-10-05 14:04:54.948 - debug: viessmann.0 (27052) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:04:54.957 - debug: viessmann.0 (27052) objectDB connected
2020-10-05 14:04:54.960 - debug: viessmann.0 (27052) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:04:54.969 - debug: viessmann.0 (27052) States create User PubSub Client
2020-10-05 14:04:54.972 - debug: viessmann.0 (27052) States create System PubSub Client
2020-10-05 14:04:54.984 - debug: viessmann.0 (27052) States connected to redis: 127.0.0.1:9000
2020-10-05 14:04:54.985 - debug: viessmann.0 (27052) statesDB connected
2020-10-05 14:04:55.759 - info: viessmann.0 (27052) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:04:55.785 - debug: viessmann.0 (27052) try to read xml files
2020-10-05 14:04:55.786 - debug: viessmann.0 (27052) try to create a ssh session
2020-10-05 14:04:56.131 - debug: viessmann.0 (27052) FTP session ready
2020-10-05 14:04:56.229 - debug: viessmann.0 (27052) Try to read Vito from: /etc/vcontrold/vito.xml to: /opt/iobroker/node_modules/iobroker.viessmann
2020-10-05 14:04:56.259 - debug: viessmann.0 (27052) Copy vito.xml from server to host successfully
2020-10-05 14:04:56.277 - debug: viessmann.0 (27052) Copy vcontrold.xml from server to host successfully
2020-10-05 14:04:56.316 - debug: viessmann.0 (27052) Types in vcontrold.xml: {"BA":{"type":"enum"},"BAHK":{"type":"uchar"},"T1U":{"type":"uchar"},"TD":{"type":"short"},"BST0":{"type":"uchar"},"BST1":{"type":"uchar"},"BST5":{"type":"uchar"},"BTST0":{"type":"uchar"},"BTST1":{"type":"uchar"},"TI":{"type":"systime"},"RT":{"type":"enum"},"SR":{"type":"enum"}}
2020-10-05 14:04:56.316 - debug: viessmann.0 (27052) Units in vcontrold.xml: {"T1U":{"unit":"°C"},"TD":{"unit":"°C"}}
2020-10-05 14:04:56.317 - info: viessmann.0 (27052) read vcontrold.xml successfull
2020-10-05 14:04:56.353 - info: viessmann.0 (27052) read vito.xml successfull
2020-10-05 14:04:56.383 - info: viessmann.0 (27052) Connect with Viessmann sytem!
2020-10-05 14:04:56.385 - debug: viessmann.0 (27052) Wait for next run: 60000 in ms
2020-10-05 14:04:56.429 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 14:04:56.430 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 14:04:56.435 - info: viessmann.0 (27052) Got terminate signal TERMINATE_YOURSELF
2020-10-05 14:04:56.437 - info: viessmann.0 (27052) cleaned everything up...
2020-10-05 14:04:56.438 - info: viessmann.0 (27052) terminating
2020-10-05 14:04:56.439 - info: viessmann.0 (27052) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 14:04:56.958 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:04:59.451 - info: host.bro instance system.adapter.viessmann.0 started with pid 27226
2020-10-05 14:05:00.652 - debug: viessmann.0 (27226) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:05:00.705 - debug: viessmann.0 (27226) Objects client ready ... initialize now
2020-10-05 14:05:00.711 - debug: viessmann.0 (27226) Objects create System PubSub Client
2020-10-05 14:05:00.713 - debug: viessmann.0 (27226) Objects create User PubSub Client
2020-10-05 14:05:00.714 - debug: viessmann.0 (27226) Objects client initialize lua scripts
2020-10-05 14:05:00.744 - debug: viessmann.0 (27226) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:05:00.757 - debug: viessmann.0 (27226) objectDB connected
2020-10-05 14:05:00.759 - debug: viessmann.0 (27226) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:05:00.766 - debug: viessmann.0 (27226) States create User PubSub Client
2020-10-05 14:05:00.769 - debug: viessmann.0 (27226) States create System PubSub Client
2020-10-05 14:05:00.779 - debug: viessmann.0 (27226) States connected to redis: 127.0.0.1:9000
2020-10-05 14:05:00.780 - debug: viessmann.0 (27226) statesDB connected
2020-10-05 14:05:01.475 - info: viessmann.0 (27226) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:05:01.621 - info: viessmann.0 (27226) Connect with Viessmann sytem!
2020-10-05 14:05:01.623 - debug: viessmann.0 (27226) Wait for next run: 60000 in ms
2020-10-05 14:05:17.731 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 14:05:17.732 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 14:05:17.735 - info: viessmann.0 (27226) Got terminate signal TERMINATE_YOURSELF
2020-10-05 14:05:17.737 - info: viessmann.0 (27226) cleaned everything up...
2020-10-05 14:05:17.737 - info: viessmann.0 (27226) terminating
2020-10-05 14:05:17.738 - info: viessmann.0 (27226) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 14:05:18.261 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:05:20.770 - info: host.bro instance system.adapter.viessmann.0 started with pid 27785
2020-10-05 14:05:21.875 - debug: viessmann.0 (27785) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:05:21.911 - debug: viessmann.0 (27785) Objects client ready ... initialize now
2020-10-05 14:05:21.916 - debug: viessmann.0 (27785) Objects create System PubSub Client
2020-10-05 14:05:21.917 - debug: viessmann.0 (27785) Objects create User PubSub Client
2020-10-05 14:05:21.918 - debug: viessmann.0 (27785) Objects client initialize lua scripts
2020-10-05 14:05:21.932 - debug: viessmann.0 (27785) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:05:21.941 - debug: viessmann.0 (27785) objectDB connected
2020-10-05 14:05:21.943 - debug: viessmann.0 (27785) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:05:21.951 - debug: viessmann.0 (27785) States create User PubSub Client
2020-10-05 14:05:21.953 - debug: viessmann.0 (27785) States create System PubSub Client
2020-10-05 14:05:21.963 - debug: viessmann.0 (27785) States connected to redis: 127.0.0.1:9000
2020-10-05 14:05:21.964 - debug: viessmann.0 (27785) statesDB connected
2020-10-05 14:05:23.341 - info: viessmann.0 (27785) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:05:23.435 - info: viessmann.0 (27785) Connect with Viessmann sytem!
2020-10-05 14:05:23.437 - debug: viessmann.0 (27785) Commands for polling: getBetriebsartAnlage
2020-10-05 14:05:23.438 - debug: viessmann.0 (27785) Commands for polling: getBetriebsartHK
2020-10-05 14:05:23.438 - debug: viessmann.0 (27785) Commands for polling: getBetriebsartHKReduziert
2020-10-05 14:05:23.438 - debug: viessmann.0 (27785) Commands for polling: getBetriebsartHKNormal
2020-10-05 14:05:23.439 - debug: viessmann.0 (27785) Commands for polling: getPartybetrieb
2020-10-05 14:05:23.440 - debug: viessmann.0 (27785) Commands for polling: getPartybetriebTempSoll
2020-10-05 14:05:23.441 - debug: viessmann.0 (27785) Wait for next run: 60000 in ms
2020-10-05 14:06:23.442 - debug: viessmann.0 (27785) Next poll: heartbeat (For Object: heartbeat)
2020-10-05 14:06:23.536 - debug: viessmann.0 (27785) Received: ERR: command unknown
2020-10-05 14:06:23.588 - debug: viessmann.0 (27785) Next poll: getBetriebsartAnlage (For Object: BetriebsartAnlage)
2020-10-05 14:06:25.075 - debug: viessmann.0 (27785) Received: 1
2020-10-05 14:06:25.129 - debug: viessmann.0 (27785) Next poll: getBetriebsartHK (For Object: BetriebsartHK)
2020-10-05 14:06:25.188 - debug: viessmann.0 (27785) Received: Normal
2020-10-05 14:06:25.238 - debug: viessmann.0 (27785) Next poll: getBetriebsartHKReduziert (For Object: BetriebsartHKReduziert)
2020-10-05 14:06:25.298 - debug: viessmann.0 (27785) Received: 0
2020-10-05 14:06:25.348 - debug: viessmann.0 (27785) Next poll: getBetriebsartHKNormal (For Object: BetriebsartHKNormal)
2020-10-05 14:06:25.410 - debug: viessmann.0 (27785) Received: 1
2020-10-05 14:06:25.458 - debug: viessmann.0 (27785) Next poll: getPartybetrieb (For Object: Partybetrieb)
2020-10-05 14:06:25.514 - debug: viessmann.0 (27785) Received: 1
2020-10-05 14:06:25.598 - debug: viessmann.0 (27785) Next poll: getPartybetriebTempSoll (For Object: PartybetriebTempSoll)
2020-10-05 14:06:25.655 - debug: viessmann.0 (27785) Received: 22.000000 °C
2020-10-05 14:06:25.662 - debug: viessmann.0 (27785) Wait for next run: 57782 in ms
2020-10-05 14:06:57.109 - info: viessmann.0 (27785) state viessmann.0.set.BetriebsartAnlage changed: 2 (ack = false)
2020-10-05 14:07:23.445 - debug: viessmann.0 (27785) Set command: setBetriebsartAnlage 2
2020-10-05 14:09:23.600 - error: viessmann.0 (27785) Timeout connection error!
2020-10-05 14:09:23.608 - info: viessmann.0 (27785) Connection with Viessmann system disconnected!
2020-10-05 14:09:36.775 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 14:09:36.778 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 14:09:36.787 - info: viessmann.0 (27785) Got terminate signal TERMINATE_YOURSELF
2020-10-05 14:09:36.790 - info: viessmann.0 (27785) cleaned everything up...
2020-10-05 14:09:36.792 - info: viessmann.0 (27785) terminating
2020-10-05 14:09:36.795 - info: viessmann.0 (27785) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 14:09:37.320 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:09:39.796 - info: host.bro instance system.adapter.viessmann.0 started with pid 1074
2020-10-05 14:09:40.976 - debug: viessmann.0 (1074) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:09:41.013 - debug: viessmann.0 (1074) Objects client ready ... initialize now
2020-10-05 14:09:41.018 - debug: viessmann.0 (1074) Objects create System PubSub Client
2020-10-05 14:09:41.019 - debug: viessmann.0 (1074) Objects create User PubSub Client
2020-10-05 14:09:41.020 - debug: viessmann.0 (1074) Objects client initialize lua scripts
2020-10-05 14:09:41.034 - debug: viessmann.0 (1074) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:09:41.042 - debug: viessmann.0 (1074) objectDB connected
2020-10-05 14:09:41.045 - debug: viessmann.0 (1074) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:09:41.052 - debug: viessmann.0 (1074) States create User PubSub Client
2020-10-05 14:09:41.055 - debug: viessmann.0 (1074) States create System PubSub Client
2020-10-05 14:09:41.066 - debug: viessmann.0 (1074) States connected to redis: 127.0.0.1:9000
2020-10-05 14:09:41.066 - debug: viessmann.0 (1074) statesDB connected
2020-10-05 14:09:42.551 - info: viessmann.0 (1074) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:09:42.621 - info: viessmann.0 (1074) Connect with Viessmann sytem!
2020-10-05 14:09:42.622 - debug: viessmann.0 (1074) Commands for polling: getBetriebsartAnlage
2020-10-05 14:09:42.623 - debug: viessmann.0 (1074) Commands for polling: getBetriebsartHK
2020-10-05 14:09:42.624 - debug: viessmann.0 (1074) Commands for polling: getBetriebsartHKReduziert
2020-10-05 14:09:42.625 - debug: viessmann.0 (1074) Commands for polling: getBetriebsartHKNormal
2020-10-05 14:09:42.625 - debug: viessmann.0 (1074) Commands for polling: getPartybetrieb
2020-10-05 14:09:42.626 - debug: viessmann.0 (1074) Commands for polling: getPartybetriebTempSoll
2020-10-05 14:09:42.629 - debug: viessmann.0 (1074) Wait for next run: 60000 in ms
2020-10-05 14:10:42.630 - debug: viessmann.0 (1074) Next poll: heartbeat (For Object: heartbeat)
2020-10-05 14:10:42.720 - debug: viessmann.0 (1074) Received: ERR: command unknown
2020-10-05 14:10:42.768 - debug: viessmann.0 (1074) Next poll: getBetriebsartAnlage (For Object: BetriebsartAnlage)
2020-10-05 14:10:44.478 - debug: viessmann.0 (1074) Received: 2
2020-10-05 14:10:44.528 - debug: viessmann.0 (1074) Next poll: getBetriebsartHK (For Object: BetriebsartHK)
2020-10-05 14:10:44.588 - debug: viessmann.0 (1074) Received: Normal
2020-10-05 14:10:44.638 - debug: viessmann.0 (1074) Next poll: getBetriebsartHKReduziert (For Object: BetriebsartHKReduziert)
2020-10-05 14:10:44.701 - debug: viessmann.0 (1074) Received: 0
2020-10-05 14:10:44.748 - debug: viessmann.0 (1074) Next poll: getBetriebsartHKNormal (For Object: BetriebsartHKNormal)
2020-10-05 14:10:44.807 - debug: viessmann.0 (1074) Received: 1
2020-10-05 14:10:44.843 - debug: viessmann.0 (1074) Next poll: getPartybetrieb (For Object: Partybetrieb)
2020-10-05 14:10:44.897 - debug: viessmann.0 (1074) Received: 1
2020-10-05 14:10:44.979 - debug: viessmann.0 (1074) Next poll: getPartybetriebTempSoll (For Object: PartybetriebTempSoll)
2020-10-05 14:10:45.036 - debug: viessmann.0 (1074) Received: 22.000000 °C
2020-10-05 14:10:45.098 - debug: viessmann.0 (1074) Wait for next run: 57533 in ms
2020-10-05 14:11:31.365 - info: viessmann.0 (1074) state viessmann.0.set.Partybetrieb changed: 0 (ack = false)
2020-10-05 14:11:42.632 - debug: viessmann.0 (1074) Set command: setPartybetrieb 0
2020-10-05 14:12:00.113 - info: info.0 (576) Popup news was read...
2020-10-05 14:12:03.384 - debug: viessmann.0 (1074) system.adapter.admin.0: logging false
2020-10-05 14:12:23.158 - debug: viessmann.0 (1074) system.adapter.admin.0: logging true
2020-10-05 14:12:38.708 - info: tankerkoenig.0 (1141) Reading data from tankerkoenig ...
2020-10-05 14:13:42.775 - error: viessmann.0 (1074) Timeout connection error!
2020-10-05 14:13:42.783 - info: viessmann.0 (1074) Connection with Viessmann system disconnected!
2020-10-05 14:14:12.905 - info: host.bro stopInstance system.adapter.viessmann.0 (force=false, process=true)
2020-10-05 14:14:12.906 - info: host.bro stopInstance system.adapter.viessmann.0 send kill signal
2020-10-05 14:14:12.910 - info: viessmann.0 (1074) Got terminate signal TERMINATE_YOURSELF
2020-10-05 14:14:12.911 - info: viessmann.0 (1074) cleaned everything up...
2020-10-05 14:14:12.912 - info: viessmann.0 (1074) terminating
2020-10-05 14:14:12.913 - info: viessmann.0 (1074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-10-05 14:14:13.443 - info: host.bro instance system.adapter.viessmann.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-10-05 14:14:15.922 - info: host.bro instance system.adapter.viessmann.0 started with pid 7414
2020-10-05 14:14:17.027 - debug: viessmann.0 (7414) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-10-05 14:14:17.066 - debug: viessmann.0 (7414) Objects client ready ... initialize now
2020-10-05 14:14:17.070 - debug: viessmann.0 (7414) Objects create System PubSub Client
2020-10-05 14:14:17.071 - debug: viessmann.0 (7414) Objects create User PubSub Client
2020-10-05 14:14:17.072 - debug: viessmann.0 (7414) Objects client initialize lua scripts
2020-10-05 14:14:17.087 - debug: viessmann.0 (7414) Objects connected to redis: 127.0.0.1:9001
2020-10-05 14:14:17.095 - debug: viessmann.0 (7414) objectDB connected
2020-10-05 14:14:17.098 - debug: viessmann.0 (7414) Redis States: Use Redis connection: 127.0.0.1:9000
2020-10-05 14:14:17.105 - debug: viessmann.0 (7414) States create User PubSub Client
2020-10-05 14:14:17.107 - debug: viessmann.0 (7414) States create System PubSub Client
2020-10-05 14:14:17.118 - debug: viessmann.0 (7414) States connected to redis: 127.0.0.1:9000
2020-10-05 14:14:17.119 - debug: viessmann.0 (7414) statesDB connected
2020-10-05 14:14:18.720 - info: viessmann.0 (7414) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.viessmann, node: v10.21.0, js-controller: 3.1.6
2020-10-05 14:14:18.808 - info: viessmann.0 (7414) Connect with Viessmann sytem!
2020-10-05 14:14:18.810 - debug: viessmann.0 (7414) Commands for polling: getBetriebsartAnlage
2020-10-05 14:14:18.811 - debug: viessmann.0 (7414) Commands for polling: getBetriebsartHK
2020-10-05 14:14:18.812 - debug: viessmann.0 (7414) Commands for polling: getBetriebsartHKReduziert
2020-10-05 14:14:18.813 - debug: viessmann.0 (7414) Commands for polling: getBetriebsartHKNormal
2020-10-05 14:14:18.813 - debug: viessmann.0 (7414) Commands for polling: getPartybetrieb
2020-10-05 14:14:18.814 - debug: viessmann.0 (7414) Commands for polling: getPartybetriebTempSoll
2020-10-05 14:14:18.816 - debug: viessmann.0 (7414) Wait for next run: 60000 in ms