pimatic-maxcul

---

The plugin doesn’t get the initial version string, so there must be an mistake in the beginning. I also reseted and tried to pair one of my devices without success.

Just at the moment Pimatic crashed with that:

<— JS stacktrace —>

==== JS stack trace =========================================

0: ExitFrame [pc: 0x2c3eae9c]
1: StubFrame [pc: 0x2c3bfa20]

Security context: 0x74112705 <JSObject>
2: unixRead [0x70cb7cdd] [/home/pi/pimatic-app/node_modules/pimatic-maxcul/node_modules/serialport/lib/bindings/unix-read.js:~6] [pc=0x56d298fc](this=0x346ab7a1 <BaseBinding map = 0x2acb5f89>,buffer=0x346ad0d1 <Uint8Array map = 0x2aca7151>,offset=15,length=65521)
3: /* anonymous /(aka / anonymous */) [0x5943f6f5] [/home/pi…

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

The actual log when changing a temperature:

19:05:17.834 [pimatic-maxcul] Set desired temperature 5 for deviceId 065e06
19:05:17.850 [pimatic-maxcul] Send Packet to CUL: 0b010040123456065e06004a, awaiting drain event
19:05:17.862 [pimatic-maxcul] serial port buffer have been drained
19:05:18.943 [pimatic-maxcul] incoming raw data from CUL: Z0E010202065E06123456000119000A
19:05:18.948 [pimatic-maxcul] decoding Message Z0E010202065E06123456000119000A
19:05:18.950 [pimatic-maxcul] RSSI for Message : -69
19:05:18.952 [pimatic-maxcul] packet length missmatch
19:05:18.954 [pimatic-maxcul] message was no valid MAX! paket.
19:05:20.851 [pimatic-maxcul] Retransmit packet 0b010040123456065e06004a, try 1 of 3
19:05:20.856 [pimatic-maxcul] Send Packet to CUL: 0b010040123456065e06004a, awaiting drain event
19:05:20.877 [pimatic-maxcul] serial port buffer have been drained
19:05:21.944 [pimatic-maxcul] incoming raw data from CUL: Z0E010202065E06123456000119000A
19:05:21.948 [pimatic-maxcul] decoding Message Z0E010202065E06123456000119000A
19:05:21.949 [pimatic-maxcul] RSSI for Message : -69
19:05:21.951 [pimatic-maxcul] packet length missmatch
19:05:21.953 [pimatic-maxcul] message was no valid MAX! paket.
19:05:23.854 [pimatic-maxcul] Retransmit packet 0b010040123456065e06004a, try 2 of 3
19:05:23.860 [pimatic-maxcul] Send Packet to CUL: 0b010040123456065e06004a, awaiting drain event
19:05:23.877 [pimatic-maxcul] serial port buffer have been drained
19:05:24.947 [pimatic-maxcul] incoming raw data from CUL: Z0E010202065E06123456000119000A
19:05:24.952 [pimatic-maxcul] decoding Message Z0E010202065E06123456000119000A
19:05:24.954 [pimatic-maxcul] RSSI for Message : -69
19:05:24.957 [pimatic-maxcul] packet length missmatch
19:05:24.959 [pimatic-maxcul] message was no valid MAX! paket.
19:05:26.854 [pimatic-maxcul] Retransmit packet 0b010040123456065e06004a, try 3 of 3
19:05:26.858 [pimatic-maxcul] Send Packet to CUL: 0b010040123456065e06004a, awaiting drain event
19:05:26.877 [pimatic-maxcul] serial port buffer have been drained
19:05:27.951 [pimatic-maxcul] incoming raw data from CUL: Z0E010202065E06123456000119000A
19:05:27.954 [pimatic-maxcul] decoding Message Z0E010202065E06123456000119000A
19:05:27.956 [pimatic-maxcul] RSSI for Message : -69
19:05:27.957 [pimatic-maxcul] packet length missmatch
19:05:27.959 [pimatic-maxcul] message was no valid MAX! paket.
19:05:29.855 [pimatic-maxcul] Paket 0b010040123456065e06004a send but no response!
19:05:29.859 [pimatic-maxcul] no packet to handle in send queue

In your log from above there is the Version String:

03:21:29.420 [pimatic-maxcul] incoming raw data from CUL: V 1.66_nocredits nanoCUL868
03:21:29.422 [pimatic-maxcul] Got Version String
03:21:29.424 [pimatic-maxcul] CUL FW Version: V 1.66_nocredits nanoCUL868

At the moment i cannot help you, I can not replicate any error in my testing rig and all of my three systems where working without any problem and there are no other user that have such a problem with the new version.

The messages got send from your system but there is no valid response. I have decoded your messages by hand an they are not valid.

The version string is from running with FHEM in the background. When only running Pimatic there comes no version string, except one time in the beginning of my tries.

Then I have to wait until new versions of Pimatic, node or the plugin , the winter is still far away

You should not run fhem in the background, serial port usage should be exclusive in linux.

If you use two programs on the same port that generates a lot of problems.

I don’t see there any problem with pimatic or the plugin in the moment…

@fbeek Unfortunately, I have to report exactly the same behavior as @hanss described above. Absolutely no idea how to fix it. It definately started with the update of the maxcul plugin.

Mh ok, as i cannot replicate the error from hanss on my testing machines I need your help to analyze the error.

It would be nice if you can open an issue on github (https://github.com/fbeek/pimatic-maxcul/issues) and add the following informations:

1.) Your plugin config
2.) Your device configs for the maxcul devices
3.) The debug log for the pimatic start from start to finish (So that i can see the pimatic and plugin init)
4.) Some Debug messages from the plugin (so that i can see some send and received messages. Simply set the temperature in pimatic and open an window conntact)
5.) Detailed error discription (what do you expect as result and what is happening instead)