Warning: !Not! sending packet ... init sequence is not complete

English Forums Bugs
#1

Hi

when starting homegear the first messages I see are the following in the homegear.err:

11/03/16 18:17:03.465 Module HomeMatic BidCoS: COC "A3E298": Warning: !!!Not!!! sending packet, because init sequence is not complete: 0E69A011FD0801370EEF0201000000
11/03/16 18:17:03.468 Module HomeMatic BidCoS: COC "A3E298": Warning: !!!Not!!! sending packet, because init sequence is not complete: 0EAFA011FD080137CF240201C80000
11/03/16 18:17:03.469 Module HomeMatic BidCoS: COC "A3E298": Warning: !!!Not!!! sending packet, because init sequence is not complete: 0E90A011FD080137C2F50201C80000
11/03/16 18:17:03.471 Module HomeMatic BidCoS: COC "A3E298": Warning: !!!Not!!! sending packet, because init sequence is not complete: 0E86A011FD080137C5440201C80000
11/03/16 18:17:03.472 Module HomeMatic BidCoS: COC "A3E298": Warning: !!!Not!!! sending packet, because init sequence is not complete: 0E75A011FD080137038A0201C80000

when doing a debug I see the following in homegear.log around the same timestamp:

11/03/16 18:17:02.893 Module HomeMatic BidCoS: Info: Central address set to 0xFD0801.
11/03/16 18:17:02.898 Module HomeMatic BidCoS: Loading peer 1
11/03/16 18:17:02.916 Module HomeMatic BidCoS: Debug: AES key of peer 1 is current.
11/03/16 18:17:02.917 Module HomeMatic BidCoS: Loading peer 2
11/03/16 18:17:02.925 Debug: Could not set parameter LOWBAT on channel 0 for peer 2. Parameter does not exist.
11/03/16 18:17:02.926 Module HomeMatic BidCoS: Loading peer 3
11/03/16 18:17:02.934 Debug: Could not set parameter LOWBAT on channel 0 for peer 3. Parameter does not exist.
11/03/16 18:17:02.934 Module HomeMatic BidCoS: Loading peer 4
11/03/16 18:17:02.943 Debug: Could not set parameter LOWBAT on channel 0 for peer 4. Parameter does not exist.
11/03/16 18:17:02.943 Module HomeMatic BidCoS: Loading peer 5
11/03/16 18:17:02.951 Debug: Could not set parameter LOWBAT on channel 0 for peer 5. Parameter does not exist.
11/03/16 18:17:02.952 Module HomeMatic BidCoS: Loading peer 6
11/03/16 18:17:02.960 Debug: Could not set parameter LOWBAT on channel 0 for peer 6. Parameter does not exist.
11/03/16 18:17:02.960 Module HomeMatic BidCoS: Loading peer 7
11/03/16 18:17:02.964 Module HomeMatic BidCoS: Loading peer 8
11/03/16 18:17:02.967 Module HomeMatic BidCoS: Loading peer 9

the peers which are complained about are:

      2 │                           │   37CF24 │    MEQ0270691 │ 00AC │ HM-ES-PMSw1-Pl            │      2.5 │             No │      No │      No
      3 │                           │   37C2F5 │    MEQ0270420 │ 00AC │ HM-ES-PMSw1-Pl            │      2.5 │             No │      No │      No
      4 │                           │   37C544 │    MEQ0270274 │ 00AC │ HM-ES-PMSw1-Pl            │      2.5 │             No │      No │      No
      5 │                           │   37038A │    MEQ0272739 │ 00AC │ HM-ES-PMSw1-Pl            │      2.5 │             No │      No │      No
      6 │                           │   370EEF │    MEQ0274053 │ 00AC │ HM-ES-PMSw1-Pl            │      2.5 │             No │      No │      No

so far it seems not to have any impact, just curious as the HM-ES-PMSw1-Pl does not have any LOWBAT.

running on an Raspberry Pi 3 Model B

homegear -v
Homegear version 0.7.15-1580
Copyright © 2013-2017 Sathya Laufer

Git commit SHA of libhomegear-base: -
Git branch of libhomegear-base: -
Git commit SHA of Homegear: -
Git branch of Homegear: -

PHP (License: PHP License):
This product includes PHP software, freely available from http://www.php.net/software/
Copyright © 1999-2017 The PHP Group. All rights reserved.

uname -a
Linux lemonpi 4.14.22-v7+ #1096 SMP Mon Feb 26 19:14:22 GMT 2018 armv7l GNU/Linux

cheers

#2

Hey @jipp,

please edit your post and use the formating options of the forum for your log and console output.

grafik

Also, please tell us which version of homegear you are running and on which platform?
Maybe you should update your homegear installation, as the current device description files do not contain LOWBAT for HM-ES-PMSw: https://github.com/Homegear/Homegear-HomeMaticBidCoS/blob/master/misc/Device%20Description%20Files/rf_es_pmsw.xml

Cheers,
Patrik

#3

updated the original post with the missing data - sorry for this :frowning:

1 Like
#4

Hi

I did some further investigations…

After I disabled in Node-BLUE some of the ‘Output value on startup’ checkboxes related to the Peers listed in the log, the messages are gone during the startup.

So in the end it looks like that I faced a kind of race condition when homegear and Node-BLUE starts.

cheers

#5

I’m starting Node-BLUE after the interfaces now. Show the messages should be gone.

Thanks and cheers,

Sathya

#6

thx - sounds like a valid simple solution :slight_smile: