Wenn ich folgendes Skript, relativ kurz hintereinander, zweimal ausführe, bleiben die HM-CC-RT-DN teilweise im Status UPDATE_PENDING. Das besonders problematische ist, das der Zustand nicht wegzubekommen ist. Die Gerätekommunikation ist dann auch gestört. Erst nach einem Neustart des homegear Dienstes fangen die Thermostate wieder an zu kommunizieren und arbeiten UPDATE_PENDING ab. Eine Ahnung warum das passiert? Sieht mir auch nach einem ähnlichen Problem aus wie hier: Problem mit HM-Dis-EP-WM55 und STICKY_UNREACH
#!/usr/bin/env php
<?php
include_once("Connect.php");
$Client->send("putParamset", array(1, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(4, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(5, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(8, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(11, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(19, 0, "MASTER", array("BUTTON_LOCK" => true)));
$Client->send("putParamset", array(22, 0, "MASTER", array("BUTTON_LOCK" => true)));
//BUTTON_LOCK: standard lock
//GLOBAL_BUTTON_LOCK: hard lock. you cant unlock it from device itself
//MODUS_BUTTON_LOCK: only mode and boost is locked
//#Ausführen mit: homegear -e rs HM-CC-RT-DN-lockButtons.php
?>
Log:
02/17/17 19:48:02.091 RPC Server (Port 2001): Info: Client number 34349 is calling RPC method: putParamset (1) Parameters:
(Integer) 22
(Integer) 0
(String) MASTER
(Struct length=1)
{
[BUTTON_LOCK]
{
(Boolean) 1
}
}
02/17/17 19:48:02.092 Module HomeMatic BidCoS: Info: Parameter BUTTON_LOCK of peer 22 and channel 0 was set to 0x01.
02/17/17 19:48:02.095 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.21.
02/17/17 19:48:02.099 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Sending (My-HM-MOD-RPI-PCB): 1030B001FD046D3F72A300050000000000
02/17/17 19:48:02.283 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -41 dBm): 0A6880023F729DFD046D00
02/17/17 19:48:02.908 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -44 dBm): 0A3080023F72A3FD046D00
02/17/17 19:48:02.910 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.21.
02/17/17 19:48:03.002 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Sending (My-HM-MOD-RPI-PCB): 0D31A001FD046D3F72A300080F01
02/17/17 19:48:03.176 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -44 dBm): 0A3180023F72A3FD046D00
02/17/17 19:48:03.270 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Sending (My-HM-MOD-RPI-PCB): 0B32A001FD046D3F72A30006
02/17/17 19:48:03.444 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -44 dBm): 0A3280023F72A3FD046D00
02/17/17 19:48:03.444 Module HomeMatic BidCoS: Info: Queue 211 is empty and there are no pending queues.
02/17/17 19:48:03.701 RPC client: Info: Calling RPC method "system.multicall" on server 192.168.178.21.
02/17/17 19:48:03.729 Info: Script with id 24 finished with exit code 0
02/17/17 19:48:03.729 RPC Server (Port 2001): Info: Connection to client number 34349 closed (3).
02/17/17 19:48:04.074 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
02/17/17 19:48:04.074 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 19). Retrying...
02/17/17 19:48:04.075 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Sending (My-HM-MOD-RPI-PCB): 106DB001FD046D221D4000050000000000
02/17/17 19:48:04.374 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
02/17/17 19:48:04.375 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 11). Retrying...