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/ioBroker/ioBroker.maxcul

• [E118] Versions in package.json and in io-package.json are different
• [E301] Tests on Travis-ci.org are broken. Please fix.

Thanks,
your automatic adapter checker.

Hi, is there any possibility to integrate fakewallthermostat as done in Fhem?

Ich arbeite hier mit einem Busware-Cul USB in der Version 1.6.1. .
Habe die Adapter-Version 1.1.1 installiert, die Thermostate werden nicht gefunden und einsortiert.
Da bei der Adapterinstallation etliche warnings kamen, hab ich die 1.0.0 installiert. Dort werden sie gefunden.
Werde die Tage von der Version 1.0.0 auf die aktuelle updaten um zu sehen, ob sie in der Objektliste erhalten bleiben!
Ich berichte!

This night i built my own nanocul and i have mounted a thermostat to my heater.
After fixing some bugs i managed to set up the cul and pair the thermostat.

Already in iobroker a new object was created and via writing to the desiitredTemperature the thermostat value is being adjusted, so the communication is working fine.

But i am not recieving any values from the thermostat

Ist der Adapter einmal installiert und der Serialport in Zeilenform angegeben kann er nicht geändert werden.
Mein Dropdownmenü bleibt leer und wenn an den anderen werten etwa Scanner was auch immer der bewirkt verstellt wird, kann der Adapter nicht mehr gestartet werden.
Er sagt immer wieder, er kann den cul nicht finden.

Hi,
Iobroker ist auf dem letzten Beta Stand.
Habe gerade das System auf Node 18.16.1 geupgradet.

Maxcul startet nicht mehr.

Hier das Debug Log:

`
2023-07-15 14:54:52.459 - debug: maxcul.0 (9404) Redis Objects: Use Redis connection: 127.0.0.1:9001

2023-07-15 14:54:52.578 - debug: maxcul.0 (9404) Objects client ready ... initialize now
2023-07-15 14:54:52.625 - debug: maxcul.0 (9404) Objects create System PubSub Client
2023-07-15 14:54:52.628 - debug: maxcul.0 (9404) Objects create User PubSub Client
2023-07-15 14:54:52.804 - debug: maxcul.0 (9404) Objects client initialize lua scripts
2023-07-15 14:54:52.823 - debug: maxcul.0 (9404) Objects connected to redis: 127.0.0.1:9001
2023-07-15 14:54:52.956 - debug: maxcul.0 (9404) Redis States: Use Redis connection: 127.0.0.1:9000
2023-07-15 14:54:53.049 - debug: maxcul.0 (9404) States create System PubSub Client
2023-07-15 14:54:53.051 - debug: maxcul.0 (9404) States create User PubSub Client
2023-07-15 14:54:53.223 - debug: maxcul.0 (9404) States connected to redis: 127.0.0.1:9000
2023-07-15 14:54:54.359 - info: maxcul.0 (9404) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.maxcul, node: v18.16.1, js-controller: 5.0.7
2023-07-15 14:54:55.055 - error: maxcul.0 (9404) uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
2023-07-15 14:54:55.056 - error: maxcul.0 (9404) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48)
at Object. (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
2023-07-15 14:54:55.057 - error: maxcul.0 (9404) Exception-Code: ERR_DLOPEN_FAILED: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
2023-07-15 14:54:55.066 - info: maxcul.0 (9404) terminating
2023-07-15 14:54:55.079 - warn: maxcul.0 (9404) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-07-15 14:54:55.581 - info: maxcul.0 (9404) terminating
2023-07-15 14:54:55.776 - error: host.iobroker Caught by controller[0]: Cannot load serialport module
2023-07-15 14:54:55.781 - error: host.iobroker instance system.adapter.maxcul.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
`
Grüße

Seit dem gestriegen update meiner seits auf Node.js v12.18.3 startet der Adapter nicht mehr.

host.iobroker | 2020-08-11 10:59:45.873 | info | Restart adapter system.adapter.maxcul.0 because enabled
-- | -- | -- | --
host.iobroker | 2020-08-11 10:59:45.872 | info | instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
host.iobroker | 2020-08-11 10:59:45.869 | error | Caught by controller[0]: Cannot load serialport module
maxcul.0 | 2020-08-11 10:59:45.246 | info | (1899) Terminated (NO_ERROR): Without reason
maxcul.0 | 2020-08-11 10:59:45.243 | info | (1899) terminating
maxcul.0 | 2020-08-11 10:59:45.183 | error | (1899) Error: Module did not self-register: '/opt/iobroker/node_modules/iobroker.maxcul/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal
maxcul.0 | 2020-08-11 10:59:45.182 | error | (1899) unhandled promise rejection: Module did not self-register: '/opt/iobroker/node_modules/iobroker.maxcul/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0 | 2020-08-11 10:59:45.180 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
maxcul.0 | 2020-08-11 10:59:44.714 | info | (1899) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.18.3, js-controller: 3.1.6
host.iobroker | 2020-08-11 10:59:41.085 | info | instance system.adapter.maxcul.0 started with pid 1899

To Reproduce
Einfach neustarten mit diesen Versionen

Versions:

• Adapter version: 1.3.1
• JS-Controller version: 3.1.6
• Node version: v12.18.3
• Operating system: Rasbian

Da so langsam einige Adapter den jc-controller 3x benötigen, habe ich auch mal ein Update gemacht.
Nun kommt folgender Fehler:
`

2020-04-24 00:48:00.085 - warn: maxcul.0 (23364) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!

2020-04-24 00:48:00.114 - warn: maxcul.0 (23364) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!

`
Scheint aber nur ein warnhinweis zu sein. Vielleicht könnte man das ja an den ls 3.xx anpassen

Hallo,
ich weiß nicht wieso das passiert, aber normal denke ich, ist das nicht. Ich setzte per Blockly das Thermostat auf manual window, wenn ich ein Fenster öffne. Dabei wird ja die Window open Temp gesetzt, soweit so gut. Nur nach ein paar Sekunden, steht wieder manual drin ? Das soll doch so bestimmt nicht sein. Ich sehe auch nichts im Log, wer ihn wieder auf manual setzt ? Sollte der manual Window Mode nicht so lange drin stehen, bis ich mein Fenster wieder schließe und den Thermostat auf manual oder auto zurück setzte ?
Grüße

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/ioBroker/ioBroker.maxcul

• [E118] Versions in package.json and in io-package.json are different
• [E301] Tests on Travis-ci.org are broken. Please fix.

Thanks,
your automatic adapter checker.

Hallo,
nachdem der WallThermostat jetzt im Broker eingelesen wurde nd auch eine Zeit lang funktioniert hat, zeigt er jetzt die falsche measuredTemperatur an.

Im Log scheint aber die richtige anzukommen:

Auch wenn ich ihn neu einlese, bekommt er den falschen Wert!

Hi,

ich hatte immer den Fehler : maxcul.0 (31492) unhandled promise rejection: undefined
und wollte dann wieder auf die 1.2.0
die lies sich nicht installieren und bin wieder auf die 1.3.0
Leider zeigt er wir keine Serial Port mehr an

JS Controller 3.1.4
Node.js: v10.20.1
NPM: v6.14.4

`

2020-05-18 20:32:35.037 - warn: maxcul.0 (4940) Please define the serial port.

2020-05-18 20:32:35.374 - info: host.raspberrypi iobroker exit 0
2020-05-18 20:32:37.352 - info: host.raspberrypi instance system.adapter.maxcul.1 started with pid 5098
2020-05-18 20:32:39.101 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2020-05-18 20:32:39.102 - error: maxcul.0 (4940) unhandled promise rejection: SerialPort.list no longer takes a callback and only returns a promise
2020-05-18 20:32:39.133 - error: maxcul.0 (4940) TypeError: SerialPort.list no longer takes a callback and only returns a promise
at Function.SerialPort.list (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:651:11)
at Adapter.adapter.on.obj (/opt/iobroker/node_modules/iobroker.maxcul/main.js:147:40)
at Adapter.emit (events.js:198:13)
at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5313:34)
at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:234:41)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
2020-05-18 20:32:39.185 - info: maxcul.0 (4940) terminating
2020-05-18 20:32:39.188 - info: maxcul.0 (4940) Terminated (NO_ERROR): Without reason
2020-05-18 20:32:39.720 - info: host.raspberrypi instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
2020-05-18 20:32:39.721 - info: host.raspberrypi Restart adapter system.adapter.maxcul.0 because enabled
2020-05-18 20:32:40.659 - info: maxcul.1 (5098) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v10.20.1, js-controller: 3.1.4
2020-05-18 20:32:40.816 - warn: maxcul.1 (5098) Please define the serial port.

`

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.

Hi,

mein Wandthermostat zeigt keine Daten, wie z.B. die aktuell gemessene Temperatur:

Wenn ich per ioBroker die Temperatur einstelle, übernimmt das Wandthermostat diese Einstellung, wenn ich aber per Wandthermostat die Temperatur rauf oder runter regle, verändert sich im ioBroker nichts.

Die normalen Heizkörperthermostate funktionieren aber auf anhieb. Nur das Wandthermostat will einfach nicht funktionieren

Ich hoffe ihr könnt mir helfen

Greetings NCMasta

Nachdem der Adapter ursprünglich vom Pimatic Adapter stammen soll, rege ich hiermit an, die aktuelle Pimatic Version des CUL Adapters neu zu portieren, um die dort entstandenen Features nutzen zu können. https://github.com/fbeek/pimatic-maxcul

Think about update stable version to 1.1.2

Version: stable=1.1.1 (242 days old) => latest=1.1.2 (183 days old)
Installs: stable=211 (53.15%), latest=105 (26.45%), total=397
Click to edit

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

It shows as "sec" in iobroker while it actually seems to be minutes.

Can be easily fixed if one changes this line accordingly.

I would also suggest to set a default value to all "config" and "valveConfig" sub-values because they seem to be empty by default and will not get pushed by the devices back to ioBroker.

My suggestions (values not in <> resembles the manufactures default values):
valveConfig
boostDuration: 5min
boostValvePosition: 100%
decalcificationDay: <unsure - I have set it to Monday>
decalcificationHour: <unsure - I have set it to 14h>
maxValveSetting: 100%
valveOffset: 0%

