(void)
02/05/19 09:03:34.390 Node-BLUE Server: Info: Client number 1 is calling RPC method: nodeEvent
(String) 878a0866.043208
(String) statusBottom/878a0866.043208
(Struct length=1)
{
[text]
{
(String) Next: 06:58:00 (on)
}
}
02/05/19 09:03:34.390 Node-BLUE Server: Response:
(void)
02/05/19 09:03:34.390 Node-BLUE Server: Info: Client number 1 is calling RPC method: nodeEvent
(String) e03d4cd9.20499
(String) statusBottom/e03d4cd9.20499
(Struct length=1)
{
[text]
{
(String) Next: 07:00:00 (on)
}
}
02/05/19 09:03:34.391 Node-BLUE Server: Response:
(void)
02/05/19 09:03:34.476 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.43:55730 accepted. Client number: 3396
02/05/19 09:03:34.477 RPC Server (Port 2001): Info: RPC server client id for client number 3396 is: 3316
02/05/19 09:03:34.478 RPC Server (Port 2001): Listening for incoming packets from client number 3396.
02/05/19 09:03:34.478 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E310A557365725F4167656E743A20484D2D584D4C5250432D436C69656E740A486F73743A2052617370692D48470A436F6E6E656374696F6E3A204B6565702D416C6976650A436F6E74656E742D547970653A20746578742F786D6C0A436F6E74656E742D4C656E6774683A203330320A0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2269736F2D383835392D31223F3E0A3C6D6574686F6443616C6C3E0A3C6D6574686F644E616D653E67657456616C75653C2F6D6574686F644E616D653E0A3C706172616D733E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E333C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E313C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C737472696E673E53544154453C2F737472696E673E0A20203C2F76616C75653E0A203C2F706172616D3E0A3C2F706172616D733E0A3C2F6D6574686F6443616C6C3E0A0A
02/05/19 09:03:34.479 RPC Server (Port 2001): Info: Client number 3396 is calling RPC method: getValue (1) Parameters:
(Integer) 3
(Integer) 1
(String) STATE
02/05/19 09:03:34.479 RPC Server (Port 2001): Response:
(Boolean) 0
02/05/19 09:03:34.479 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Type: text/xml
Content-Length: 123
0
02/05/19 09:03:34.503 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E310A557365725F4167656E743A20484D2D584D4C5250432D436C69656E740A486F73743A2052617370692D48470A436F6E6E656374696F6E3A204B6565702D416C6976650A436F6E74656E742D547970653A20746578742F786D6C0A436F6E74656E742D4C656E6774683A203330320A0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2269736F2D383835392D31223F3E0A3C6D6574686F6443616C6C3E0A3C6D6574686F644E616D653E67657456616C75653C2F6D6574686F644E616D653E0A3C706172616D733E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E343C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E313C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C737472696E673E53544154453C2F737472696E673E0A20203C2F76616C75653E0A203C2F706172616D3E0A3C2F706172616D733E0A3C2F6D6574686F6443616C6C3E0A0A
02/05/19 09:03:34.504 RPC Server (Port 2001): Error in file RPC/RpcServer.cpp line 1731 in function void Homegear::Rpc::RpcServer::readClient(std::shared_ptr): basic_string::_M_create
02/05/19 09:03:34.509 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.43:55732 accepted. Client number: 3397
02/05/19 09:03:34.509 RPC Server (Port 2001): Info: RPC server client id for client number 3397 is: 3317
02/05/19 09:03:34.510 RPC Server (Port 2001): Listening for incoming packets from client number 3397.
02/05/19 09:03:34.511 RPC Server (Port 2001): Debug: Packet received: 504F5354202F20485454502F312E310A557365725F4167656E743A20484D2D584D4C5250432D436C69656E740A486F73743A2052617370692D48470A436F6E6E656374696F6E3A204B6565702D416C6976650A436F6E74656E742D547970653A20746578742F786D6C0A436F6E74656E742D4C656E6774683A203330320A0A3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D2269736F2D383835392D31223F3E0A3C6D6574686F6443616C6C3E0A3C6D6574686F644E616D653E67657456616C75653C2F6D6574686F644E616D653E0A3C706172616D733E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E343C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C696E743E313C2F696E743E0A20203C2F76616C75653E0A203C2F706172616D3E0A203C706172616D3E0A20203C76616C75653E0A2020203C737472696E673E53544154453C2F737472696E673E0A20203C2F76616C75653E0A203C2F706172616D3E0A3C2F706172616D733E0A3C2F6D6574686F6443616C6C3E0A0A
02/05/19 09:03:34.511 RPC Server (Port 2001): Info: Client number 3397 is calling RPC method: getValue (1) Parameters:
(Integer) 4
(Integer) 1
(String) STATE
02/05/19 09:03:34.511 RPC Server (Port 2001): Response:
(Boolean) 0
02/05/19 09:03:34.511 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Type: text/xml
Content-Length: 123
0
02/05/19 09:03:34.523 Node-BLUE Server: Info: Client number 0 is calling RPC method: nodeEvent
(String) f22711e3.c602d
(String) statusBottom/f22711e3.c602d
(Struct length=1)
{
[text]
{
(String) Next: 02/09/19 (on)
}