2016-03-15 19:29:56,968 [main] WARN org.pidome.server.PiDomeServerBoot - Running server with security manager disabled. This is the case as long the server is in alpha state. 2016-03-15 19:29:57,189 [main] WARN org.pidome.server.PiDomeServerBoot - There is no default locale present in the config file, will default to: en_US 2016-03-15 19:29:57,213 [main] INFO org.pidome.server.PiDomeServerBoot - Starting server with build: 0.1-SNAPSHOT-2015-12-28.611 on platform: Linux (arm) 2016-03-15 19:29:57,594 [main] INFO com.zaxxer.hikari.HikariDataSource - DBConnectionPool_PiDomeServer - is starting. 2016-03-15 19:30:03,709 [main] INFO org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999 2016-03-15 19:30:04,068 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Initializing RPC 2016-03-15 19:30:04,735 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PackageService 2016-03-15 19:30:04,964 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DashboardService 2016-03-15 19:30:04,966 [main] ERROR org.pidome.server.system.rpc.PidomeJSONRPC - RPC namespace 'JSONService' has been misconfigured! 2016-03-15 19:30:04,968 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: JSONService 2016-03-15 19:30:05,060 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DataModifierService 2016-03-15 19:30:05,301 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: LocationService 2016-03-15 19:30:05,308 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MessengerService 2016-03-15 19:30:05,390 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: WeatherService 2016-03-15 19:30:05,456 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: RemotesService 2016-03-15 19:30:05,611 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: CategoryService 2016-03-15 19:30:05,705 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: HardwareService 2016-03-15 19:30:05,869 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: AccessControllerService 2016-03-15 19:30:06,119 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: ClientService 2016-03-15 19:30:06,317 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserService 2016-03-15 19:30:06,363 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PluginService 2016-03-15 19:30:06,872 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DeviceService 2016-03-15 19:30:07,057 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MediaService 2016-03-15 19:30:07,152 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: EventService 2016-03-15 19:30:07,265 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserStatusService 2016-03-15 19:30:07,310 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UtilityMeasurementService 2016-03-15 19:30:07,331 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PlatformService 2016-03-15 19:30:07,466 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: TriggerService 2016-03-15 19:30:07,623 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: AutomationRulesService 2016-03-15 19:30:07,698 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: SystemService 2016-03-15 19:30:07,787 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: ScenesService 2016-03-15 19:30:07,874 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DayPartService 2016-03-15 19:30:07,977 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MacroService 2016-03-15 19:30:08,088 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PresenceService 2016-03-15 19:30:08,141 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DevicePluginService 2016-03-15 19:30:08,155 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done Initializing RPC 2016-03-15 19:30:08,172 [main] INFO org.pidome.server.system.extras.SystemExtras - Initializing system extras 2016-03-15 19:30:08,175 [main] INFO org.pidome.server.system.extras.SystemExtras - LED notifications setting: false 2016-03-15 19:30:08,177 [main] INFO org.pidome.server.system.extras.DataNotificationLeds - Led notification pins are disabled. If you want to enable this got to http://pidome.org on how to enable this. 2016-03-15 19:30:08,179 [main] INFO org.pidome.server.system.extras.SystemExtras - Done initializing extras 2016-03-15 19:30:08,246 [main] INFO org.pidome.server.system.network.Network - Autodiscovery of network interface addresses 2016-03-15 19:30:08,360 [main] INFO org.pidome.server.services.provider.CertGen - Generating certificate(s), please wait...... 2016-03-15 19:30:18,329 [main] INFO org.pidome.server.services.provider.CertGen - Certificate(s) generated. 2016-03-15 19:30:18,336 [main] INFO org.pidome.server.system.network.Network - Network interface loaded 2016-03-15 19:30:18,869 [main] INFO org.pidome.server.services.clients.websockets.WebHttpWSService - Websocket service started: 192.168.178.34 - 8088 2016-03-15 19:30:19,463 [main] INFO org.pidome.server.services.clients.websockets.WebHttpWSService - Websocket ssl service started: 192.168.178.34 - 8089 2016-03-15 19:30:21,088 [HTTP service provider] INFO org.pidome.server.services.clients.http.DefaultHttpServer - HTTP Webservice started at ip: raspberrypi.fritz.box/192.168.178.34, on port: 8080, max threads: 100 2016-03-15 19:30:21,610 [main] INFO org.pidome.server.services.accesscontrollers.AccesControllersService - Loading access controller devices wrappers 2016-03-15 19:30:22,749 [WEBCLIENT] ERROR org.pidome.server.services.clients.http.HTTPClientHandler - Not authorized at 192.168.178.26, rewriting request (POST /login.xhtml HTTP/1.1) 2016-03-15 19:30:23,183 [WEBCLIENT] WARN org.pidome.server.system.webservice.webclient.Webclient_login - Client logged in: admin via 192.168.178.26 2016-03-15 19:30:26,288 [main] INFO org.pidome.server.system.hardware.Hardware - Hardware discovery started 2016-03-15 19:30:26,463 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Server information layer' hardware driver using saved configuration. 2016-03-15 19:30:26,470 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'ServerDevicePeripheral' for loading Server information layer. 2016-03-15 19:30:26,830 [main] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Server information layer 2016-03-15 19:30:29,755 [HTTPS Service provider] INFO org.pidome.server.services.clients.http.DefaultHttpsServer - HTTPS Webservice started at ip: raspberrypi.fritz.box/192.168.178.34, on port: 8443, max threads: 100 2016-03-15 19:30:30,681 [main] INFO com.zaxxer.hikari.HikariDataSource - DBConnectionPool_DEVICE_1 - is starting. 2016-03-15 19:30:30,780 [main] INFO org.pidome.server.system.hardware.devices.Devices - Device: The PiDome Server self: Rasp server has been loaded 2016-03-15 19:30:31,067 [main] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver NativeServerDriver on Server information layer on port {Internally used device map} is ready for use 2016-03-15 19:30:31,084 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB 2016-03-15 19:30:31,091 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO 2016-03-15 19:30:31,119 [User-defined-serials-discovery] INFO org.pidome.server.system.hardware.Hardware - Started user defined serial devices discovery 2016-03-15 19:30:31,108 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C 2016-03-15 19:30:31,130 [main] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2016-03-15 19:30:31,154 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry GPIO I2C' hardware driver using saved configuration. 2016-03-15 19:30:31,166 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOI2C' for loading Raspberry GPIO I2C. 2016-03-15 19:30:31,222 [main] INFO org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 15-03-2016 19:30 2016-03-15 19:30:31,588 [main] INFO org.pidome.server.system.presence.PresenceService - Set presence to Home at 15-03-2016 19:30 2016-03-15 19:30:31,744 [User-defined-serials-discovery] INFO org.pidome.server.system.hardware.Hardware - Done user defined serial devices discovery 2016-03-15 19:30:31,788 [main] INFO org.pidome.server.services.clients.socketservice.SocketService - Client display terminal server has started 2016-03-15 19:30:31,783 [Socket] INFO org.pidome.server.services.clients.socketservice.SocketService - Active, waiting for connections on ip: raspberrypi.fritz.box/192.168.178.34 and port: 11000 2016-03-15 19:30:31,805 [main] INFO org.pidome.server.services.clients.socketservice.SocketService - Client display terminal SSL server has started 2016-03-15 19:30:32,519 [SocketSSL] INFO org.pidome.server.services.clients.socketservice.SocketService - Active, waiting for connections on ip: raspberrypi.fritz.box/192.168.178.34 and port: 11001 2016-03-15 19:30:32,677 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Data modifiers plugin service 2016-03-15 19:30:32,788 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service 2016-03-15 19:30:32,811 [I2C-discovery] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Raspberry GPIO I2C 2016-03-15 19:30:32,848 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service 2016-03-15 19:30:32,977 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service 2016-03-15 19:30:32,998 [I2C-discovery] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver NativeDefaultI2CDriver on Raspberry GPIO I2C on port {Auto discovery by driver} is ready for use 2016-03-15 19:30:33,026 [Serial-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry Pi GPIO Serial' hardware driver using saved configuration. 2016-03-15 19:30:33,032 [Serial-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOSerial' for loading Raspberry Pi GPIO Serial. 2016-03-15 19:30:33,029 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on I2C 2016-03-15 19:30:33,138 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service 2016-03-15 19:30:33,356 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service 2016-03-15 19:30:33,388 [PluginService::Start:Devices plugin service] INFO org.pidome.server.services.plugins.PluginService - Starting 'MQTT Server hook' (PiDome MQTT Broker) with the 'Devices plugin service' plugin service 2016-03-15 19:30:33,350 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on Serial GPIO 2016-03-15 19:30:33,419 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Weather plugins service 2016-03-15 19:30:34,274 [main] INFO org.pidome.server.services.network.BroadcastService - Broadcast message: 'DOMCONTROL:192.168.178.34-SCREEN:DOMCONTROL:11000-SCREENSSL:DOMCONTROL:11001-WS:DOMCONTROL:8088' 2016-03-15 19:30:34,314 [SERVICE:BroadcastServer] INFO org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds 2016-03-15 19:30:34,872 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Emulator for: PiDome MQTT Broker' hardware driver using saved configuration. 2016-03-15 19:30:34,875 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'HwPluginEmu' for loading Emulator for: PiDome MQTT Broker. 2016-03-15 19:30:34,975 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Emulator for: PiDome MQTT Broker 2016-03-15 19:30:35,045 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting plugin links: MQTT Server hook 2016-03-15 19:30:35,047 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting device instance link 2016-03-15 19:30:35,095 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Assigning the next installed devices to emulator plugin 'MQTT Server hook': {} 2016-03-15 19:30:35,144 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver PidomeMQTTBrokerDriver on Emulator for: PiDome MQTT Broker on port e0cc4a43-22b4-4b12-a491-a0afd57a0629 is ready for use 2016-03-15 19:30:36,428 [Thread-32] INFO org.pidome.server.services.automations.AutomationRules - Loaded rule: CPU usage 2016-03-15 19:30:37,661 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 19:30:38,038 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Dell, Dell USB Keyboard' device drivers going to load, please wait... 2016-03-15 19:30:38,071 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Dell, Dell USB Keyboard' hardware driver using saved configuration. 2016-03-15 19:30:38,114 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '413c' and pid '2010' for loading Dell, Dell USB Keyboard. 2016-03-15 19:30:38,117 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 19:30:38,120 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Dell, Dell USB Keyboard'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 19:30:38,953 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 19:30:38,956 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Dell, Dell USB Keyboard' device drivers going to load, please wait... 2016-03-15 19:30:38,958 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Dell, Dell USB Keyboard' hardware driver using saved configuration. 2016-03-15 19:30:38,960 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '413c' and pid '2010' for loading Dell, Dell USB Keyboard. 2016-03-15 19:30:38,973 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 19:30:38,975 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Dell, Dell USB Keyboard'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 19:30:39,175 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 19:30:39,194 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)' device drivers going to load, please wait... 2016-03-15 19:30:39,196 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)' hardware driver using saved configuration. 2016-03-15 19:30:39,199 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '045e' and pid '0039' for loading Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM). 2016-03-15 19:30:39,253 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 19:30:39,255 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 19:30:43,841 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2016-03-15 19:30:43,843 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on USB 2016-03-15 19:30:43,875 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2016-03-15 19:30:44,673 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - Server binded 2016-03-15 19:30:44,717 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - WebSocket is disabled 2016-03-15 19:30:44,722 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - SSL is disabled 2016-03-15 19:30:44,739 [PluginService::Start:Devices plugin service] INFO org.pidome.server.services.plugins.PluginService - Started plugin: MQTT Server hook 2016-03-15 19:30:45,748 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:30:45,802 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Connected client ID with clean session true 2016-03-15 19:30:45,822 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Create persistent session for clientID MyMQTT 2016-03-15 19:30:45,963 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:31:01,074 [TriggerTimeRun::19:31] INFO org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Evening 2016-03-15 19:31:01,117 [TriggerTimeRun::19:31] INFO org.pidome.server.system.dayparts.DayPartsService - Set daypart to Evening at 15-03-2016 19:31 2016-03-15 19:34:29,494 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:34:29,512 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Connected client ID with clean session true 2016-03-15 19:34:29,513 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Create persistent session for clientID MQTT_FX_Client 2016-03-15 19:34:57,385 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:35:05,596 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - replying with UnsubAck to MSG ID 2 2016-03-15 19:35:25,479 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:36:13,702 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:36:30,957 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - replying with UnsubAck to MSG ID 5 2016-03-15 19:36:41,622 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:36:47,973 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - replying with UnsubAck to MSG ID 7 2016-03-15 19:38:11,764 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - replying with UnsubAck to MSG ID 8 2016-03-15 19:38:16,788 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic <#> with QoS 0 - MOST_ONE 2016-03-15 19:39:13,843 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - replying with UnsubAck to MSG ID 10 2016-03-15 19:39:18,155 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:40:41,945 [WEBCLIENT] WARN org.pidome.server.services.clients.http.HTTPClientHandler - 404 error: File: '/desktop/theme/default/style.css' not found - org.pidome.server.system.webservice.Webservice404Exception: File: '/desktop/theme/default/style.css' not found 2016-03-15 19:41:50,689 [WEBCLIENT] INFO org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Log level modified to: DEBUG 2016-03-15 19:41:50,717 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data=true, success=true, message=} 2016-03-15 19:41:57,878 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 19:41:57,892 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 19:42:00,119 [TriggerTimeRun::19:42] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 19:42 in trigger event 'Set Night' 2016-03-15 19:42:00,133 [TriggerTimeRun::19:42] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 19:42 in trigger event 'Set Morning' 2016-03-15 19:42:00,136 [TriggerTimeRun::19:42] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 19:42 in trigger event 'Set Afternoon' 2016-03-15 19:42:00,138 [TriggerTimeRun::19:42] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 19:42 in trigger event 'Set Evening' 2016-03-15 19:42:00,348 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 64) 2016-03-15 19:42:00,362 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 19:42:00,365 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:00,367 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:00,369 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 19:42:00,370 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 22.3 2016-03-15 19:42:00,383 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 19:42:00,389 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.3> 2016-03-15 19:42:00,422 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:00,431 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Broker republishing to client topic qos , active true 2016-03-15 19:42:00,443 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - sendPublish invoked clientId on topic QoS MOST_ONE retained false messageID 1 2016-03-15 19:42:00,445 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - send publish message to on topic 2016-03-15 19:42:00,446 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.3> 2016-03-15 19:42:00,449 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - clientIDs are {MyMQTT=ConnectionDescriptor{m_clientID=MyMQTT, m_cleanSession=true}, MQTT_FX_Client=ConnectionDescriptor{m_clientID=MQTT_FX_Client, m_cleanSession=true}} 2016-03-15 19:42:00,451 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Session for clientId MQTT_FX_Client is org.dna.mqtt.moquette.server.netty.NettyChannel@60387a 2016-03-15 19:42:00,471 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - disruptorPublish publishing event on output org.dna.mqtt.moquette.messaging.spi.impl.events.OutputMessagingEvent@13a241a 2016-03-15 19:42:00,695 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 19:42:00,698 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 19:42:01,410 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 19:42:10,641 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - Header read error: Socket closed java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:203) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:223) ~[?:1.8.0_60] at org.pidome.server.services.clients.http.HTTPClientHandler.clientInputStreamListener(HTTPClientHandler.java:143) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] at org.pidome.server.services.clients.http.HTTPClientHandler.run(HTTPClientHandler.java:123) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] 2016-03-15 19:42:12,061 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 64) 2016-03-15 19:42:12,072 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 19:42:12,074 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:12,076 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:12,078 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 19:42:12,080 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 22.1 2016-03-15 19:42:12,081 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 19:42:12,094 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.1> 2016-03-15 19:42:12,098 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:12,112 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Broker republishing to client topic qos , active true 2016-03-15 19:42:12,114 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - sendPublish invoked clientId on topic QoS MOST_ONE retained false messageID 1 2016-03-15 19:42:12,115 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - send publish message to on topic 2016-03-15 19:42:12,117 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.1> 2016-03-15 19:42:12,119 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - clientIDs are {MyMQTT=ConnectionDescriptor{m_clientID=MyMQTT, m_cleanSession=true}, MQTT_FX_Client=ConnectionDescriptor{m_clientID=MQTT_FX_Client, m_cleanSession=true}} 2016-03-15 19:42:12,120 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Session for clientId MQTT_FX_Client is org.dna.mqtt.moquette.server.netty.NettyChannel@60387a 2016-03-15 19:42:12,132 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - disruptorPublish publishing event on output org.dna.mqtt.moquette.messaging.spi.impl.events.OutputMessagingEvent@112e2b9 2016-03-15 19:42:16,430 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 19:42:18,153 [nioEventLoopGroup-3-2] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 19:42:23,776 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 64) 2016-03-15 19:42:23,782 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 19:42:23,784 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:23,794 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:23,796 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 19:42:23,798 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 22.0 2016-03-15 19:42:23,799 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 19:42:23,832 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.0> 2016-03-15 19:42:23,837 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:23,840 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Broker republishing to client topic qos , active true 2016-03-15 19:42:23,853 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - sendPublish invoked clientId on topic QoS MOST_ONE retained false messageID 1 2016-03-15 19:42:23,855 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - send publish message to on topic 2016-03-15 19:42:23,857 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <22.0> 2016-03-15 19:42:23,859 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - clientIDs are {MyMQTT=ConnectionDescriptor{m_clientID=MyMQTT, m_cleanSession=true}, MQTT_FX_Client=ConnectionDescriptor{m_clientID=MQTT_FX_Client, m_cleanSession=true}} 2016-03-15 19:42:23,861 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Session for clientId MQTT_FX_Client is org.dna.mqtt.moquette.server.netty.NettyChannel@60387a 2016-03-15 19:42:23,873 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - disruptorPublish publishing event on output org.dna.mqtt.moquette.messaging.spi.impl.events.OutputMessagingEvent@2861b8 2016-03-15 19:42:27,797 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat:39.5;uptime:786.76;cpuusage:4.93;memusage:13.03;diskspace:9229.41; - procheat:39.5;uptime:786.76;cpuusage:4.93;memusage:13.03;diskspace:9229.41; 2016-03-15 19:42:27,816 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 39.5 2016-03-15 19:42:27,832 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device org.pidome.driver.device.pidomeServerDevice with group values, control: procheat, containing 39.5 2016-03-15 19:42:27,834 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /hooks/devices/1/values/procheat 2016-03-15 19:42:27,836 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <39.5> 2016-03-15 19:42:27,853 [pool-3-thread-1] DEBUG org.pidome.server.services.automations.rule.logic.compare.AutomationCompareList - Rule compare list result with check type AND: false 2016-03-15 19:42:27,857 [pool-3-thread-1] DEBUG org.pidome.server.services.automations.rule.logic.compare.AutomationCompareList - Rule compare list result with check type AND: false 2016-03-15 19:42:27,857 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:27,869 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /Home/Floor unknown/Location unknown/device/Rasp server/Device values/Pi temperature 2016-03-15 19:42:27,877 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 19:42:27,877 [pool-3-thread-1] DEBUG org.pidome.server.services.automations.rule.logic.compare.AutomationCompareList - Rule compare list result with check type AND: false 2016-03-15 19:42:27,885 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 19:42:27,871 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <39.5> 2016-03-15 19:42:27,887 [pool-3-thread-1] DEBUG org.pidome.server.services.automations.rule.logic.compare.AutomationCompareList - Rule compare list result with check type AND: false 2016-03-15 19:42:27,922 [pool-3-thread-1] DEBUG org.pidome.server.services.automations.rule.logic.compare.AutomationCompareList - Rule compare list result with check type AND: true 2016-03-15 19:42:27,952 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 4.93 2016-03-15 19:42:27,952 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:27,976 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device org.pidome.driver.device.pidomeServerDevice with group values, control: uptime, containing 0 days 0:13:6 2016-03-15 19:42:27,977 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /hooks/devices/1/values/uptime 2016-03-15 19:42:27,979 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <0 days 0:13:6> 2016-03-15 19:42:27,994 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,002 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /Home/Floor unknown/Location unknown/device/Rasp server/Device values/Uptime 2016-03-15 19:42:28,004 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <0 days 0:13:6> 2016-03-15 19:42:28,008 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,023 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device org.pidome.driver.device.pidomeServerDevice with group values, control: cpuusage, containing 4.93 2016-03-15 19:42:28,032 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /hooks/devices/1/values/cpuusage 2016-03-15 19:42:28,033 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <4.93> 2016-03-15 19:42:28,056 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,063 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /Home/Floor unknown/Location unknown/device/Rasp server/Device values/CPU load 2016-03-15 19:42:28,074 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <4.93> 2016-03-15 19:42:28,078 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,093 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 13.03 2016-03-15 19:42:28,133 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device org.pidome.driver.device.pidomeServerDevice with group values, control: memusage, containing 13.03 2016-03-15 19:42:28,135 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /hooks/devices/1/values/memusage 2016-03-15 19:42:28,137 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <13.03> 2016-03-15 19:42:28,164 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,167 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /Home/Floor unknown/Location unknown/device/Rasp server/Device values/Memory usage 2016-03-15 19:42:28,169 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <13.03> 2016-03-15 19:42:28,187 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,217 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 9229.41 2016-03-15 19:42:28,232 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device org.pidome.driver.device.pidomeServerDevice with group values, control: diskspace, containing 9229.41 2016-03-15 19:42:28,252 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /hooks/devices/1/values/diskspace 2016-03-15 19:42:28,254 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <9229.41> 2016-03-15 19:42:28,258 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:28,278 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic /Home/Floor unknown/Location unknown/device/Rasp server/Device values/Disk space 2016-03-15 19:42:28,298 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <9229.41> 2016-03-15 19:42:28,314 [pool-5-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:30,695 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 19:42:30,702 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 19:42:31,450 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 19:42:35,491 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 64) 2016-03-15 19:42:35,502 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 19:42:35,504 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:35,506 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:35,523 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 19:42:35,524 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 21.9 2016-03-15 19:42:35,526 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 19:42:35,528 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.9> 2016-03-15 19:42:35,559 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:35,572 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Broker republishing to client topic qos , active true 2016-03-15 19:42:35,574 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - sendPublish invoked clientId on topic QoS MOST_ONE retained false messageID 1 2016-03-15 19:42:35,576 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - send publish message to on topic 2016-03-15 19:42:35,577 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.9> 2016-03-15 19:42:35,580 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - clientIDs are {MyMQTT=ConnectionDescriptor{m_clientID=MyMQTT, m_cleanSession=true}, MQTT_FX_Client=ConnectionDescriptor{m_clientID=MQTT_FX_Client, m_cleanSession=true}} 2016-03-15 19:42:35,592 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Session for clientId MQTT_FX_Client is org.dna.mqtt.moquette.server.netty.NettyChannel@60387a 2016-03-15 19:42:35,594 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - disruptorPublish publishing event on output org.dna.mqtt.moquette.messaging.spi.impl.events.OutputMessagingEvent@152222f 2016-03-15 19:42:46,466 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 19:42:47,208 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 64) 2016-03-15 19:42:47,223 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 19:42:47,225 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:47,227 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 19:42:47,229 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 19:42:47,230 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 21.8 2016-03-15 19:42:47,243 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 19:42:47,245 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.8> 2016-03-15 19:42:47,250 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] mygateway1-out 1 0 1 0 + 30 + 0 1 0 0[filter:mygateway1-out/30/0/1/0/0, cliID: MQTT_FX_Client, qos: MOST_ONE, active: true] # # 2016-03-15 19:42:47,264 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Broker republishing to client topic qos , active true 2016-03-15 19:42:47,266 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - sendPublish invoked clientId on topic QoS MOST_ONE retained false messageID 1 2016-03-15 19:42:47,267 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - send publish message to on topic 2016-03-15 19:42:47,269 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.8> 2016-03-15 19:42:47,282 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - clientIDs are {MyMQTT=ConnectionDescriptor{m_clientID=MyMQTT, m_cleanSession=true}, MQTT_FX_Client=ConnectionDescriptor{m_clientID=MQTT_FX_Client, m_cleanSession=true}} 2016-03-15 19:42:47,284 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Session for clientId MQTT_FX_Client is org.dna.mqtt.moquette.server.netty.NettyChannel@60387a 2016-03-15 19:42:47,285 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - disruptorPublish publishing event on output org.dna.mqtt.moquette.messaging.spi.impl.events.OutputMessagingEvent@112dfeb 2016-03-15 19:42:50,668 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: GET /jsonrpc.json?rpc={"jsonrpc":%20"2.0",%20"method":%20"SystemService.setServerSetting",%20"id":"SystemService.setServerSetting",%20"params":%20{"setting":"setdebug",%20"values":%20{"value":false}}} HTTP/1.1 2016-03-15 19:42:50,682 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Accept: */* 2016-03-15 19:42:50,684 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: X-Requested-With: XMLHttpRequest 2016-03-15 19:42:50,687 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Referer: http://192.168.178.34:8080/desktop/settings.html 2016-03-15 19:42:50,689 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Accept-Language: nl-NL 2016-03-15 19:42:50,691 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Accept-Encoding: gzip, deflate 2016-03-15 19:42:50,704 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko 2016-03-15 19:42:50,706 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Host: 192.168.178.34:8080 2016-03-15 19:42:50,709 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: If-Modified-Since: Sun, 13 Mar 2016 20:36:58 GMT 2016-03-15 19:42:50,743 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Connection: Keep-Alive 2016-03-15 19:42:50,745 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: Cookie: key=7f4dc7ed-2dc6-4b7f-b968-b6cc9a6c968e 2016-03-15 19:42:50,747 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - 192.168.178.26 - 1458067370661: 2016-03-15 19:42:50,784 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - JSON String to parse: {"jsonrpc": "2.0", "method": "SystemService.setServerSetting", "id":"SystemService.setServerSetting", "params": {"setting":"setdebug", "values": {"value":false}}} 2016-03-15 19:42:50,787 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Parsed JSON Object: {method=SystemService.setServerSetting, id=SystemService.setServerSetting, jsonrpc=2.0, params={values={value=false}, setting=setdebug}} 2016-03-15 19:42:50,788 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Set request id: SystemService.setServerSetting 2016-03-15 19:42:50,790 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Searching named parameter set for setServerSetting in SystemService 2016-03-15 19:42:50,822 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Found param key: setting 2016-03-15 19:42:50,824 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Found param key: values 2016-03-15 19:42:50,825 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - searching for setServerSetting in SystemService 2016-03-15 19:42:50,827 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Declared params for setServerSetting : [class java.lang.String, class java.lang.Object] 2016-03-15 19:42:50,829 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Passed in params for 'setServerSetting': [setdebug, {value=false}] 2016-03-15 19:42:50,870 [WEBCLIENT] INFO org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Log level modified to: INFO 2016-03-15 19:43:39,667 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:43:39,708 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Disconnected client with clean session true 2016-03-15 19:43:42,303 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:43:42,312 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Connected client ID with clean session true 2016-03-15 19:43:42,314 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Create persistent session for clientID MQTT_FX_Client 2016-03-15 19:46:27,183 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 19:58:14,993 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:58:15,023 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 19:58:15,025 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Connected client ID with clean session true 2016-03-15 19:58:15,027 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Create persistent session for clientID MyMQTT 2016-03-15 19:58:15,029 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Lost connection with client 2016-03-15 19:58:15,052 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 20:12:04,508 [Thread-35] INFO org.pidome.server.PiDomeServerBoot - Server shutdown instantiated 2016-03-15 20:12:04,547 [Thread-35] INFO org.pidome.server.services.clients.socketservice.SocketService - Stopped, clients can not be served 2016-03-15 20:12:04,548 [Thread-35] INFO org.pidome.server.services.clients.socketservice.SocketService - Client display terminal (ssl) server has stopped 2016-03-15 20:12:04,582 [Thread-35] INFO org.pidome.server.services.clients.websockets.WebHttpWSService - Websocket service stopped 2016-03-15 20:12:04,586 [Thread-35] INFO org.pidome.server.system.hardware.devices.Devices - Stopping devices for driver org.pidome.drivers.mqtt.pidomeMQTTBrokerDriver 2016-03-15 20:12:57,687 [main] WARN org.pidome.server.PiDomeServerBoot - Running server with security manager disabled. This is the case as long the server is in alpha state. 2016-03-15 20:12:57,735 [main] WARN org.pidome.server.PiDomeServerBoot - There is no default locale present in the config file, will default to: en_US 2016-03-15 20:12:57,738 [main] INFO org.pidome.server.PiDomeServerBoot - Starting server with build: 0.1-SNAPSHOT-2015-12-28.611 on platform: Linux (arm) 2016-03-15 20:12:58,121 [main] INFO com.zaxxer.hikari.HikariDataSource - DBConnectionPool_PiDomeServer - is starting. 2016-03-15 20:13:04,241 [main] INFO org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999 2016-03-15 20:13:04,596 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Initializing RPC 2016-03-15 20:13:05,262 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PackageService 2016-03-15 20:13:05,490 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DashboardService 2016-03-15 20:13:05,493 [main] ERROR org.pidome.server.system.rpc.PidomeJSONRPC - RPC namespace 'JSONService' has been misconfigured! 2016-03-15 20:13:05,495 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: JSONService 2016-03-15 20:13:05,587 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DataModifierService 2016-03-15 20:13:05,827 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: LocationService 2016-03-15 20:13:05,834 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MessengerService 2016-03-15 20:13:05,915 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: WeatherService 2016-03-15 20:13:05,981 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: RemotesService 2016-03-15 20:13:06,136 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: CategoryService 2016-03-15 20:13:06,228 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: HardwareService 2016-03-15 20:13:06,317 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: AccessControllerService 2016-03-15 20:13:06,647 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: ClientService 2016-03-15 20:13:06,845 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserService 2016-03-15 20:13:06,890 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PluginService 2016-03-15 20:13:07,400 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DeviceService 2016-03-15 20:13:07,586 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MediaService 2016-03-15 20:13:07,686 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: EventService 2016-03-15 20:13:07,777 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserStatusService 2016-03-15 20:13:07,841 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: UtilityMeasurementService 2016-03-15 20:13:07,861 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PlatformService 2016-03-15 20:13:07,996 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: TriggerService 2016-03-15 20:13:08,086 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: AutomationRulesService 2016-03-15 20:13:08,217 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: SystemService 2016-03-15 20:13:08,310 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: ScenesService 2016-03-15 20:13:08,398 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DayPartService 2016-03-15 20:13:08,501 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: MacroService 2016-03-15 20:13:08,611 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: PresenceService 2016-03-15 20:13:08,661 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done initializing RPC namespace: DevicePluginService 2016-03-15 20:13:08,673 [main] INFO org.pidome.server.system.rpc.PidomeJSONRPC - Done Initializing RPC 2016-03-15 20:13:08,693 [main] INFO org.pidome.server.system.extras.SystemExtras - Initializing system extras 2016-03-15 20:13:08,695 [main] INFO org.pidome.server.system.extras.SystemExtras - LED notifications setting: false 2016-03-15 20:13:08,698 [main] INFO org.pidome.server.system.extras.DataNotificationLeds - Led notification pins are disabled. If you want to enable this got to http://pidome.org on how to enable this. 2016-03-15 20:13:08,699 [main] INFO org.pidome.server.system.extras.SystemExtras - Done initializing extras 2016-03-15 20:13:08,750 [main] INFO org.pidome.server.system.network.Network - Autodiscovery of network interface addresses 2016-03-15 20:13:08,821 [main] INFO org.pidome.server.services.provider.CertGen - Generating certificate(s), please wait...... 2016-03-15 20:13:19,878 [main] INFO org.pidome.server.services.provider.CertGen - Certificate(s) generated. 2016-03-15 20:13:19,884 [main] INFO org.pidome.server.system.network.Network - Network interface loaded 2016-03-15 20:13:20,391 [main] INFO org.pidome.server.services.clients.websockets.WebHttpWSService - Websocket service started: 192.168.178.34 - 8088 2016-03-15 20:13:20,986 [main] INFO org.pidome.server.services.clients.websockets.WebHttpWSService - Websocket ssl service started: 192.168.178.34 - 8089 2016-03-15 20:13:22,275 [HTTP service provider] INFO org.pidome.server.services.clients.http.DefaultHttpServer - HTTP Webservice started at ip: raspberrypi.fritz.box/192.168.178.34, on port: 8080, max threads: 100 2016-03-15 20:13:23,194 [main] INFO org.pidome.server.services.accesscontrollers.AccesControllersService - Loading access controller devices wrappers 2016-03-15 20:13:26,269 [main] INFO org.pidome.server.system.hardware.Hardware - Hardware discovery started 2016-03-15 20:13:26,374 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Server information layer' hardware driver using saved configuration. 2016-03-15 20:13:26,381 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'ServerDevicePeripheral' for loading Server information layer. 2016-03-15 20:13:26,593 [main] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Server information layer 2016-03-15 20:13:28,846 [HTTPS Service provider] INFO org.pidome.server.services.clients.http.DefaultHttpsServer - HTTPS Webservice started at ip: raspberrypi.fritz.box/192.168.178.34, on port: 8443, max threads: 100 2016-03-15 20:13:29,182 [main] INFO com.zaxxer.hikari.HikariDataSource - DBConnectionPool_DEVICE_1 - is starting. 2016-03-15 20:13:29,273 [main] INFO org.pidome.server.system.hardware.devices.Devices - Device: The PiDome Server self: Rasp server has been loaded 2016-03-15 20:13:29,446 [main] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver NativeServerDriver on Server information layer on port {Internally used device map} is ready for use 2016-03-15 20:13:29,453 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB 2016-03-15 20:13:29,468 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C 2016-03-15 20:13:29,464 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO 2016-03-15 20:13:29,506 [main] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2016-03-15 20:13:29,514 [User-defined-serials-discovery] INFO org.pidome.server.system.hardware.Hardware - Started user defined serial devices discovery 2016-03-15 20:13:29,520 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry GPIO I2C' hardware driver using saved configuration. 2016-03-15 20:13:29,523 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOI2C' for loading Raspberry GPIO I2C. 2016-03-15 20:13:29,665 [main] INFO org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 15-03-2016 20:13 2016-03-15 20:13:30,007 [User-defined-serials-discovery] INFO org.pidome.server.system.hardware.Hardware - Done user defined serial devices discovery 2016-03-15 20:13:30,096 [main] INFO org.pidome.server.system.presence.PresenceService - Set presence to Home at 15-03-2016 20:13 2016-03-15 20:13:30,276 [main] INFO org.pidome.server.services.clients.socketservice.SocketService - Client display terminal server has started 2016-03-15 20:13:30,280 [Socket] INFO org.pidome.server.services.clients.socketservice.SocketService - Active, waiting for connections on ip: raspberrypi.fritz.box/192.168.178.34 and port: 11000 2016-03-15 20:13:30,283 [main] INFO org.pidome.server.services.clients.socketservice.SocketService - Client display terminal SSL server has started 2016-03-15 20:13:30,345 [I2C-discovery] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Raspberry GPIO I2C 2016-03-15 20:13:30,418 [SocketSSL] INFO org.pidome.server.services.clients.socketservice.SocketService - Active, waiting for connections on ip: raspberrypi.fritz.box/192.168.178.34 and port: 11001 2016-03-15 20:13:30,479 [I2C-discovery] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver NativeDefaultI2CDriver on Raspberry GPIO I2C on port {Auto discovery by driver} is ready for use 2016-03-15 20:13:30,483 [Serial-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry Pi GPIO Serial' hardware driver using saved configuration. 2016-03-15 20:13:30,489 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on I2C 2016-03-15 20:13:30,493 [Serial-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOSerial' for loading Raspberry Pi GPIO Serial. 2016-03-15 20:13:30,552 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Data modifiers plugin service 2016-03-15 20:13:30,648 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service 2016-03-15 20:13:30,714 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on Serial GPIO 2016-03-15 20:13:30,719 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service 2016-03-15 20:13:30,844 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service 2016-03-15 20:13:30,914 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service 2016-03-15 20:13:30,957 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service 2016-03-15 20:13:30,990 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Weather plugins service 2016-03-15 20:13:30,996 [PluginService::Start:Devices plugin service] INFO org.pidome.server.services.plugins.PluginService - Starting 'MQTT Server hook' (PiDome MQTT Broker) with the 'Devices plugin service' plugin service 2016-03-15 20:13:31,760 [main] INFO org.pidome.server.services.network.BroadcastService - Broadcast message: 'DOMCONTROL:192.168.178.34-SCREEN:DOMCONTROL:11000-SCREENSSL:DOMCONTROL:11001-WS:DOMCONTROL:8088' 2016-03-15 20:13:31,806 [SERVICE:BroadcastServer] INFO org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds 2016-03-15 20:13:32,336 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Emulator for: PiDome MQTT Broker' hardware driver using saved configuration. 2016-03-15 20:13:32,338 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'HwPluginEmu' for loading Emulator for: PiDome MQTT Broker. 2016-03-15 20:13:32,392 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Emulator for: PiDome MQTT Broker 2016-03-15 20:13:32,476 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting plugin links: MQTT Server hook 2016-03-15 20:13:32,478 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting device instance link 2016-03-15 20:13:32,519 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Assigning the next installed devices to emulator plugin 'MQTT Server hook': {} 2016-03-15 20:13:32,546 [PluginService::Start:Devices plugin service] INFO org.pidome.server.system.hardware.drivers.Drivers - Driver PidomeMQTTBrokerDriver on Emulator for: PiDome MQTT Broker on port 93ecea3f-4908-482b-96cd-0bcd55dcc65d is ready for use 2016-03-15 20:13:33,451 [Thread-24] INFO org.pidome.server.services.automations.AutomationRules - Loaded rule: CPU usage 2016-03-15 20:13:33,932 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 20:13:34,012 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Dell, Dell USB Keyboard' device drivers going to load, please wait... 2016-03-15 20:13:34,025 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Dell, Dell USB Keyboard' hardware driver using saved configuration. 2016-03-15 20:13:34,028 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '413c' and pid '2010' for loading Dell, Dell USB Keyboard. 2016-03-15 20:13:34,031 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 20:13:34,038 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Dell, Dell USB Keyboard'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 20:13:34,194 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 20:13:34,237 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Dell, Dell USB Keyboard' device drivers going to load, please wait... 2016-03-15 20:13:34,238 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Dell, Dell USB Keyboard' hardware driver using saved configuration. 2016-03-15 20:13:34,241 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '413c' and pid '2010' for loading Dell, Dell USB Keyboard. 2016-03-15 20:13:34,272 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 20:13:34,274 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Dell, Dell USB Keyboard'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 20:13:34,475 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB device added, please wait 2016-03-15 20:13:34,496 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)' device drivers going to load, please wait... 2016-03-15 20:13:34,497 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)' hardware driver using saved configuration. 2016-03-15 20:13:34,500 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Using vid '045e' and pid '0039' for loading Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM). 2016-03-15 20:13:34,502 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - No config or vendor and product id based driver found, fall back on subsystem 'TYPE_USB, HID' with user settings 2016-03-15 20:13:34,521 [USB-discovery] WARN org.pidome.server.system.hardware.peripherals.Peripherals - Hardware driver not found for 'Microsoft, Microsoft 5-Button Mouse with IntelliEye(TM)'. Not loaded, Device not compatible with PiDome: No packages found which should have the driver for system: TYPE_USB and sub system: HID 2016-03-15 20:13:36,230 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2016-03-15 20:13:36,235 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Done peripherals discovery on USB 2016-03-15 20:13:36,269 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2016-03-15 20:13:37,859 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - Server binded 2016-03-15 20:13:37,886 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - WebSocket is disabled 2016-03-15 20:13:37,889 [PluginService::Start:Devices plugin service] INFO org.dna.mqtt.moquette.server.netty.NettyAcceptor - SSL is disabled 2016-03-15 20:13:37,891 [PluginService::Start:Devices plugin service] INFO org.pidome.server.services.plugins.PluginService - Started plugin: MQTT Server hook 2016-03-15 20:13:39,372 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - cleaning old saved subscriptions for client 2016-03-15 20:13:39,414 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Connected client ID with clean session true 2016-03-15 20:13:39,415 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Create persistent session for clientID MyMQTT 2016-03-15 20:13:39,540 [pool-9-thread-1] INFO org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscribed to topic with QoS 0 - MOST_ONE 2016-03-15 20:14:00,595 [TriggerTimeRun::20:14] INFO org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Evening 2016-03-15 20:14:00,612 [TriggerTimeRun::20:14] INFO org.pidome.server.system.dayparts.DayPartsService - Set daypart to Evening at 15-03-2016 20:14 2016-03-15 20:14:14,706 [WEBCLIENT] ERROR org.pidome.server.services.clients.http.HTTPClientHandler - Not authorized at 192.168.178.26, rewriting request (GET / HTTP/1.1) 2016-03-15 20:14:26,182 [WEBCLIENT] ERROR org.pidome.server.services.clients.http.HTTPClientHandler - Not authorized at 192.168.178.26, rewriting request (POST /login.xhtml HTTP/1.1) 2016-03-15 20:14:26,291 [WEBCLIENT] WARN org.pidome.server.system.webservice.webclient.Webclient_login - Client logged in: admin via 192.168.178.26 2016-03-15 20:14:35,741 [WEBCLIENT] WARN org.pidome.server.services.clients.http.HTTPClientHandler - 404 error: File: '/desktop/theme/default/style.css' not found - org.pidome.server.system.webservice.Webservice404Exception: File: '/desktop/theme/default/style.css' not found 2016-03-15 20:14:38,311 [WEBCLIENT] INFO org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Log level modified to: DEBUG 2016-03-15 20:14:38,339 [WEBCLIENT] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Response data: {data=true, success=true, message=} 2016-03-15 20:14:39,639 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 20:14:49,194 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 432) 2016-03-15 20:14:49,204 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 20:14:49,207 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 20:14:49,213 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 20:14:49,216 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 20:14:49,217 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 21.0 2016-03-15 20:14:49,220 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 20:14:49,238 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.0> 2016-03-15 20:14:49,260 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] 2016-03-15 20:14:50,741 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - Header read error: Socket closed java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:203) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:223) ~[?:1.8.0_60] at org.pidome.server.services.clients.http.HTTPClientHandler.clientInputStreamListener(HTTPClientHandler.java:143) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] at org.pidome.server.services.clients.http.HTTPClientHandler.run(HTTPClientHandler.java:123) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] 2016-03-15 20:14:54,658 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 20:14:58,269 [WEBCLIENT] DEBUG org.pidome.server.services.clients.http.HTTPClientHandler - Header read error: Socket closed java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:203) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_60] at java.net.SocketInputStream.read(SocketInputStream.java:223) ~[?:1.8.0_60] at org.pidome.server.services.clients.http.HTTPClientHandler.clientInputStreamListener(HTTPClientHandler.java:143) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] at org.pidome.server.services.clients.http.HTTPClientHandler.run(HTTPClientHandler.java:123) [pidome-server.jar:0.1-SNAPSHOT-2015-12-28.611] 2016-03-15 20:14:58,413 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 20:14:58,424 [Hikari housekeeper (pool DBConnectionPool_PiDomeServer)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_PiDomeServer stats (total=10, active=0, idle=10, waiting=0) 2016-03-15 20:14:59,187 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - Before cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 20:14:59,194 [Hikari housekeeper (pool DBConnectionPool_DEVICE_1)] DEBUG com.zaxxer.hikari.pool.HikariPool - After cleanup pool DBConnectionPool_DEVICE_1 stats (total=5, active=0, idle=5, waiting=0) 2016-03-15 20:15:00,580 [TriggerTimeRun::20:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 20:15 in trigger event 'Set Night' 2016-03-15 20:15:00,594 [TriggerTimeRun::20:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 20:15 in trigger event 'Set Morning' 2016-03-15 20:15:00,597 [TriggerTimeRun::20:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 20:15 in trigger event 'Set Afternoon' 2016-03-15 20:15:00,600 [TriggerTimeRun::20:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 20:15 in trigger event 'Set Evening' 2016-03-15 20:15:00,912 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 416) 2016-03-15 20:15:00,924 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 20:15:00,926 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 20:15:00,930 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 20:15:00,932 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 20:15:00,945 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 21.1 2016-03-15 20:15:00,947 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 20:15:00,949 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.1> 2016-03-15 20:15:00,952 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true] 2016-03-15 20:15:09,676 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PINGREQ 2016-03-15 20:15:12,631 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.parser.netty.PublishDecoder - decode invoked with buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 33, cap: 400) 2016-03-15 20:15:12,640 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.server.netty.NettyMQTTHandler - Received a message of type PUBLISH 2016-03-15 20:15:12,642 [nioEventLoopGroup-3-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - disruptorPublish publishing event ProtocolEvent wrapping PUBLISH 2016-03-15 20:15:12,652 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.SimpleMessaging - onEvent processing messaging event from input ringbuffer ProtocolEvent wrapping PUBLISH 2016-03-15 20:15:12,655 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - Publish recieved from clientID on topic with QoS MOST_ONE 2016-03-15 20:15:12,657 [pool-9-thread-1] DEBUG org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Broker handling: MyMQTT, mygateway1-out/30/0/1/0/0, 21.0 2016-03-15 20:15:12,659 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - publish2Subscribers republishing to existing subscribers that matches the topic mygateway1-out/30/0/1/0/0 2016-03-15 20:15:12,660 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - content <21.0> 2016-03-15 20:15:12,675 [pool-9-thread-1] DEBUG org.dna.mqtt.moquette.messaging.spi.impl.ProtocolProcessor - subscription tree mygateway1-in + + + + +[filter:mygateway1-in/+/+/+/+/+, cliID: MyMQTT, qos: MOST_ONE, active: true]