config
comfortTemperature: 21
ecoTemperature: 17
maximumTemperature: <unsure - I have set it to 30>
minimumTemperature: <unsure - I have set it to 15>
offset: 0
windowsOpenTemperature: <unsure - I have set it to 15>

Hi, der Datenpunkt offset(maxcul.0.OEQ2044068.config.offset) eines Thermostats hat standardmäßig die Wertgrenzen +4,5 bis +30,5. Das heißt, das keine offset Werte kleiner 4,5 angenommen werden, die praktisch jedoch sehr plausibel wären.
Anpassen auf +30 und - 30 schafft Abhilfe.
Danke!

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

DerAdapter stürzt quasi abund startet sich einmal in der Stunde neu.
Node.js: v12.16.3
NPM: 6.14.4
JS-Controller: 3.0.20
Hier das Log:
`

2020-05-03 12:03:58.793 - debug: maxcul.0 (9916) serial port buffer have been drained

2020-05-03 12:03:58.795 - debug: maxcul.0 (9916) delayed next send by 0ms (Queue length left = 0, Current Credit = 679)
2020-05-03 12:03:59.788 - debug: maxcul.0 (9916) Retransmit packet 0f0104031234561234560014030c4375, try 2 of 3
2020-05-03 12:03:59.789 - debug: maxcul.0 (9916) Send Packet to CUL: Zs0f0104031234561234560014030c4375, awaiting drain event
2020-05-03 12:03:59.790 - debug: maxcul.0 (9916) serial port buffer have been drained
2020-05-03 12:04:01.791 - debug: maxcul.0 (9916) delayed next send by 2000ms (Queue length left = 1, Current Credit = 679)
2020-05-03 12:04:01.792 - debug: maxcul.0 (9916) Send Packet to CUL: X, awaiting drain event
2020-05-03 12:04:01.793 - debug: maxcul.0 (9916) serial port buffer have been drained
2020-05-03 12:04:01.794 - debug: maxcul.0 (9916) delayed next send by 0ms (Queue length left = 0, Current Credit = 569)
2020-05-03 12:04:02.789 - debug: maxcul.0 (9916) Retransmit packet 0f0104031234561234560014030c4375, try 3 of 3
2020-05-03 12:04:02.790 - debug: maxcul.0 (9916) Send Packet to CUL: Zs0f0104031234561234560014030c4375, awaiting drain event
2020-05-03 12:04:02.791 - debug: maxcul.0 (9916) serial port buffer have been drained
2020-05-03 12:04:04.791 - debug: maxcul.0 (9916) delayed next send by 2000ms (Queue length left = 1, Current Credit = 569)
2020-05-03 12:04:04.792 - debug: maxcul.0 (9916) Send Packet to CUL: X, awaiting drain event
2020-05-03 12:04:04.794 - debug: maxcul.0 (9916) serial port buffer have been drained
2020-05-03 12:04:04.794 - debug: maxcul.0 (9916) delayed next send by 0ms (Queue length left = 0, Current Credit = 459)
2020-05-03 12:04:05.791 - error: maxcul.0 (9916) uncaught exception: undefined
2020-05-03 12:04:05.793 - debug: maxcul.0 (9916) Send Packet to CUL: X, awaiting drain event
2020-05-03 12:04:05.797 - info: maxcul.0 (9916) terminating
2020-05-03 12:04:05.798 - info: maxcul.0 (9916) Terminated (NO_ERROR): Without reason
2020-05-03 12:04:06.317 - info: host.iobroker instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
2020-05-03 12:04:06.319 - info: host.iobroker Restart adapter system.adapter.maxcul.0 because enabled
2020-05-03 12:04:36.339 - info: host.iobroker instance system.adapter.maxcul.0 started with pid 22058
2020-05-03 12:04:36.678 - debug: maxcul.0 (22058) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-05-03 12:04:36.699 - debug: maxcul.0 (22058) Objects client ready ... initialize now
2020-05-03 12:04:36.701 - debug: maxcul.0 (22058) Objects create System PubSub Client
2020-05-03 12:04:36.702 - debug: maxcul.0 (22058) Objects create User PubSub Client
2020-05-03 12:04:36.702 - debug: maxcul.0 (22058) Objects client initialize lua scripts
2020-05-03 12:04:36.716 - debug: maxcul.0 (22058) Objects connected to redis: 127.0.0.1:9001
2020-05-03 12:04:36.719 - debug: maxcul.0 (22058) objectDB connected
2020-05-03 12:04:36.720 - debug: maxcul.0 (22058) Redis States: Use Redis connection: 127.0.0.1:9000
2020-05-03 12:04:36.727 - debug: maxcul.0 (22058) States create User PubSub Client
2020-05-03 12:04:36.728 - debug: maxcul.0 (22058) States create System PubSub Client
2020-05-03 12:04:36.739 - debug: maxcul.0 (22058) States connected to redis: 127.0.0.1:9000
2020-05-03 12:04:36.740 - debug: maxcul.0 (22058) statesDB connected
2020-05-03 12:04:37.084 - info: maxcul.0 (22058) starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.0.20
2020-05-03 12:04:37.101 - warn: maxcul.0 (22058) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
2020-05-03 12:04:37.117 - warn: maxcul.0 (22058) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
2020-05-03 12:04:37.244 - info: maxcul.0 (22058) using serial device /dev/ttyACM0@9600
2020-05-03 12:04:37.253 - info: maxcul.0 (22058) serialPort /dev/ttyACM0 is open!
2020-05-03 12:04:39.255 - debug: maxcul.0 (22058) check CUL Firmware version
2020-05-03 12:04:39.256 - debug: maxcul.0 (22058) Requested CUL Version...
2020-05-03 12:04:39.259 - debug: maxcul.0 (22058) incoming raw data from CUL: V 1.61 CUL868
2020-05-03 12:04:39.260 - info: maxcul.0 (22058) CUL FW Version: V 1.61 CUL868
2020-05-03 12:04:42.247 - debug: maxcul.0 (22058) Send Packet to CUL: X, awaiting drain event
2020-05-03 12:04:42.250 - debug: maxcul.0 (22058) serial port buffer have been drained
2020-05-03 12:04:42.251 - debug: maxcul.0 (22058) delayed next send by 0ms (Queue length left = 0, Current Credit = 497)
2020-05-03 12:04:43.257 - debug: maxcul.0 (22058) enable MAX! Mode of the CUL868
2020-05-03 12:04:43.258 - debug: maxcul.0 (22058) X20 written
2020-05-03 12:04:43.259 - debug: maxcul.0 (22058) X20 drained
2020-05-03 12:04:43.260 - debug: maxcul.0 (22058) Zr written
2020-05-03 12:04:43.260 - debug: maxcul.0 (22058) Zr drained
2020-05-03 12:04:43.261 - debug: maxcul.0 (22058) Za written
2020-05-03 12:04:43.262 - debug: maxcul.0 (22058) Za drained
2020-05-03 12:04:47.247 - debug: maxcul.0 (22058) Send Packet to CUL: X, awaiting drain event
2020-05-03 12:04:47.249 - debug: maxcul.0 (22058) serial port buffer have been drained
2020-05-03 12:04:47.250 - debug: maxcul.0 (22058) delayed next send by 0ms (Queue length left = 0, Current Credit = 502)

`

Hallo Zusammen,

aus gegeben Anlass #30 würde ich gerne darüber diskutieren, wie sinnvoll es wäre den pairing modus nicht auf dauerhaft aktiv zu schalten, sondern dem Benutzer die Wahl zu lassen wann er aktiviert sein soll?

Was haltet Ihr davon?

Ist es möglich die Wochenplanung aus den Thermostaten zu lesen und zu setzen? ich habe leider keine Möglichkeit gefunden. Muss ich sonst die Thermostate im manuellen Modus betreiben und dann selbst die Temperaturen umstellen?

Think about update stable version to 1.3.1

Version: stable=1.3.0 (86 days old) => latest=1.3.1 (15 days old)
Installs: stable=155 (40.9%), latest=55 (14.51%), total=379
Click to edit

I used a cul flashed Max!Cube and got warn messages every few minutes. I got also no values in the detail view only " ". After I clicked in the cell of the value the display change to 0°, 0%, false etc.
The warn message looks like:
unknown device: {"src":"XXXXXX","mode":"0","desiredTemperature":21,"valvePosition":27,"measuredTemperature":20.8,"dstSetting":1,"lanGateway":1,"panel":0,"rfError":0,"batteryLow":0,"untilString":"","r
I can found the device XXXXXX under the max.cul object as a thermostat.
BTW: The devices are not paired.

After the Update the Adapter not start anymore...

I don't know if it a problem of my installation or is it a general problem?

Logs:
`

The Adapter allows to select the USB device via a drop down box. Unfortunately only real devices are listed, not symlinked devices. This is fine as only one serial USB device is plugged in. In my case I have two devices:

/dev/ttyUSB0
/dev/ttyUSB1

Which serial adapter gets assigned to which device is random at boot, so eventually I have to select a different device after boot. This is not optimal.

Suggested alternatives:

1. Don't use a drop-down but put a textfield there like the iobroker.zigbee adapter does
2. Include symlinked devices in the dropdown (e. g. everything that's named /dev/tty*, both real and symlinked). Best case this also includes all devices in /dev/serial/by-id/, to prevent tedious fiddling with udev rules.

Hi,

I'm the author of the bitset.js library you use. I just got the shorter npm name "bitset" instead of "bitset.js". The latter is now deprecated. Could you please update your dependencies?

Thanks and sorry for any inconveniences
Robert

Hello after installing the new adapter and including some of my MAX WTH or THs, the adapter did recognize them, but did not show any values.

here the log:

`
maxcul.0 2018-01-29 08:46:16.104 info received unknown data: 900
maxcul.0 2018-01-29 08:46:16.086 info received unknown data: 20
maxcul.0 2018-01-29 08:46:11.092 info received unknown data: 20 900
maxcul.0 2018-01-29 08:46:06.081 info received unknown data: 20 900
maxcul.0 2018-01-29 08:46:03.428 info received unknown data: 1190B2A17
maxcul.0 2018-01-29 08:46:03.379 info received unknown data: 21B90B71A7002AD3F7
maxcul.0 2018-01-29 08:46:01.087 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:56.094 info received unknown data:
maxcul.0 2018-01-29 08:45:51.083 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:46.071 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:41.077 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:36.083 info received unknown data: 900
maxcul.0 2018-01-29 08:45:36.066 info received unknown data: 20
maxcul.0 2018-01-29 08:45:31.075 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:26.062 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:21.068 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:16.056 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:11.061 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:06.051 info received unknown data: 20 900
maxcul.0 2018-01-29 08:45:01.040 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:59.730 info received unknown data: 1203AE19C1C9000119002808
maxcul.0 2018-01-29 08:44:56.046 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:51.035 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:46.042 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:41.031 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:36.035 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:31.025 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:26.032 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:21.021 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:16.009 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:11.014 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:06.004 info received unknown data: 20 900
maxcul.0 2018-01-29 08:44:01.500 info received unknown data: 308
maxcul.0 2018-01-29 08:44:01.010 info received unknown data: 00
maxcul.0 2018-01-29 08:43:55.999 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:50.988 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:45.994 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:40.999 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:35.989 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:30.998 info received unknown data:
maxcul.0 2018-01-29 08:43:25.984 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:20.989 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:18.434 info received unknown data: 01
maxcul.0 2018-01-29 08:43:18.385 info received unknown data: 02AD3F1
maxcul.0 2018-01-29 08:43:15.978 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:10.984 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:05.973 info received unknown data: 20 900
maxcul.0 2018-01-29 08:43:00.962 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:55.968 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:52.808 info received unknown data: 1
maxcul.0 2018-01-29 08:42:52.759 info received unknown data: 03DB0028C911
maxcul.0 2018-01-29 08:42:50.957 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:45.963 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:40.952 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:35.966 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:30.949 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:26.289 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:42:26.276 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:42:26.264 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:42:26.249 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:42:26.233 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:42:26.214 info object maxcul.0.maxcul.0.MEQ0679193.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:42:26.201 info object maxcul.0.maxcul.0.MEQ0679193.rssi created
maxcul.0 2018-01-29 08:42:26.188 info object maxcul.0.maxcul.0.MEQ0679193.config.windowOpenTime created
maxcul.0 2018-01-29 08:42:26.177 info object maxcul.0.maxcul.0.MEQ0679193.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:42:26.163 info object maxcul.0.maxcul.0.MEQ0679193.config.offset created
maxcul.0 2018-01-29 08:42:26.151 info object maxcul.0.maxcul.0.MEQ0679193.config.maximumTemperature created
maxcul.0 2018-01-29 08:42:26.137 info object maxcul.0.maxcul.0.MEQ0679193.config.minimumTemperature created
maxcul.0 2018-01-29 08:42:26.123 info object maxcul.0.maxcul.0.MEQ0679193.config.ecoTemperature created
maxcul.0 2018-01-29 08:42:26.110 info object maxcul.0.maxcul.0.MEQ0679193.config.comfortTemperature created
maxcul.0 2018-01-29 08:42:26.098 info object maxcul.0.maxcul.0.MEQ0679193.batteryLow created
maxcul.0 2018-01-29 08:42:26.084 info object maxcul.0.maxcul.0.MEQ0679193.rfError created
maxcul.0 2018-01-29 08:42:26.055 info object maxcul.0.maxcul.0.MEQ0679193.valvePosition created
maxcul.0 2018-01-29 08:42:26.042 info object maxcul.0.maxcul.0.MEQ0679193.desiredTemperature created
maxcul.0 2018-01-29 08:42:26.032 info object maxcul.0.maxcul.0.MEQ0679193.measuredTemperature created
maxcul.0 2018-01-29 08:42:26.019 info object maxcul.0.maxcul.0.MEQ0679193.mode created
maxcul.0 2018-01-29 08:42:26.007 info object maxcul.0.maxcul.0.MEQ0679193 created
maxcul.0 2018-01-29 08:42:25.988 info PairDevice: {"src":"1203db","type":1,"raw":"1001A14D455130363739313933","rssi":-65.5}
maxcul.0 2018-01-29 08:42:25.953 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:20.991 info received unknown data: 1001A14D45513036373931393311
maxcul.0 2018-01-29 08:42:20.942 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:15.997 info received unknown data: 3311
maxcul.0 2018-01-29 08:42:15.948 info received unknown data: 900
maxcul.0 2018-01-29 08:42:15.931 info received unknown data: 20
maxcul.0 2018-01-29 08:42:12.740 info received unknown data:
maxcul.0 2018-01-29 08:42:12.689 info received unknown data: 80028CE22
maxcul.0 2018-01-29 08:42:10.987 info received unknown data: 04001203DB0E94A7001001A14D4551303637393139330D
maxcul.0 2018-01-29 08:42:10.937 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:05.992 info received unknown data: 01A14D4551303637393139330C
maxcul.0 2018-01-29 08:42:05.944 info received unknown data: 20 900
maxcul.0 2018-01-29 08:42:00.998 info received unknown data: 393317
maxcul.0 2018-01-29 08:42:00.935 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:55.940 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:50.927 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:45.916 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:40.923 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:35.911 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:30.917 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:25.906 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:20.913 info received unknown data: 900
maxcul.0 2018-01-29 08:41:20.895 info received unknown data: 20
maxcul.0 2018-01-29 08:41:15.903 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:12.544 info received unknown data: 145A2B192204000119002AFF
maxcul.0 2018-01-29 08:41:10.907 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:05.896 info received unknown data: 20 900
maxcul.0 2018-01-29 08:41:01.494 info received unknown data: 01A14D45513036373931393311
maxcul.0 2018-01-29 08:41:00.885 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:56.497 info received unknown data: 0F
maxcul.0 2018-01-29 08:40:55.891 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:51.486 info received unknown data: 4001203DB0E94A7001001A14D4551303637393139330D
maxcul.0 2018-01-29 08:40:50.880 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:46.492 info received unknown data: D4551303637393139330B
maxcul.0 2018-01-29 08:40:45.886 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:41.497 info received unknown data: C
maxcul.0 2018-01-29 08:40:40.875 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:36.486 info received unknown data: 1203DB0E94A7001001A14D45513036373931393313
maxcul.0 2018-01-29 08:40:35.883 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:30.873 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:25.876 info received unknown data: 0 900
maxcul.0 2018-01-29 08:40:25.860 info received unknown data: 2
maxcul.0 2018-01-29 08:40:20.866 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:15.854 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:10.860 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:05.849 info received unknown data: 20 900
maxcul.0 2018-01-29 08:40:00.855 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:55.844 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:50.852 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:45.843 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:40.846 info received unknown data: 900
maxcul.0 2018-01-29 08:39:40.828 info received unknown data: 20
maxcul.0 2018-01-29 08:39:35.834 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:30.823 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:27.387 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:39:27.372 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:39:27.342 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:39:27.331 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:39:27.318 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:39:27.307 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:39:27.298 info object maxcul.0.maxcul.0.OEQ1455934.rssi created
maxcul.0 2018-01-29 08:39:27.278 info object maxcul.0.maxcul.0.OEQ1455934.config.windowOpenTime created
maxcul.0 2018-01-29 08:39:27.265 info object maxcul.0.maxcul.0.OEQ1455934.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:39:27.234 info object maxcul.0.maxcul.0.OEQ1455934.config.offset created
maxcul.0 2018-01-29 08:39:27.223 info object maxcul.0.maxcul.0.OEQ1455934.config.maximumTemperature created
maxcul.0 2018-01-29 08:39:27.212 info object maxcul.0.maxcul.0.OEQ1455934.config.minimumTemperature created
maxcul.0 2018-01-29 08:39:27.171 info object maxcul.0.maxcul.0.OEQ1455934.config.ecoTemperature created
maxcul.0 2018-01-29 08:39:27.135 info object maxcul.0.maxcul.0.OEQ1455934.config.comfortTemperature created
maxcul.0 2018-01-29 08:39:27.122 info object maxcul.0.maxcul.0.OEQ1455934.batteryLow created
maxcul.0 2018-01-29 08:39:27.109 info object maxcul.0.maxcul.0.OEQ1455934.rfError created
maxcul.0 2018-01-29 08:39:27.093 info object maxcul.0.maxcul.0.OEQ1455934.valvePosition created
maxcul.0 2018-01-29 08:39:27.078 info object maxcul.0.maxcul.0.OEQ1455934.desiredTemperature created
maxcul.0 2018-01-29 08:39:27.055 info object maxcul.0.maxcul.0.OEQ1455934.measuredTemperature created
maxcul.0 2018-01-29 08:39:27.045 info object maxcul.0.maxcul.0.OEQ1455934.mode created
maxcul.0 2018-01-29 08:39:27.032 info object maxcul.0.maxcul.0.OEQ1455934 created
maxcul.0 2018-01-29 08:39:26.768 info PairDevice: {"src":"19c977","type":3,"raw":"1003FF4F455131343535393334","rssi":-65.5}
maxcul.0 2018-01-29 08:39:25.829 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:21.768 info received unknown data: E94A7001003FF4F45513134353539333410
maxcul.0 2018-01-29 08:39:20.818 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:16.773 info received unknown data: 353539333411
maxcul.0 2018-01-29 08:39:15.825 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:12.034 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:39:12.021 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:39:12.009 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:39:11.998 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:39:11.985 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:39:11.970 info object maxcul.0.maxcul.0.OEQ1455934.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:39:11.958 info object maxcul.0.maxcul.0.OEQ1455934.rssi created
maxcul.0 2018-01-29 08:39:11.947 info object maxcul.0.maxcul.0.OEQ1455934.config.windowOpenTime created
maxcul.0 2018-01-29 08:39:11.934 info object maxcul.0.maxcul.0.OEQ1455934.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:39:11.921 info object maxcul.0.maxcul.0.OEQ1455934.config.offset created
maxcul.0 2018-01-29 08:39:11.906 info object maxcul.0.maxcul.0.OEQ1455934.config.maximumTemperature created
maxcul.0 2018-01-29 08:39:11.895 info object maxcul.0.maxcul.0.OEQ1455934.config.minimumTemperature created
maxcul.0 2018-01-29 08:39:11.882 info object maxcul.0.maxcul.0.OEQ1455934.config.ecoTemperature created
maxcul.0 2018-01-29 08:39:11.871 info object maxcul.0.maxcul.0.OEQ1455934.config.comfortTemperature created
maxcul.0 2018-01-29 08:39:11.858 info object maxcul.0.maxcul.0.OEQ1455934.batteryLow created
maxcul.0 2018-01-29 08:39:11.845 info object maxcul.0.maxcul.0.OEQ1455934.rfError created
maxcul.0 2018-01-29 08:39:11.833 info object maxcul.0.maxcul.0.OEQ1455934.valvePosition created
maxcul.0 2018-01-29 08:39:11.822 info object maxcul.0.maxcul.0.OEQ1455934.desiredTemperature created
maxcul.0 2018-01-29 08:39:11.809 info object maxcul.0.maxcul.0.OEQ1455934.measuredTemperature created
maxcul.0 2018-01-29 08:39:11.796 info object maxcul.0.maxcul.0.OEQ1455934.mode created
maxcul.0 2018-01-29 08:39:11.783 info object maxcul.0.maxcul.0.OEQ1455934 created
maxcul.0 2018-01-29 08:39:11.768 info PairDevice: {"src":"19c977","type":3,"raw":"1003FF4F455131343535393334","rssi":-64.5}
maxcul.0 2018-01-29 08:39:10.815 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:06.768 info received unknown data: A7001003FF4F45513134353539333411
maxcul.0 2018-01-29 08:39:05.819 info received unknown data: 20 900
maxcul.0 2018-01-29 08:39:01.774 info received unknown data: 39333413
maxcul.0 2018-01-29 08:39:00.808 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:56.977 info received unknown data: 770E94A7001003FF4F4551313435353933341C
maxcul.0 2018-01-29 08:38:55.814 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:50.803 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:45.808 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:40.798 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:35.804 info received unknown data: 900
maxcul.0 2018-01-29 08:38:35.787 info received unknown data: 20
maxcul.0 2018-01-29 08:38:30.793 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:25.798 info received unknown data:
maxcul.0 2018-01-29 08:38:20.788 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:15.795 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:10.785 info received unknown data: 20 900
maxcul.0 2018-01-29 08:38:05.789 info received unknown data: 00
maxcul.0 2018-01-29 08:38:00.780 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:55.768 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:50.773 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:45.762 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:40.751 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:37.394 info received unknown data: 3F4
maxcul.0 2018-01-29 08:37:35.740 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:30.746 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:25.754 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:22.705 info received unknown data: 353336343329
maxcul.0 2018-01-29 08:37:20.742 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:17.958 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:37:17.948 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:37:17.938 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:37:17.925 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:37:17.915 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:37:17.900 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:37:17.886 info object maxcul.0.maxcul.0.OEQ1453643.rssi created
maxcul.0 2018-01-29 08:37:17.877 info object maxcul.0.maxcul.0.OEQ1453643.config.windowOpenTime created
maxcul.0 2018-01-29 08:37:17.865 info object maxcul.0.maxcul.0.OEQ1453643.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:37:17.853 info object maxcul.0.maxcul.0.OEQ1453643.config.offset created
maxcul.0 2018-01-29 08:37:17.841 info object maxcul.0.maxcul.0.OEQ1453643.config.maximumTemperature created
maxcul.0 2018-01-29 08:37:17.829 info object maxcul.0.maxcul.0.OEQ1453643.config.minimumTemperature created
maxcul.0 2018-01-29 08:37:17.817 info object maxcul.0.maxcul.0.OEQ1453643.config.ecoTemperature created
maxcul.0 2018-01-29 08:37:17.804 info object maxcul.0.maxcul.0.OEQ1453643.config.comfortTemperature created
maxcul.0 2018-01-29 08:37:17.793 info object maxcul.0.maxcul.0.OEQ1453643.batteryLow created
maxcul.0 2018-01-29 08:37:17.778 info object maxcul.0.maxcul.0.OEQ1453643.rfError created
maxcul.0 2018-01-29 08:37:17.765 info object maxcul.0.maxcul.0.OEQ1453643.valvePosition created
maxcul.0 2018-01-29 08:37:17.751 info object maxcul.0.maxcul.0.OEQ1453643.desiredTemperature created
maxcul.0 2018-01-29 08:37:17.735 info object maxcul.0.maxcul.0.OEQ1453643.measuredTemperature created
maxcul.0 2018-01-29 08:37:17.723 info object maxcul.0.maxcul.0.OEQ1453643.mode created
maxcul.0 2018-01-29 08:37:17.710 info object maxcul.0.maxcul.0.OEQ1453643 created
maxcul.0 2018-01-29 08:37:17.697 info PairDevice: {"src":"19c1c9","type":3,"raw":"1003FF4F455131343533363433","rssi":-53.5}
maxcul.0 2018-01-29 08:37:15.730 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:12.700 info received unknown data: E94A7001003FF4F45513134353336343329
maxcul.0 2018-01-29 08:37:10.735 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:07.706 info received unknown data: 353336343329
maxcul.0 2018-01-29 08:37:05.811 info received unknown data: 000119002811
maxcul.0 2018-01-29 08:37:05.758 info received unknown data: 4219C9771203DB0028CB13
maxcul.0 2018-01-29 08:37:05.725 info received unknown data: 20 900
maxcul.0 2018-01-29 08:37:02.982 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:37:02.969 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:37:02.957 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:37:02.943 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:37:02.926 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:37:02.912 info object maxcul.0.maxcul.0.OEQ1453643.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:37:02.899 info object maxcul.0.maxcul.0.OEQ1453643.rssi created
maxcul.0 2018-01-29 08:37:02.887 info object maxcul.0.maxcul.0.OEQ1453643.config.windowOpenTime created
maxcul.0 2018-01-29 08:37:02.877 info object maxcul.0.maxcul.0.OEQ1453643.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:37:02.866 info object maxcul.0.maxcul.0.OEQ1453643.config.offset created
maxcul.0 2018-01-29 08:37:02.853 info object maxcul.0.maxcul.0.OEQ1453643.config.maximumTemperature created
maxcul.0 2018-01-29 08:37:02.841 info object maxcul.0.maxcul.0.OEQ1453643.config.minimumTemperature created
maxcul.0 2018-01-29 08:37:02.830 info object maxcul.0.maxcul.0.OEQ1453643.config.ecoTemperature created
maxcul.0 2018-01-29 08:37:02.816 info object maxcul.0.maxcul.0.OEQ1453643.config.comfortTemperature created
maxcul.0 2018-01-29 08:37:02.800 info object maxcul.0.maxcul.0.OEQ1453643.batteryLow created
maxcul.0 2018-01-29 08:37:02.785 info object maxcul.0.maxcul.0.OEQ1453643.rfError created
maxcul.0 2018-01-29 08:37:02.774 info object maxcul.0.maxcul.0.OEQ1453643.valvePosition created
maxcul.0 2018-01-29 08:37:02.749 info object maxcul.0.maxcul.0.OEQ1453643.desiredTemperature created
maxcul.0 2018-01-29 08:37:02.738 info object maxcul.0.maxcul.0.OEQ1453643.measuredTemperature created
maxcul.0 2018-01-29 08:37:02.727 info object maxcul.0.maxcul.0.OEQ1453643.mode created
maxcul.0 2018-01-29 08:37:02.713 info object maxcul.0.maxcul.0.OEQ1453643 created
maxcul.0 2018-01-29 08:37:02.698 info PairDevice: {"src":"19c1c9","type":3,"raw":"1003FF4F455131343533363433","rssi":-54}
maxcul.0 2018-01-29 08:37:00.731 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:57.701 info received unknown data: A7001003FF4F45513134353336343327
maxcul.0 2018-01-29 08:36:55.721 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:52.903 info received unknown data: 5
maxcul.0 2018-01-29 08:36:50.726 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:45.715 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:40.721 info received unknown data: 900
maxcul.0 2018-01-29 08:36:40.704 info received unknown data: 20
maxcul.0 2018-01-29 08:36:35.712 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:30.720 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:27.737 info received unknown data: 02021203D819C1C900011900281C
maxcul.0 2018-01-29 08:36:25.705 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:20.696 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:15.700 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:10.689 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:05.695 info received unknown data: 20 900
maxcul.0 2018-01-29 08:36:00.684 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:55.690 info received unknown data: 900
maxcul.0 2018-01-29 08:35:55.673 info received unknown data: 20
maxcul.0 2018-01-29 08:35:50.679 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:45.685 info received unknown data:
maxcul.0 2018-01-29 08:35:40.674 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:35.668 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:30.669 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:27.525 info received unknown data: 4551303637393230381C
maxcul.0 2018-01-29 08:35:25.658 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:23.545 info received unknown data: D0202145A2B192204000119002AFE
maxcul.0 2018-01-29 08:35:22.855 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:35:22.843 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:35:22.830 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:35:22.809 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:35:22.788 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:35:22.779 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:35:22.764 info object maxcul.0.maxcul.0.MEQ0679208.rssi created
maxcul.0 2018-01-29 08:35:22.752 info object maxcul.0.maxcul.0.MEQ0679208.config.windowOpenTime created
maxcul.0 2018-01-29 08:35:22.741 info object maxcul.0.maxcul.0.MEQ0679208.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:35:22.731 info object maxcul.0.maxcul.0.MEQ0679208.config.offset created
maxcul.0 2018-01-29 08:35:22.718 info object maxcul.0.maxcul.0.MEQ0679208.config.maximumTemperature created
maxcul.0 2018-01-29 08:35:22.706 info object maxcul.0.maxcul.0.MEQ0679208.config.minimumTemperature created
maxcul.0 2018-01-29 08:35:22.695 info object maxcul.0.maxcul.0.MEQ0679208.config.ecoTemperature created
maxcul.0 2018-01-29 08:35:22.682 info object maxcul.0.maxcul.0.MEQ0679208.config.comfortTemperature created
maxcul.0 2018-01-29 08:35:22.672 info object maxcul.0.maxcul.0.MEQ0679208.batteryLow created
maxcul.0 2018-01-29 08:35:22.660 info object maxcul.0.maxcul.0.MEQ0679208.rfError created
maxcul.0 2018-01-29 08:35:22.645 info object maxcul.0.maxcul.0.MEQ0679208.valvePosition created
maxcul.0 2018-01-29 08:35:22.632 info object maxcul.0.maxcul.0.MEQ0679208.desiredTemperature created
maxcul.0 2018-01-29 08:35:22.617 info object maxcul.0.maxcul.0.MEQ0679208.measuredTemperature created
maxcul.0 2018-01-29 08:35:22.604 info object maxcul.0.maxcul.0.MEQ0679208.mode created
maxcul.0 2018-01-29 08:35:22.589 info object maxcul.0.maxcul.0.MEQ0679208 created
maxcul.0 2018-01-29 08:35:22.530 info received unknown data:
maxcul.0 2018-01-29 08:35:22.516 info PairDevice: {"src":"1203d8","type":1,"raw":"1001A14D455130363739323038","rssi":-60}
maxcul.0 2018-01-29 08:35:20.663 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:17.519 info received unknown data: 01203D80E94A7001001A14D4551303637393230381C
maxcul.0 2018-01-29 08:35:15.653 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:12.525 info received unknown data: 551303637393230381F
maxcul.0 2018-01-29 08:35:10.659 info received unknown data: 20 900
maxcul.0 2018-01-29 08:35:10.069 info received unknown data: 0000190F2D00F0FB
maxcul.0 2018-01-29 08:35:07.848 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:35:07.833 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:35:07.819 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:35:07.808 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:35:07.795 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:35:07.783 info object maxcul.0.maxcul.0.MEQ0679208.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:35:07.771 info object maxcul.0.maxcul.0.MEQ0679208.rssi created
maxcul.0 2018-01-29 08:35:07.759 info object maxcul.0.maxcul.0.MEQ0679208.config.windowOpenTime created
maxcul.0 2018-01-29 08:35:07.747 info object maxcul.0.maxcul.0.MEQ0679208.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:35:07.734 info object maxcul.0.maxcul.0.MEQ0679208.config.offset created
maxcul.0 2018-01-29 08:35:07.720 info object maxcul.0.maxcul.0.MEQ0679208.config.maximumTemperature created
maxcul.0 2018-01-29 08:35:07.708 info object maxcul.0.maxcul.0.MEQ0679208.config.minimumTemperature created
maxcul.0 2018-01-29 08:35:07.694 info object maxcul.0.maxcul.0.MEQ0679208.config.ecoTemperature created
maxcul.0 2018-01-29 08:35:07.674 info object maxcul.0.maxcul.0.MEQ0679208.config.comfortTemperature created
maxcul.0 2018-01-29 08:35:07.661 info object maxcul.0.maxcul.0.MEQ0679208.batteryLow created
maxcul.0 2018-01-29 08:35:07.646 info object maxcul.0.maxcul.0.MEQ0679208.rfError created
maxcul.0 2018-01-29 08:35:07.619 info object maxcul.0.maxcul.0.MEQ0679208.valvePosition created
maxcul.0 2018-01-29 08:35:07.601 info object maxcul.0.maxcul.0.MEQ0679208.desiredTemperature created
maxcul.0 2018-01-29 08:35:07.583 info object maxcul.0.maxcul.0.MEQ0679208.measuredTemperature created
maxcul.0 2018-01-29 08:35:07.564 info object maxcul.0.maxcul.0.MEQ0679208.mode created
maxcul.0 2018-01-29 08:35:07.537 info object maxcul.0.maxcul.0.MEQ0679208 created
maxcul.0 2018-01-29 08:35:07.518 info PairDevice: {"src":"1203d8","type":1,"raw":"1001A14D455130363739323038","rssi":-59}
maxcul.0 2018-01-29 08:35:05.677 info received unknown data: 00
maxcul.0 2018-01-29 08:35:02.521 info received unknown data: 03D80E94A7001001A14D4551303637393230381E
maxcul.0 2018-01-29 08:35:01.615 info object maxcul.0.maxcul.0.0B71A7.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:35:01.595 info object maxcul.0.maxcul.0.0B71A7.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:35:01.574 info object maxcul.0.maxcul.0.0B71A7.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:35:01.545 info object maxcul.0.maxcul.0.0B71A7.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:35:01.472 info object maxcul.0.maxcul.0.0B71A7.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:35:01.444 info object maxcul.0.maxcul.0.0B71A7.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:35:01.422 info object maxcul.0.maxcul.0.0B71A7.rssi created
maxcul.0 2018-01-29 08:35:01.403 info object maxcul.0.maxcul.0.0B71A7.config.windowOpenTime created
maxcul.0 2018-01-29 08:35:01.389 info object maxcul.0.maxcul.0.0B71A7.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:35:01.373 info object maxcul.0.maxcul.0.0B71A7.config.offset created
maxcul.0 2018-01-29 08:35:01.358 info object maxcul.0.maxcul.0.0B71A7.config.maximumTemperature created
maxcul.0 2018-01-29 08:35:01.343 info object maxcul.0.maxcul.0.0B71A7.config.minimumTemperature created
maxcul.0 2018-01-29 08:35:01.326 info object maxcul.0.maxcul.0.0B71A7.config.ecoTemperature created
maxcul.0 2018-01-29 08:35:01.252 info object maxcul.0.maxcul.0.0B71A7.config.comfortTemperature created
maxcul.0 2018-01-29 08:35:01.221 info object maxcul.0.maxcul.0.0B71A7.batteryLow created
maxcul.0 2018-01-29 08:35:01.198 info object maxcul.0.maxcul.0.0B71A7.rfError created
maxcul.0 2018-01-29 08:35:01.165 info object maxcul.0.maxcul.0.0B71A7.valvePosition created
maxcul.0 2018-01-29 08:35:01.151 info object maxcul.0.maxcul.0.0B71A7.desiredTemperature created
maxcul.0 2018-01-29 08:35:01.132 info object maxcul.0.maxcul.0.0B71A7.measuredTemperature created
maxcul.0 2018-01-29 08:35:01.115 info object maxcul.0.maxcul.0.0B71A7.mode created
maxcul.0 2018-01-29 08:35:01.101 info object maxcul.0.maxcul.0.0B71A7 created
maxcul.0 2018-01-29 08:35:01.081 info received unknown data:
maxcul.0 2018-01-29 08:35:01.071 warn Unknown device: {"src":"0b71a7","mode":1,"desiredTemperature":21,"valvePosition":11,"measuredTemperature":21.1,"dstSetting":1,"lanGateway":1,"panel":0,"rfError":0,"batteryLow":0,"untilString":"","rssi
maxcul.0 2018-01-29 08:35:00.661 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:55.659 info received unknown data: 900
maxcul.0 2018-01-29 08:34:55.645 info received unknown data: 20
maxcul.0 2018-01-29 08:34:50.648 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:45.637 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:41.449 info received unknown data: 90B2A1D
maxcul.0 2018-01-29 08:34:41.396 info received unknown data: 71A7002AD3FD
maxcul.0 2018-01-29 08:34:40.644 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:35.633 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:30.622 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:25.629 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:20.620 info received unknown data: 20 900
maxcul.0 2018-01-29 08:34:15.606 info received unknown data: 20 898
maxcul.0 2018-01-29 08:34:10.612 info received unknown data: 20 893
maxcul.0 2018-01-29 08:34:06.763 info received unknown data: 914
maxcul.0 2018-01-29 08:34:05.603 info received unknown data: 20 888
maxcul.0 2018-01-29 08:34:00.608 info received unknown data: 20 883
maxcul.0 2018-01-29 08:33:55.595 info received unknown data: 20 878
maxcul.0 2018-01-29 08:33:50.585 info received unknown data: 20 873
maxcul.0 2018-01-29 08:33:46.016 info received unknown data: 70004001203D80E94A7001001A14D4551303637393230381B
maxcul.0 2018-01-29 08:33:45.590 info received unknown data: 20 868
maxcul.0 2018-01-29 08:33:41.022 info received unknown data: 001001A14D4551303637393230381C
maxcul.0 2018-01-29 08:33:40.596 info received unknown data: 863
maxcul.0 2018-01-29 08:33:40.580 info received unknown data: 20
maxcul.0 2018-01-29 08:33:36.028 info received unknown data: 30381C
maxcul.0 2018-01-29 08:33:35.585 info received unknown data: 20 858
maxcul.0 2018-01-29 08:33:31.017 info received unknown data: 0004001203D80E94A7001001A14D4551303637393230381C
maxcul.0 2018-01-29 08:33:30.575 info received unknown data: 20 853
maxcul.0 2018-01-29 08:33:29.740 info received unknown data: AE19C1C900011900280B
maxcul.0 2018-01-29 08:33:29.690 info received unknown data: 42044219C1C91203AE0028CC19
maxcul.0 2018-01-29 08:33:26.022 info received unknown data: 1A14D4551303637393230381C
maxcul.0 2018-01-29 08:33:25.580 info received unknown data: 20 848
maxcul.0 2018-01-29 08:33:23.435 info received unknown data: D3FE
maxcul.0 2018-01-29 08:33:21.028 info received unknown data: 3230381D
maxcul.0 2018-01-29 08:33:20.588 info received unknown data: 3
maxcul.0 2018-01-29 08:33:15.575 info received unknown data: 20 838
maxcul.0 2018-01-29 08:33:10.564 info received unknown data: 20 833
maxcul.0 2018-01-29 08:33:08.077 info received unknown data: 94A7001001A14D45513036373931373908
maxcul.0 2018-01-29 08:33:05.571 info received unknown data: 20 828
maxcul.0 2018-01-29 08:33:03.081 info received unknown data: 036373931373909
maxcul.0 2018-01-29 08:33:00.559 info received unknown data: 20 823
maxcul.0 2018-01-29 08:32:58.398 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:32:58.388 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:32:58.370 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:32:58.359 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:32:58.341 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:32:58.329 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:32:58.315 info object maxcul.0.maxcul.0.MEQ0679179.rssi created
maxcul.0 2018-01-29 08:32:58.302 info object maxcul.0.maxcul.0.MEQ0679179.config.windowOpenTime created
maxcul.0 2018-01-29 08:32:58.287 info object maxcul.0.maxcul.0.MEQ0679179.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:32:58.278 info object maxcul.0.maxcul.0.MEQ0679179.config.offset created
maxcul.0 2018-01-29 08:32:58.262 info object maxcul.0.maxcul.0.MEQ0679179.config.maximumTemperature created
maxcul.0 2018-01-29 08:32:58.227 info object maxcul.0.maxcul.0.MEQ0679179.config.minimumTemperature created
maxcul.0 2018-01-29 08:32:58.214 info object maxcul.0.maxcul.0.MEQ0679179.config.ecoTemperature created
maxcul.0 2018-01-29 08:32:58.204 info object maxcul.0.maxcul.0.MEQ0679179.config.comfortTemperature created
maxcul.0 2018-01-29 08:32:58.194 info object maxcul.0.maxcul.0.MEQ0679179.batteryLow created
maxcul.0 2018-01-29 08:32:58.184 info object maxcul.0.maxcul.0.MEQ0679179.rfError created
maxcul.0 2018-01-29 08:32:58.170 info object maxcul.0.maxcul.0.MEQ0679179.valvePosition created
maxcul.0 2018-01-29 08:32:58.146 info object maxcul.0.maxcul.0.MEQ0679179.desiredTemperature created
maxcul.0 2018-01-29 08:32:58.135 info object maxcul.0.maxcul.0.MEQ0679179.measuredTemperature created
maxcul.0 2018-01-29 08:32:58.113 info object maxcul.0.maxcul.0.MEQ0679179.mode created
maxcul.0 2018-01-29 08:32:58.086 info object maxcul.0.maxcul.0.MEQ0679179 created
maxcul.0 2018-01-29 08:32:58.073 info PairDevice: {"src":"1203ae","type":1,"raw":"1001A14D455130363739313739","rssi":-69.5}
maxcul.0 2018-01-29 08:32:55.565 info received unknown data: 20 818
maxcul.0 2018-01-29 08:32:53.076 info received unknown data: 4A7001001A14D45513036373931373909
maxcul.0 2018-01-29 08:32:50.554 info received unknown data: 20 813
maxcul.0 2018-01-29 08:32:48.083 info received unknown data: 73931373909
maxcul.0 2018-01-29 08:32:45.560 info received unknown data: 20 808
maxcul.0 2018-01-29 08:32:43.378 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.valveOffset created
maxcul.0 2018-01-29 08:32:43.366 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.maxValveSetting created
maxcul.0 2018-01-29 08:32:43.354 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.decalcificationHour created
maxcul.0 2018-01-29 08:32:43.341 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.decalcificationDay created
maxcul.0 2018-01-29 08:32:43.329 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.boostValvePosition created
maxcul.0 2018-01-29 08:32:43.314 info object maxcul.0.maxcul.0.MEQ0679179.valveConfig.boostDuration created
maxcul.0 2018-01-29 08:32:43.303 info object maxcul.0.maxcul.0.MEQ0679179.rssi created
maxcul.0 2018-01-29 08:32:43.287 info object maxcul.0.maxcul.0.MEQ0679179.config.windowOpenTime created
maxcul.0 2018-01-29 08:32:43.275 info object maxcul.0.maxcul.0.MEQ0679179.config.windowOpenTemperature created
maxcul.0 2018-01-29 08:32:43.255 info object maxcul.0.maxcul.0.MEQ0679179.config.offset created
maxcul.0 2018-01-29 08:32:43.241 info object maxcul.0.maxcul.0.MEQ0679179.config.maximumTemperature created
maxcul.0 2018-01-29 08:32:43.227 info object maxcul.0.maxcul.0.MEQ0679179.config.minimumTemperature created
maxcul.0 2018-01-29 08:32:43.216 info object maxcul.0.maxcul.0.MEQ0679179.config.ecoTemperature created
maxcul.0 2018-01-29 08:32:43.205 info object maxcul.0.maxcul.0.MEQ0679179.config.comfortTemperature created
maxcul.0 2018-01-29 08:32:43.193 info object maxcul.0.maxcul.0.MEQ0679179.batteryLow created
maxcul.0 2018-01-29 08:32:43.180 info object maxcul.0.maxcul.0.MEQ0679179.rfError created
maxcul.0 2018-01-29 08:32:43.147 info object maxcul.0.maxcul.0.MEQ0679179.valvePosition created
maxcul.0 2018-01-29 08:32:43.136 info object maxcul.0.maxcul.0.MEQ0679179.desiredTemperature created
maxcul.0 2018-01-29 08:32:43.120 info object maxcul.0.maxcul.0.MEQ0679179.measuredTemperature created
maxcul.0 2018-01-29 08:32:43.107 info object maxcul.0.maxcul.0.MEQ0679179.mode created
maxcul.0 2018-01-29 08:32:43.091 info object maxcul.0.maxcul.0.MEQ0679179 created
maxcul.0 2018-01-29 08:32:43.078 info PairDevice: {"src":"1203ae","type":1,"raw":"1001A14D455130363739313739","rssi":-67}

`

Best regards
Maik

In Version 1.0.0 habe ich das Problem "received unknown data". Das Problem tritt nicht sofort auf, erst funktioniert alles wunderbar, aber "plötzlich" geht's dann wieder los. Auch erzeugen meine 3 Thermostate ca. 15 weitere Geräte, die es gar nicht gibt.
Kann mir da jemand helfen?

Nach dem Update auf Node.js 16.15.1 und npm 8.11.0 auf js-controller 4.0.23 kommt folgender Fehler:
`

2022-06-19 14:07:33.447 - error: host.iob Caught by controller[0]: Cannot load serialport module

2022-06-19 14:07:33.449 - error: host.iob instance system.adapter.maxcul.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-06-19 14:08:05.863 - error: maxcul.0 (4677) uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
2022-06-19 14:08:05.866 - error: maxcul.0 (4677) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1189:18)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48)
at Object. (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
2022-06-19 14:08:05.866 - error: maxcul.0 (4677) Exception-Code: ERR_DLOPEN_FAILED: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.

`

Hallo,
trotz aktualisiertem Adapter auf 1.1.2 meint iobroker der Adapter wäre nicht aktuell!

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.

http://forum.iobroker.net/viewtopic.php?f=36&t=6052&p=62409#p62409

I am stuck with the iobroker.maxcul adapter due to the lack of documentation. Can you please extend the read me a bit.

1. Does it support external sensors to be used as MAX! Wallthermostat and ShutterContact replacements like the Pimatic plugin from where it is derived from? Or have developments of both projects split for a long time and since then code is separated?
   In FHEM and Pimatic this feature is call FakeWallThermostat and FakeShutterContact. It has been added to Pimatic with version 1.0.0 committed on Jan 14, 2018
   It would require that components could be "associated" which each other or that the adapter is doing it in the background without visibility for the user.
   Could you please write (or copy and paste for FHEM/Pimatic) what features the iobroker adpater has and which ones not.
   Documentation that I find worth to be copied into the readme, if they apply to iobroker.maxcul or would be worth to be mentioned not beeing support at the moment if this is the case:
   https://wiki.fhem.de/wiki/MAX#Externer_Temperatursensor_f.C3.BCr_Heizk.C3.B6rperregelung
   https://github.com/fbeek/pimatic-maxcul
   This has also been raised in iobroker from with no answer: https://forum.iobroker.net/viewtopic.php?t=20684

Hallo.
ich habe alle meine Thermostate im Automatik modus laufen, also Wochenprogramm.
Aber nur ein Thermostat lässt zu die Temperatur im ioBroker zu ändern. Dabei bleibt es auch im Automatik modus.
bei den anderen muss ich vorher den manuellen modus auswählen, und kann dann erst die Temperatur ändern.

dann habe ich noch zwei Thermostate mit einem Wandthermostat gekoppelt. da lässt sich gar nichts ändern.

bei allen Thermostaten ist es aber möglich das Wochenprogramm zu übertragen.

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

ReadMe Link zeigt auf die github seite vom CUL nicht auf die vom MAXCUL.

Hi,
is it possible to make maxcul compatible with CUNO devices?
I flashed my buggy MaxCube as a CUNO Device but it doesn't work with ioBroker.

Gruß

Jens

Hello
after installing the adapter I get the followin error:
File index_m.html not found

Best regards

Elmar

Hm nach Update von node und dem Controller, hatte ich Probleme den Adapter zu starten, hab dann ja @serialport gelöscht und über git neu installiert.

Danach startete der Adapter und es kam auch kein Fehler in der Log, hatte auch Testhalber mal Temps an einen HT gesendet, der hat direkt reagiert. Jetzt schau ich in der Log, etwas später nun steht folgendes drin..

`

`

Grüße,

Dear Adapter developer,

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!

Mit der CUL FW Version: V 1.67 CUL868 ......auf Busware CUL oder auf geflashtem MaxCube gleicher Fehler ca. jede Stunde.

maxcul.0 | 2020-07-25 08:13:40.034 | info | (9623) Terminated (NO_ERROR): Without reason
maxcul.0 | 2020-07-25 08:13:40.032 | info | (9623) terminating
maxcul.0 | 2020-07-25 08:13:40.014 | error | (9623) unhandled promise rejection: undefined
Unhandled | 2020-07-25 08:13:40.013 | error | promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
maxcul.0 | 2020-07-25 08:13:27.971 | info | (9623) checkTimeIntervalFired

Läuft auf Raspi 4 , Adapter mit reboot mehrfach neu installiert....keine Änderung

Mathias

Hallo, nachdem ich den Stick (der in Fhem ohne probleme ging) per "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A94xxxxx-if00-port0" einhänge und dann den Adapter Starte Blinkt der Adapter zwischen Rot und Gelb und im Log ist das hier zu sehen.

maxcul.0	2020-05-09 23:07:15.309	error	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
maxcul.0	2020-05-09 23:07:15.309	error	at Module._compile (internal/modules/cjs/loader.js:1133:30)
maxcul.0	2020-05-09 23:07:15.309	error	at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22)
maxcul.0	2020-05-09 23:07:15.309	error	at require (internal/modules/cjs/helpers.js:77:18)
maxcul.0	2020-05-09 23:07:15.309	error	at Module.require (internal/modules/cjs/loader.js:1019:19)
maxcul.0	2020-05-09 23:07:15.309	error	at Function.Module._load (internal/modules/cjs/loader.js:877:14)
maxcul.0	2020-05-09 23:07:15.309	error	at Module.load (internal/modules/cjs/loader.js:977:32)
maxcul.0	2020-05-09 23:07:15.309	error	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
maxcul.0	2020-05-09 23:07:15.309	error	at Module._compile (internal/modules/cjs/loader.js:1133:30)
maxcul.0	2020-05-09 23:07:15.309	error	at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:1:36)
maxcul.0	2020-05-09 23:07:15.309	error	at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48)
maxcul.0	2020-05-09 23:07:15.309	error	at require (internal/modules/cjs/helpers.js:77:18)
maxcul.0	2020-05-09 23:07:15.309	error	at Module.require (internal/modules/cjs/loader.js:1019:19)
maxcul.0	2020-05-09 23:07:15.309	error	at Function.Module._load (internal/modules/cjs/loader.js:877:14)
maxcul.0	2020-05-09 23:07:15.309	error	at Module.load (internal/modules/cjs/loader.js:977:32)
maxcul.0	2020-05-09 23:07:15.309	error	at Object.Module._extensions..node (internal/modules/cjs/loader.js:1183:18)
maxcul.0	2020-05-09 23:07:15.309	error	(1873) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-09 23:07:15.309	error	(1873) uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-09 23:07:15.245	info	(1873) starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3
host.iobroker	2020-05-09 23:07:14.157	info	instance system.adapter.maxcul.0 started with pid 1873
host.iobroker	2020-05-09 23:07:14.151	info	"system.adapter.maxcul.0" enabled

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/ioBroker/ioBroker.maxcul

• [E104] No common.titleLang found in io-package.json
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E153] common.dependencies must contain {"js-controller": ">=1.5.8"} or {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E504] found setInterval in "main.js, but no clearInterval detected
• [E605] No actual year found in copyright. Please add "Copyright (c) 2017-2022 bluefox [email protected]" at the end of README.md

Thanks,
your automatic adapter checker.

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!

Der MaxCul-Adapter (Iobroker) hat mittlerweile, wie im Changelog beschrieben, Wochenprogramme integriert, womit man die Thermostate direkt mit einem Wochenprogramm versehen kann. Leider gehen meine Einträge im Iobroker nicht an das Thermostat. Anzeige "Bestätigt : False", der Thermostat schaltet auch nicht nach den von mir eingestellten Zeiten. Die Werte BatteryLow, desiredTemperature, measuredTemperature, mode, rferror, rssi und valvePosition überträgt der CUL sauber zum Thermostat und zurück, den Rest nicht. Ich habe die Thermostate gerade im Modus "manuell" laufen und regle das alles über Skripte, die Wochenprogramme direkt am Thermostat zu hinterlegen würde natürlich traffic sparen. Mache ich etwas falsch oder ist das ein Bug?

Ich schreibe mal in deutsch, da meines Erachtens die MAX! Komponenten auch nur hier benutzt werden.
Entweder habe ich es noch nicht entdeckt, oder es fehlt noch etwas.
Ich betreibe einen umgeflashten Cube und komme von FHEM.
Dort konnte man schön die Wochenprogramme erstellen und zum Thermostat transferieren, so dass auch ohne Cube diese arbeiten. Zudem fehlt mir die Möglichkeit die Komponenten untereinander zu verheiraten. Auch hier kann ich z.B. den Fensterkontakt mit einem Thermostat verbinden, so dass beim Öffnen des Fenster dies ohne Cube auf die Temperatur fährt, welche unter "Fenster offen" hinterlegt ist.
Mir ist bekannt, dass es für VIS eine Vorlage gibt "Heizungsthermostatsteuerung 2.0 - Script". Aber hier steuert dann iobroker und nicht die Thermonstate selbst - oder?

Hallo,

seit der Version 1.0.0 des maxcul Adapters ist das Wandthermostat integriert.

Mir ist aufgefallen, dass das Schalten am Wandthermostat erst verzögert im Wert maxcul.0.JEQ0604903.desiredTemperature dargestellt wird.

Bei Tests mit der Stoppuhr kam ich auf Verzögerungen zwischen 13 Sekunden und 2 Minute 40 Sekunden.

Logfile im Debug-Mode siehe unten. Hier wurde der Wert desired temp auf 19.5 geändert und nach ca. 52 Sekunden angezeigt.

2018-10-30 17:45:32.201 - info: host.Elzershark instance system.adapter.maxcul.0 started with pid 4862
2018-10-30 17:45:33.817 - info: maxcul.0 States connected to redis: 127.0.0.1:6379
2018-10-30 17:45:34.024 - info: maxcul.0 starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v6.13.1
2018-10-30 17:45:34.516 - info: maxcul.0 using serial device /dev/ttyUSB1@38400
2018-10-30 17:45:34.544 - info: maxcul.0 serialPort /dev/ttyUSB1 is open!
2018-10-30 17:45:36.574 - info: maxcul.0 CUL FW Version: V 1.67 nanoCUL868
2018-10-30 17:56:27.133 - info: host.Elzershark object change system.adapter.maxcul.0
2018-10-30 17:56:27.144 - info: host.Elzershark stopInstance system.adapter.maxcul.0
2018-10-30 17:56:27.145 - info: host.Elzershark stopInstance system.adapter.maxcul.0 killing pid 4862
2018-10-30 17:56:27.170 - info: maxcul.0 terminating
2018-10-30 17:56:27.211 - info: host.Elzershark instance system.adapter.maxcul.0 terminated with code 0 (OK)
2018-10-30 17:56:29.731 - info: host.Elzershark instance system.adapter.maxcul.0 started with pid 5482
2018-10-30 17:56:31.393 - debug: maxcul.0 objectDB connected
2018-10-30 17:56:31.466 - debug: maxcul.0 statesDB connected
2018-10-30 17:56:31.478 - info: maxcul.0 States connected to redis: 127.0.0.1:6379
2018-10-30 17:56:31.688 - info: maxcul.0 starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v6.13.1
2018-10-30 17:56:32.220 - info: maxcul.0 using serial device /dev/ttyUSB1@38400
2018-10-30 17:56:32.242 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.connection {"val":false,"ack":true,"ts":1540918592238,"q":0,"from":"system.adapter.maxcul.0","lc":1540918587153}
2018-10-30 17:56:32.258 - info: maxcul.0 serialPort /dev/ttyUSB1 is open!
2018-10-30 17:56:34.264 - debug: maxcul.0 check CUL Firmware version
2018-10-30 17:56:34.271 - debug: maxcul.0 Requested CUL Version...
2018-10-30 17:56:34.292 - debug: maxcul.0 incoming raw data from CUL: V 1.67 nanoCUL868
2018-10-30 17:56:34.297 - info: maxcul.0 CUL FW Version: V 1.67 nanoCUL868
2018-10-30 17:56:34.309 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.version {"val":"V 1.67 nanoCUL868","ack":true,"ts":1540918594304,"q":0,"from":"system.adapter.maxcul.0","lc":1540647851277}
2018-10-30 17:56:34.311 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.connection {"val":true,"ack":true,"ts":1540918594306,"q":0,"from":"system.adapter.maxcul.0","lc":1540918594306}
2018-10-30 17:56:37.244 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:56:37.251 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:56:37.258 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 453)
2018-10-30 17:56:37.269 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.limitOverflow {"val":false,"ack":true,"ts":1540918597263,"q":0,"from":"system.adapter.maxcul.0","lc":1540774683352}
2018-10-30 17:56:37.271 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":453,"ack":true,"ts":1540918597264,"q":0,"from":"system.adapter.maxcul.0","lc":1540918597264}
2018-10-30 17:56:38.276 - debug: maxcul.0 enable MAX! Mode of the CUL868
2018-10-30 17:56:38.278 - debug: maxcul.0 X20 written
2018-10-30 17:56:38.283 - debug: maxcul.0 X20 drained
2018-10-30 17:56:38.285 - debug: maxcul.0 Zr written
2018-10-30 17:56:38.289 - debug: maxcul.0 Zr drained
2018-10-30 17:56:38.292 - debug: maxcul.0 Za written
2018-10-30 17:56:38.295 - debug: maxcul.0 Za drained
2018-10-30 17:56:42.251 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:56:42.255 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:56:42.256 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 453)
2018-10-30 17:56:42.264 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":458,"ack":true,"ts":1540918602261,"q":0,"from":"system.adapter.maxcul.0","lc":1540918602261}
2018-10-30 17:56:47.258 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:56:47.262 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:56:47.264 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 458)
2018-10-30 17:56:47.287 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":463,"ack":true,"ts":1540918607276,"q":0,"from":"system.adapter.maxcul.0","lc":1540918607276}
2018-10-30 17:56:52.264 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:56:52.268 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:56:52.272 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 463)
2018-10-30 17:56:52.286 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":468,"ack":true,"ts":1540918612283,"q":0,"from":"system.adapter.maxcul.0","lc":1540918612283}
2018-10-30 17:56:57.267 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:56:57.270 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:56:57.272 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 468)
2018-10-30 17:56:57.302 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":473,"ack":true,"ts":1540918617300,"q":0,"from":"system.adapter.maxcul.0","lc":1540918617300}
2018-10-30 17:57:02.268 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:02.272 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:02.276 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 473)
2018-10-30 17:57:02.293 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":478,"ack":true,"ts":1540918622290,"q":0,"from":"system.adapter.maxcul.0","lc":1540918622290}
2018-10-30 17:57:06.266 - debug: maxcul.0 incoming raw data from CUL: Z0B9F000212345605FE66000000
2018-10-30 17:57:06.271 - debug: maxcul.0 decoding Message Z0B9F000212345605FE66000000
2018-10-30 17:57:06.273 - debug: maxcul.0 RSSI for Message: -74
2018-10-30 17:57:06.279 - debug: maxcul.0 ignored auto-ack packet
2018-10-30 17:57:06.286 - debug: maxcul.0 incoming raw data from CUL: Z0B9F054005FE66123456006702
2018-10-30 17:57:06.287 - debug: maxcul.0 decoding Message Z0B9F054005FE66123456006702
2018-10-30 17:57:06.288 - debug: maxcul.0 RSSI for Message: -73
2018-10-30 17:57:06.290 - debug: maxcul.0 received unknown command id 40
2018-10-30 17:57:07.271 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:07.274 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:07.276 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 478)
2018-10-30 17:57:07.285 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":474,"ack":true,"ts":1540918627282,"q":0,"from":"system.adapter.maxcul.0","lc":1540918627282}
2018-10-30 17:57:12.278 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:12.281 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:12.284 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 474)
2018-10-30 17:57:12.297 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":479,"ack":true,"ts":1540918632293,"q":0,"from":"system.adapter.maxcul.0","lc":1540918632293}
2018-10-30 17:57:17.296 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:17.303 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:17.305 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 479)
2018-10-30 17:57:17.310 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":484,"ack":true,"ts":1540918637308,"q":0,"from":"system.adapter.maxcul.0","lc":1540918637308}
2018-10-30 17:57:22.295 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:22.298 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:22.301 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 484)
2018-10-30 17:57:22.319 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":489,"ack":true,"ts":1540918642316,"q":0,"from":"system.adapter.maxcul.0","lc":1540918642316}
2018-10-30 17:57:27.299 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:27.303 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:27.304 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 489)
2018-10-30 17:57:27.312 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":494,"ack":true,"ts":1540918647309,"q":0,"from":"system.adapter.maxcul.0","lc":1540918647309}
2018-10-30 17:57:32.299 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:32.302 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:32.303 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 494)
2018-10-30 17:57:32.321 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":499,"ack":true,"ts":1540918652319,"q":0,"from":"system.adapter.maxcul.0","lc":1540918652319}
2018-10-30 17:57:37.305 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:37.309 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:37.311 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 499)
2018-10-30 17:57:37.317 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":504,"ack":true,"ts":1540918657315,"q":0,"from":"system.adapter.maxcul.0","lc":1540918657315}
2018-10-30 17:57:42.313 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:42.316 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:42.318 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 504)
2018-10-30 17:57:42.327 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":509,"ack":true,"ts":1540918662324,"q":0,"from":"system.adapter.maxcul.0","lc":1540918662324}
2018-10-30 17:57:47.314 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:47.318 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:47.321 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 509)
2018-10-30 17:57:47.344 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":514,"ack":true,"ts":1540918667340,"q":0,"from":"system.adapter.maxcul.0","lc":1540918667340}
2018-10-30 17:57:48.711 - debug: maxcul.0 incoming raw data from CUL: Z0C03044205FE660000000027D501
2018-10-30 17:57:48.712 - debug: maxcul.0 decoding Message Z0C03044205FE660000000027D501
2018-10-30 17:57:48.718 - debug: maxcul.0 RSSI for Message: -73.5
2018-10-30 17:57:48.726 - debug: maxcul.0 got data from wallthermostat 05fe66 desired temp: 19.5 - measured temp: 21.3
2018-10-30 17:57:48.733 - debug: maxcul.0 WallThermostatControlRecieved: {"src":"05fe66","desired":19.5,"measured":21.3}
2018-10-30 17:57:52.263 - debug: maxcul.0 incoming raw data from CUL: Z0FA0047005FE660000000019012700D502
2018-10-30 17:57:52.264 - debug: maxcul.0 decoding Message Z0FA0047005FE660000000019012700D502
2018-10-30 17:57:52.265 - debug: maxcul.0 RSSI for Message: -73
2018-10-30 17:57:52.268 - debug: maxcul.0 got data from wallthermostat state 05fe66 with payload 19012700D5
2018-10-30 17:57:52.301 - debug: maxcul.0 WallThermostatStateReceived: {"src":"05fe66","mode":"1","desiredTemperature":19.5,"measuredTemperature":21.3,"dstSetting":1,"langateway":1,"panel":0,"rferror":0,"batterylow":0}
2018-10-30 17:57:52.308 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.JEQ0604903.mode {"val":1,"ack":true,"ts":1540918672303,"q":0,"from":"system.adapter.maxcul.0","lc":1540712936697}
2018-10-30 17:57:52.319 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:52.321 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.JEQ0604903.desiredTemperature {"val":19.5,"ack":true,"ts":1540918672311,"q":0,"from":"system.adapter.maxcul.0","lc":1540918672311}
2018-10-30 17:57:52.323 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.JEQ0615825.desiredTemperature {"val":19.5,"ack":false,"ts":1540918672318,"q":0,"from":"system.adapter.javascript.0","lc":1540918672318}
2018-10-30 17:57:52.325 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:52.328 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 514)
2018-10-30 17:57:52.331 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.JEQ0604903.measuredTemperature {"val":21.3,"ack":true,"ts":1540918672327,"q":0,"from":"system.adapter.maxcul.0","lc":1540918672327}
2018-10-30 17:57:52.336 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":519,"ack":true,"ts":1540918672334,"q":0,"from":"system.adapter.maxcul.0","lc":1540918672334}
2018-10-30 17:57:53.324 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.JEQ0614929.desiredTemperature {"val":19.5,"ack":false,"ts":1540918673320,"q":0,"from":"system.adapter.javascript.0","lc":1540918673320}
2018-10-30 17:57:53.337 - debug: maxcul.0 sendTemperature(maxcul.0.JEQ0615825, 19.5, 1)
2018-10-30 17:57:53.357 - debug: maxcul.0 Send Packet to CUL: Zs0b01004012345605dd490067, awaiting drain event
2018-10-30 17:57:53.360 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:54.329 - debug: maxcul.0 sendTemperature(maxcul.0.JEQ0614929, 19.5, 1)
2018-10-30 17:57:54.441 - debug: maxcul.0 incoming raw data from CUL: Z0E01020205DD49123456000119432705
2018-10-30 17:57:54.442 - debug: maxcul.0 decoding Message Z0E01020205DD49123456000119432705
2018-10-30 17:57:54.443 - debug: maxcul.0 RSSI for Message: -71.5
2018-10-30 17:57:54.448 - debug: maxcul.0 got OK-ACK Packet from 05dd49
2018-10-30 17:57:54.451 - debug: maxcul.0 Queued send for Zs0b01004012345605e1140067 (Queue length = 2)
2018-10-30 17:57:55.362 - debug: maxcul.0 delayed next send by 2000ms (Queue length left = 2, Current Credit = 519)
2018-10-30 17:57:55.364 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:55.368 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:55.371 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 1, Current Credit = 519)
2018-10-30 17:57:55.372 - debug: maxcul.0 Send Packet to CUL: Zs0b01004012345605e1140067, awaiting drain event
2018-10-30 17:57:55.374 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:55.379 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":412,"ack":true,"ts":1540918675376,"q":0,"from":"system.adapter.maxcul.0","lc":1540918675376}
2018-10-30 17:57:56.455 - debug: maxcul.0 incoming raw data from CUL: Z0E01020205E11412345600011941271F
2018-10-30 17:57:56.456 - debug: maxcul.0 decoding Message Z0E01020205E11412345600011941271F
2018-10-30 17:57:56.457 - debug: maxcul.0 RSSI for Message: -58.5
2018-10-30 17:57:56.461 - debug: maxcul.0 got OK-ACK Packet from 05e114
2018-10-30 17:57:57.320 - debug: maxcul.0 Ignore command because already in queue X
2018-10-30 17:57:57.376 - debug: maxcul.0 delayed next send by 2000ms (Queue length left = 1, Current Credit = 412)
2018-10-30 17:57:57.380 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:57:57.389 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:57:57.403 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 412)
2018-10-30 17:57:57.428 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":305,"ack":true,"ts":1540918677407,"q":0,"from":"system.adapter.maxcul.0","lc":1540918677407}
2018-10-30 17:58:02.328 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:02.333 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:02.335 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 305)
2018-10-30 17:58:02.339 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":310,"ack":true,"ts":1540918682337,"q":0,"from":"system.adapter.maxcul.0","lc":1540918682337}
2018-10-30 17:58:07.346 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:07.354 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:07.358 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 315)
2018-10-30 17:58:07.359 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":315,"ack":true,"ts":1540918687355,"q":0,"from":"system.adapter.maxcul.0","lc":1540918687355}
2018-10-30 17:58:12.348 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:12.351 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:12.353 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 315)
2018-10-30 17:58:12.358 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":320,"ack":true,"ts":1540918692356,"q":0,"from":"system.adapter.maxcul.0","lc":1540918692356}
2018-10-30 17:58:17.349 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:17.352 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:17.354 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 320)
2018-10-30 17:58:17.371 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":325,"ack":true,"ts":1540918697367,"q":0,"from":"system.adapter.maxcul.0","lc":1540918697367}
2018-10-30 17:58:22.355 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:22.358 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:22.360 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 325)
2018-10-30 17:58:22.364 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":330,"ack":true,"ts":1540918702362,"q":0,"from":"system.adapter.maxcul.0","lc":1540918702362}
2018-10-30 17:58:27.362 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:27.365 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:27.366 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 330)
2018-10-30 17:58:27.381 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":335,"ack":true,"ts":1540918707372,"q":0,"from":"system.adapter.maxcul.0","lc":1540918707372}
2018-10-30 17:58:32.363 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:32.366 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:32.369 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 335)
2018-10-30 17:58:32.385 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":340,"ack":true,"ts":1540918712383,"q":0,"from":"system.adapter.maxcul.0","lc":1540918712383}
2018-10-30 17:58:37.367 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:37.370 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:37.373 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 340)
2018-10-30 17:58:37.379 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":345,"ack":true,"ts":1540918717377,"q":0,"from":"system.adapter.maxcul.0","lc":1540918717377}
2018-10-30 17:58:40.289 - debug: maxcul.0 redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1540918720286,"q":0,"from":"system.adapter.admin.0","lc":1540918720286}
2018-10-30 17:58:40.290 - debug: maxcul.0 system.adapter.admin.0: logging true
2018-10-30 17:58:42.374 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:42.378 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:42.380 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 345)
2018-10-30 17:58:42.391 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":351,"ack":true,"ts":1540918722389,"q":0,"from":"system.adapter.maxcul.0","lc":1540918722389}
2018-10-30 17:58:47.377 - debug: maxcul.0 Send Packet to CUL: X, awaiting drain event
2018-10-30 17:58:47.380 - debug: maxcul.0 serial port buffer have been drained
2018-10-30 17:58:47.382 - debug: maxcul.0 delayed next send by 0ms (Queue length left = 0, Current Credit = 351)
2018-10-30 17:58:47.402 - debug: maxcul.0 redis pmessage io.maxcul.0.* io.maxcul.0.info.quota {"val":356,"ack":true,"ts":1540918727399,"q":0,"from":"system.adapter.maxcul.0","lc":1540918727399} 

System:
Max! Cul Version 1.0.0
nanoCUL FTDI m. CC1101 868Mhz Transceiver CUL für FHEM FW 1.67 an Serialport: /dev/ttyUSB1
Raspberry Pi 3
Linux Elzershark 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35 BST 2018 armv7l GNU/Linux