Queues werden nur langsam abgearbeitet (MAX)

Deutsche Foren Fehler
#1

Hi,

ich habe noch ein zweites Setup, bestehend aus:
[ul]
[li]MAX CUBE umgeflasht zu CUL[/li]
[li] 2x BC-TC-C-WM [v1.3][/li]
[li] 1x BC-TC-C-WM [v1.0][/li]
[li] 2x BC-SC-Rd-WM [v1.3][/li]
[li] 2x BC-SC-Rd-WM-2 [v1.0][/li]
[li] 3x BC-RT-TRX-CyG [v1.5][/li]
[li] 1x BC-RT-TRX-CyG [v1.8][/li]
[li] 1x BC-TS-Sw-Pl [v1.1][/li][/ul]

Anlernen hat super geklappt, auch das einrichten von Verknüpfungen. Für das Konfigurieren des Wochenprogramms habe ich ein kleines Excel-Programm gemacht welches einen String für PutParamSet für alle Parameter erstellt:

"LEQ0981263", "MASTER", {

"ENDTIME_MONDAY_1": 1440, "TEMPERATURE_MONDAY_1": 18.01,
"ENDTIME_MONDAY_2": 1440, "TEMPERATURE_MONDAY_2": 5.01,
"ENDTIME_MONDAY_3": 1440, "TEMPERATURE_MONDAY_3": 5.01,
"ENDTIME_MONDAY_4": 1440, "TEMPERATURE_MONDAY_4": 5.01,
"ENDTIME_MONDAY_5": 1440, "TEMPERATURE_MONDAY_5": 5.01,
"ENDTIME_MONDAY_6": 1440, "TEMPERATURE_MONDAY_6": 5.01,
"ENDTIME_MONDAY_7": 1440, "TEMPERATURE_MONDAY_7": 5.01,
"ENDTIME_MONDAY_8": 1440, "TEMPERATURE_MONDAY_8": 5.01,
"ENDTIME_MONDAY_9": 1440, "TEMPERATURE_MONDAY_9": 5.01,
"ENDTIME_MONDAY_10": 1440, "TEMPERATURE_MONDAY_10": 5.01,
"ENDTIME_MONDAY_11": 1440, "TEMPERATURE_MONDAY_11": 5.01,
"ENDTIME_MONDAY_12": 1440, "TEMPERATURE_MONDAY_12": 5.01,
"ENDTIME_MONDAY_13": 1440, "TEMPERATURE_MONDAY_13": 5.01,


"ENDTIME_TUESDAY_1": 1440, "TEMPERATURE_TUESDAY_1": 18.01,
"ENDTIME_TUESDAY_2": 1440, "TEMPERATURE_TUESDAY_2": 5.01,
"ENDTIME_TUESDAY_3": 1440, "TEMPERATURE_TUESDAY_3": 5.01,
"ENDTIME_TUESDAY_4": 1440, "TEMPERATURE_TUESDAY_4": 5.01,
"ENDTIME_TUESDAY_5": 1440, "TEMPERATURE_TUESDAY_5": 5.01,
"ENDTIME_TUESDAY_6": 1440, "TEMPERATURE_TUESDAY_6": 5.01,
"ENDTIME_TUESDAY_7": 1440, "TEMPERATURE_TUESDAY_7": 5.01,
"ENDTIME_TUESDAY_8": 1440, "TEMPERATURE_TUESDAY_8": 5.01,
"ENDTIME_TUESDAY_9": 1440, "TEMPERATURE_TUESDAY_9": 5.01,
"ENDTIME_TUESDAY_10": 1440, "TEMPERATURE_TUESDAY_10": 5.01,
"ENDTIME_TUESDAY_11": 1440, "TEMPERATURE_TUESDAY_11": 5.01,
"ENDTIME_TUESDAY_12": 1440, "TEMPERATURE_TUESDAY_12": 5.01,
"ENDTIME_TUESDAY_13": 1440, "TEMPERATURE_TUESDAY_13": 5.01,


"ENDTIME_WEDNESDAY_1": 1440, "TEMPERATURE_WEDNESDAY_1": 18.01,
"ENDTIME_WEDNESDAY_2": 1440, "TEMPERATURE_WEDNESDAY_2": 5.01,
"ENDTIME_WEDNESDAY_3": 1440, "TEMPERATURE_WEDNESDAY_3": 5.01,
"ENDTIME_WEDNESDAY_4": 1440, "TEMPERATURE_WEDNESDAY_4": 5.01,
"ENDTIME_WEDNESDAY_5": 1440, "TEMPERATURE_WEDNESDAY_5": 5.01,
"ENDTIME_WEDNESDAY_6": 1440, "TEMPERATURE_WEDNESDAY_6": 5.01,
"ENDTIME_WEDNESDAY_7": 1440, "TEMPERATURE_WEDNESDAY_7": 5.01,
"ENDTIME_WEDNESDAY_8": 1440, "TEMPERATURE_WEDNESDAY_8": 5.01,
"ENDTIME_WEDNESDAY_9": 1440, "TEMPERATURE_WEDNESDAY_9": 5.01,
"ENDTIME_WEDNESDAY_10": 1440, "TEMPERATURE_WEDNESDAY_10": 5.01,
"ENDTIME_WEDNESDAY_11": 1440, "TEMPERATURE_WEDNESDAY_11": 5.01,
"ENDTIME_WEDNESDAY_12": 1440, "TEMPERATURE_WEDNESDAY_12": 5.01,
"ENDTIME_WEDNESDAY_13": 1440, "TEMPERATURE_WEDNESDAY_13": 5.01,


"ENDTIME_THURSDAY_1": 1440, "TEMPERATURE_THURSDAY_1": 18.01,
"ENDTIME_THURSDAY_2": 1440, "TEMPERATURE_THURSDAY_2": 5.01,
"ENDTIME_THURSDAY_3": 1440, "TEMPERATURE_THURSDAY_3": 5.01,
"ENDTIME_THURSDAY_4": 1440, "TEMPERATURE_THURSDAY_4": 5.01,
"ENDTIME_THURSDAY_5": 1440, "TEMPERATURE_THURSDAY_5": 5.01,
"ENDTIME_THURSDAY_6": 1440, "TEMPERATURE_THURSDAY_6": 5.01,
"ENDTIME_THURSDAY_7": 1440, "TEMPERATURE_THURSDAY_7": 5.01,
"ENDTIME_THURSDAY_8": 1440, "TEMPERATURE_THURSDAY_8": 5.01,
"ENDTIME_THURSDAY_9": 1440, "TEMPERATURE_THURSDAY_9": 5.01,
"ENDTIME_THURSDAY_10": 1440, "TEMPERATURE_THURSDAY_10": 5.01,
"ENDTIME_THURSDAY_11": 1440, "TEMPERATURE_THURSDAY_11": 5.01,
"ENDTIME_THURSDAY_12": 1440, "TEMPERATURE_THURSDAY_12": 5.01,
"ENDTIME_THURSDAY_13": 1440, "TEMPERATURE_THURSDAY_13": 5.01,


"ENDTIME_FRIDAY_1": 1440, "TEMPERATURE_FRIDAY_1": 18.01,
"ENDTIME_FRIDAY_2": 1440, "TEMPERATURE_FRIDAY_2": 5.01,
"ENDTIME_FRIDAY_3": 1440, "TEMPERATURE_FRIDAY_3": 5.01,
"ENDTIME_FRIDAY_4": 1440, "TEMPERATURE_FRIDAY_4": 5.01,
"ENDTIME_FRIDAY_5": 1440, "TEMPERATURE_FRIDAY_5": 5.01,
"ENDTIME_FRIDAY_6": 1440, "TEMPERATURE_FRIDAY_6": 5.01,
"ENDTIME_FRIDAY_7": 1440, "TEMPERATURE_FRIDAY_7": 5.01,
"ENDTIME_FRIDAY_8": 1440, "TEMPERATURE_FRIDAY_8": 5.01,
"ENDTIME_FRIDAY_9": 1440, "TEMPERATURE_FRIDAY_9": 5.01,
"ENDTIME_FRIDAY_10": 1440, "TEMPERATURE_FRIDAY_10": 5.01,
"ENDTIME_FRIDAY_11": 1440, "TEMPERATURE_FRIDAY_11": 5.01,
"ENDTIME_FRIDAY_12": 1440, "TEMPERATURE_FRIDAY_12": 5.01,
"ENDTIME_FRIDAY_13": 1440, "TEMPERATURE_FRIDAY_13": 5.01,


"ENDTIME_SATURDAY_1": 1440, "TEMPERATURE_SATURDAY_1": 18.01,
"ENDTIME_SATURDAY_2": 1440, "TEMPERATURE_SATURDAY_2": 5.01,
"ENDTIME_SATURDAY_3": 1440, "TEMPERATURE_SATURDAY_3": 5.01,
"ENDTIME_SATURDAY_4": 1440, "TEMPERATURE_SATURDAY_4": 5.01,
"ENDTIME_SATURDAY_5": 1440, "TEMPERATURE_SATURDAY_5": 5.01,
"ENDTIME_SATURDAY_6": 1440, "TEMPERATURE_SATURDAY_6": 5.01,
"ENDTIME_SATURDAY_7": 1440, "TEMPERATURE_SATURDAY_7": 5.01,
"ENDTIME_SATURDAY_8": 1440, "TEMPERATURE_SATURDAY_8": 5.01,
"ENDTIME_SATURDAY_9": 1440, "TEMPERATURE_SATURDAY_9": 5.01,
"ENDTIME_SATURDAY_10": 1440, "TEMPERATURE_SATURDAY_10": 5.01,
"ENDTIME_SATURDAY_11": 1440, "TEMPERATURE_SATURDAY_11": 5.01,
"ENDTIME_SATURDAY_12": 1440, "TEMPERATURE_SATURDAY_12": 5.01,
"ENDTIME_SATURDAY_13": 1440, "TEMPERATURE_SATURDAY_13": 5.01,


"ENDTIME_SUNDAY_1": 1440, "TEMPERATURE_SUNDAY_1": 18.01,
"ENDTIME_SUNDAY_2": 1440, "TEMPERATURE_SUNDAY_2": 5.01,
"ENDTIME_SUNDAY_3": 1440, "TEMPERATURE_SUNDAY_3": 5.01,
"ENDTIME_SUNDAY_4": 1440, "TEMPERATURE_SUNDAY_4": 5.01,
"ENDTIME_SUNDAY_5": 1440, "TEMPERATURE_SUNDAY_5": 5.01,
"ENDTIME_SUNDAY_6": 1440, "TEMPERATURE_SUNDAY_6": 5.01,
"ENDTIME_SUNDAY_7": 1440, "TEMPERATURE_SUNDAY_7": 5.01,
"ENDTIME_SUNDAY_8": 1440, "TEMPERATURE_SUNDAY_8": 5.01,
"ENDTIME_SUNDAY_9": 1440, "TEMPERATURE_SUNDAY_9": 5.01,
"ENDTIME_SUNDAY_10": 1440, "TEMPERATURE_SUNDAY_10": 5.01,
"ENDTIME_SUNDAY_11": 1440, "TEMPERATURE_SUNDAY_11": 5.01,
"ENDTIME_SUNDAY_12": 1440, "TEMPERATURE_SUNDAY_12": 5.01,
"ENDTIME_SUNDAY_13": 1440, "TEMPERATURE_SUNDAY_13": 5.01

}

Ich weiss, sind etwas viele Daten, aber man macht das ja normal nur einmal.

Die übertragung per RPC klappt auch, danach wird auch fleissig gesendet (WOR: yes) bis die 1% Grenze erreicht ist (Meldung “LOVF”). Soweit so gut. Unter “queues info” waren noch 9 Queues mit je 2 Paketen gelistet. Normalerweise sollte er diese doch dann nach 15 Minuten abarbeiten, oder? Das ist aber nicht passiert, erst nach ~930 Minuten wurden wieder einige Pakete übertragen (WOR: yes). Danach noch 4 Queues mit je 2 Paketen:

(Device)> peers select 1
Peer with id 1 and device type 0x300 selected.
For information about the peer's commands type: "help"
(Peer)> queues info
Number of Pending queues: 4
Queue 1:
  Number of packets: 2
  Packet 1 (Type: Packet): 170D0010FDAB8603BFF70014152015201520152015201520
  Packet 2 (Type: Message): Type: 02 Subtype: FFFFFFFF
Queue 2:
  Number of packets: 2
  Packet 1 (Type: Packet): 170E0010FDAB8603BFF70015152015201520152015201520
  Packet 2 (Type: Message): Type: 02 Subtype: FFFFFFFF
Queue 3:
  Number of packets: 2
  Packet 1 (Type: Packet): 170F0010FDAB8603BFF70016152015201520152015201520
  Packet 2 (Type: Message): Type: 02 Subtype: FFFFFFFF
Queue 4:
  Number of packets: 2
  Packet 1 (Type: Packet): 0F5B0003FDAB8603BFF7000F0D4C87C7
  Packet 2 (Type: Message): Type: 02 Subtype: FFFFFFFF

Ich vermute wenn ich noch warte ist er übermorgen fertig - und das für ein Thermostat. Ist das normal?

Ich kann natürlich meine Konfiguration kürzen, so dass pro Tag nur 5 Werte übertragen werden. Aber normalerweise sollte das doch schneller übertragen werden und keine 3 Tage dauern, oder?

Hier noch ein gekürztes Log

11/12/15 21:29:55.760 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0A000A0303BFF7FDAB8600
11/12/15 21:29:55.799 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B000202FDAB8603BFF70000
11/12/15 21:30:04.749 Info: Calling XML RPC method "system.listMethods" on server binary://192.168.2.116 and port 9123.
--
11/12/15 21:31:02.278 MAX packet received (My-MAX-CUL, RSSI: 0x2E): 17000400032E59000000001501FF49455130353432373736
11/12/15 21:31:02.386 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 0B590001FDAB86032E590000
11/12/15 21:31:03.452 MAX packet received (My-MAX-CUL, RSSI: 0x2E): 0E590202032E59FDAB860001192A28
--
11/12/15 21:31:03.698 Module MAX: Added peer 0x32E59.
11/12/15 21:31:03.701 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0F5A0003FDAB86032E59000F0C549FDF
11/12/15 21:31:03.703 Info: Calling XML RPC method "system.multicall" on server binary://192.168.2.116 and port 9123.
--
11/12/15 21:32:53.904 RPC Server (Port 2001): Info: Connection to client number 6402 closed (3).
11/12/15 21:32:53.911 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 0B000540FDAB8603BFF70128
11/12/15 21:32:53.948 Info: Calling XML RPC method "system.multicall" on server http://192.168.2.116 and port 2015.
--
11/12/15 21:32:54.982 Info: Connected to host 192.168.2.116 on port 2015. Client number is: 6409
11/12/15 21:32:55.011 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B000002FDAB8603BFF70000
11/12/15 21:32:55.014 Info: Calling XML RPC method "system.multicall" on server binary://192.168.2.116 and port 9123.
--
11/12/15 21:32:55.016 Info: Connected to host 192.168.2.116 on port 9123. Client number is: 6410
11/12/15 21:32:55.051 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B010540FDAB8603BFF70128
11/12/15 21:32:55.091 Info: Calling XML RPC method "system.multicall" on server http://192.168.2.116 and port 2015.
--
11/12/15 21:32:55.094 Info: Connected to host 192.168.2.116 on port 2015. Client number is: 6411
11/12/15 21:32:58.157 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 0B010540FDAB8603BFF70128
11/12/15 21:32:59.218 MAX packet received (My-MAX-CUL, RSSI: 0x50): 0E01020203BFF7FDAB860001180128
--
11/12/15 21:36:02.753 Info: Connected to host 192.168.2.116 on port 9123. Client number is: 6439
11/12/15 21:36:02.845 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19020010FDAB8603BFF70000580C486C59201520152015201520
11/12/15 21:36:03.917 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0E02020203BFF7FDAB860001180128
--
11/12/15 21:36:03.926 Info: Connected to host 192.168.2.116 on port 2015. Client number is: 6441
11/12/15 21:36:04.027 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19030010FDAB8603BFF70001580C486C59144920152015201520
11/12/15 21:36:05.099 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0E03020203BFF7FDAB86000118012A
11/12/15 21:36:05.201 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19040010FDAB8603BFF7000248CC591449201520152015201520
11/12/15 21:36:06.275 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0E04020203BFF7FDAB86000118012A
11/12/15 21:36:06.380 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19050010FDAB8603BFF7000348CC591449201520152015201520
11/12/15 21:36:07.455 MAX packet received (My-MAX-CUL, RSSI: 0x51): 0E05020203BFF7FDAB86000118012A
11/12/15 21:36:07.560 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19060010FDAB8603BFF7000448CC591449201520152015201520
11/12/15 21:36:07.804 RPC Server (Port 2001): Info: Connection to client number 6437 closed (3).
11/12/15 21:36:08.635 MAX packet received (My-MAX-CUL, RSSI: 0x50): 0E06020203BFF7FDAB86000118012A
11/12/15 21:36:08.740 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19070010FDAB8603BFF7000548CC591449201520152015201520
11/12/15 21:36:08.742 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF

11/12/15 21:36:11.895 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19070010FDAB8603BFF7000548CC591449201520152015201520
11/12/15 21:36:11.899 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF

11/12/15 21:36:14.898 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19070010FDAB8603BFF7000548CC591449201520152015201520
11/12/15 21:36:14.900 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF
--
11/13/15 13:06:18.160 MAX packet received (My-MAX-CUL, RSSI: 0x3F): 0C5904420F409A0000000028BC
11/13/15 13:07:47.542 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 19070010FDAB8603BFF7000548CC591449201520152015201520
11/13/15 13:07:50.685 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19070010FDAB8603BFF7000548CC591449201520152015201520
11/13/15 13:07:51.757 MAX packet received (My-MAX-CUL, RSSI: 0x35): 0E07020203BFF7FDAB860001180122
--
11/13/15 13:07:51.762 Info: Connected to host 192.168.2.116 on port 9123. Client number is: 663
11/13/15 13:07:51.864 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19080010FDAB8603BFF7000648CC592015201520152015201520
11/13/15 13:07:54.903 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 19080010FDAB8603BFF7000648CC592015201520152015201520
11/13/15 13:07:55.976 MAX packet received (My-MAX-CUL, RSSI: 0x35): 0E08020203BFF7FDAB860001180122
11/13/15 13:07:56.078 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 17090010FDAB8603BFF70010152015201520152015201520
11/13/15 13:07:57.151 MAX packet received (My-MAX-CUL, RSSI: 0x35): 0E09020203BFF7FDAB860001180124
11/13/15 13:07:57.256 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170A0010FDAB8603BFF70011152015201520152015201520
11/13/15 13:07:58.326 MAX packet received (My-MAX-CUL, RSSI: 0x35): 0E0A020203BFF7FDAB860001180124
11/13/15 13:07:58.428 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170B0010FDAB8603BFF70012152015201520152015201520
11/13/15 13:07:59.501 MAX packet received (My-MAX-CUL, RSSI: 0x36): 0E0B020203BFF7FDAB860001180124
11/13/15 13:07:59.606 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170C0010FDAB8603BFF70013152015201520152015201520
11/13/15 13:08:00.676 MAX packet received (My-MAX-CUL, RSSI: 0x36): 0E0C020203BFF7FDAB860001180124
11/13/15 13:08:00.779 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170D0010FDAB8603BFF70014152015201520152015201520
11/13/15 13:08:00.781 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF

11/13/15 13:08:03.928 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170D0010FDAB8603BFF70014152015201520152015201520
11/13/15 13:08:03.931 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF

11/13/15 13:08:06.930 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 170D0010FDAB8603BFF70014152015201520152015201520
11/13/15 13:08:06.932 Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF
--
11/13/15 13:13:36.732 Info: Connected to host 192.168.2.116 on port 9123. Client number is: 669
11/13/15 13:14:27.708 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: yes): 0F5C0003FDAB86032E59000F0D4C8ECE
11/13/15 13:14:28.774 MAX packet received (My-MAX-CUL, RSSI: 0x24): 0E5C0202032E59FDAB860001194A28

Grüße,
Patrick

#2

Hi,

also heute wurden alle noch ausstehenden Pakete übertragen. Die Dauer zwischen den Sendeversuchen lag jetzt bei genau 12 Stunden. Evtl. habe ich vorher Homegear zwischendurch neu gestartet, daher die längere Zeit.

Ich hab auch mal im Code nachgeforscht, scheinbar liegt es an der Wartezeit die für MAX-Geräte benutzt wird in der Homeagear-MAX/MAXPeer.cpp:

[code]void MAXPeer::worker()
{
if(!_centralFeatures || _disposing) return;
std::vector<uint32_t> positionsToDelete;
int64_t time;
try
{
time = BaseLib::HelperFunctions::getTime();
if(_rpcDevice)
{
serviceMessages->checkUnreach(_rpcDevice->timeout, getLastPacketReceived());
if(_rpcDevice->needsTime && (time - _lastTimePacket) > 43200000)
{
_lastTimePacket = time;
std::shared_ptr central = std::dynamic_pointer_cast(getCentral());
std::shared_ptr queue(new PacketQueue(_physicalInterface, PacketQueueType::PEER));
queue->peer = central->getPeer(_peerID);
queue->noSending = true;

			queue->push(central->getTimePacket(central->messageCounter()->at(0)++, _address, getRXModes() & HomegearDevice::ReceiveModes::wakeOnRadio));
			queue->push(central->getMessages()->find(DIRECTIONIN, 0x02, 0x02, std::vector<std::pair<uint32_t, int32_t>>()));
			queue->parameterName = "CURRENT_TIME";
			queue->channel = 0;
			pendingQueues->remove("CURRENT_TIME", 0);
			pendingQueues->push(queue);
			if((getRXModes() & HomegearDevice::ReceiveModes::always) || (getRXModes() & HomegearDevice::ReceiveModes::wakeOnRadio)) central->enqueuePendingQueues(_address);
		}
	}
	if(serviceMessages->getConfigPending())
	{
		if(!pendingQueues || pendingQueues->empty()) serviceMessages->setConfigPending(false);
		else if(_bl->settings.devLog() && (getRXModes() & HomegearDevice::ReceiveModes::wakeUp) && (_bl->hf.getTime() - serviceMessages->getConfigPendingSetTime()) > 360000)
		{
			GD::out.printWarning("Devlog warning: Configuration for peer with id " + std::to_string(_peerID) + " supporting wake up is pending since more than 6 minutes.");
			serviceMessages->resetConfigPendingSetTime();
		}
	}
}
[/code]

Die dort eingestellten 43200000 ms sind genau 12 Stunden und für das Wandthermostat ist “needsTime” auch gesetzt.
Warum sind das 12 h, ist dies korrekt?

Was mir auch noch aufgefallen ist, die Meldung “Warning: Too short packet received: LOVF” sollte eigentlich gar nicht kommen, sondern “Warning: CUL with id 1 reached 1% limit” - hier ist wohl ein Bug in CUL.cpp, der Vergleich mit “LOVF” muss vermutlich nach “LOVF\n” lauten (oder du vergleichst nur den Anfang). Das Newline wird auch bei “Warning: Too short packet received: LOVF” immer mit im Log ausgegeben (leere Zeile nach LOVF).

if(packetHex == "LOVF") _out.printWarning("Warning: CUL with id " + _settings->id + " reached 1% limit. You need to wait, before sending is allowed again.");
        		else if(packetHex == "Z") continue;
        		else _out.printWarning("Warning: Too short packet received: " + packetHex);
#3

Hallo Patrick,

das 1%-Limit bei den MAX!-Geräten ist echt nervig. Bisher war es so, dass du die Anlerntaste drücken musstest, damit die Queue weiter abgearbeitet wird. Dass es nach 12 Stunden weiterging, lag an dem Zeitpaket, welches die aktuelle Uhrzeit an die Geräte überträgt und einen erneuten Versuch der Konfigurationsübertragung startet. Ich habe Homegear jetzt aber so angepasst, dass die Konfiguration alle 15 bis 45 Minuten (zufällig) erneut versucht wird zu übertragen.

Richtig. Da fehlte in der Tat das “\n”. Danke dir! Ist jetzt korrigiert.

Beide Änderungen werde ich morgen pushen und sie sind dann im folgenden Nightly vorhanden.

Viele Grüße

Sathya

#4

Hallo ich habe evtl. ein ähnliches Problem… macht es Sinn die Problematik an dieser Stelle zu Posten oder besser ein neues Topic aufmachen?