2014-09-06 08:46:19,723 [main] INFO org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999 2014-09-06 08:46:25,338 [main] INFO org.pidome.server.system.extras.SystemExtras - Initializing system extras 2014-09-06 08:46:25,351 [main] INFO org.pidome.server.system.extras.SystemExtras - LED notifications setting: false 2014-09-06 08:46:25,354 [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. 2014-09-06 08:46:25,356 [main] INFO org.pidome.server.system.extras.SystemExtras - Done initializing extras 2014-09-06 08:46:25,872 [main] ERROR err - SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". 2014-09-06 08:46:25,879 [main] ERROR err - SLF4J: Defaulting to no-operation (NOP) logger implementation 2014-09-06 08:46:25,881 [main] ERROR err - SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 2014-09-06 08:46:29,407 [main] INFO org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 06-09-2014 08:46 2014-09-06 08:46:30,088 [main] INFO org.pidome.server.system.presence.PresenceService - Set presence to Home at 06-09-2014 08:46 2014-09-06 08:46:37,348 [main] INFO org.pidome.server.services.provider.CertGen - Generating certificate(s), please wait...... 2014-09-06 08:46:48,992 [main] INFO org.pidome.server.services.provider.CertGen - Certificate(s) generated. 2014-09-06 08:46:49,010 [main] INFO org.pidome.server.system.network.Network - Network interface loaded 2014-09-06 08:46:49,671 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket ssl service started: 10.0.0.13 - 8089 2014-09-06 08:46:49,757 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service 2014-09-06 08:46:49,857 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service 2014-09-06 08:46:49,981 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal server has started 2014-09-06 08:46:50,029 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal SSL server has started 2014-09-06 08:46:50,078 [HTTP service provider] INFO org.pidome.server.system.webservice.DefaultHttpServer - HTTP Webservice started at ip: 10.0.0.13/10.0.0.13, on port: 8080, max threads: 50 2014-09-06 08:46:50,090 [Socket] INFO org.pidome.server.services.socketservice.SocketService - Active, waiting for connections on ip: 10.0.0.13/10.0.0.13 and port: 11000 2014-09-06 08:46:50,237 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket service started: 10.0.0.13 - 8088 2014-09-06 08:46:51,035 [main] INFO org.pidome.server.system.hardware.Hardware - Hardware discovery started 2014-09-06 08:46:51,895 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Server information layer ready for use 2014-09-06 08:46:58,057 [main] INFO org.pidome.server.system.hardware.devices.Devices - Device: The PiDome Server self has been loaded 2014-09-06 08:46:58,097 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB 2014-09-06 08:47:05,298 [HTTPS Service provider] INFO org.pidome.server.system.webservice.DefaultHttpsServer - HTTPS Webservice started at ip: 10.0.0.13/10.0.0.13, on port: 8443, max threads: 50 2014-09-06 08:47:05,327 [SocketSSL] INFO org.pidome.server.services.socketservice.SocketService - Active, waiting for connections on ip: 10.0.0.13/10.0.0.13 and port: 11001 2014-09-06 08:47:08,041 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 08:47:08,067 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO 2014-09-06 08:47:08,117 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 08:47:08,368 [Serial-discovery] ERROR org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral driver PidomeNativeSerial can not be started: Temporary disabled 2014-09-06 08:47:08,411 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C 2014-09-06 08:47:09,194 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Raspberry GPIO I2C ready for use 2014-09-06 08:47:09,335 [main] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 08:47:09,347 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 08:47:09,376 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service 2014-09-06 08:47:09,593 [main] INFO org.pidome.server.services.network.BroadcastService - Broadcast message: 'DOMCONTROL:10.0.0.13-SCREEN:DOMCONTROL:11000-SCREENSSL:DOMCONTROL:11001' 2014-09-06 08:47:09,646 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service 2014-09-06 08:47:09,653 [SERVICE:BroadcastServer] INFO org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds 2014-09-06 08:47:09,681 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service 2014-09-06 08:48:00,296 [TriggerTimeRun::08:48] INFO org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Morning 2014-09-06 08:48:00,335 [TriggerTimeRun::08:48] INFO org.pidome.server.system.dayparts.DayPartsService - Set daypart to Morning at 06-09-2014 08:48 2014-09-06 08:49:17,466 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 08:49:43,410 [Thread-48] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC ready for use 2014-09-06 08:49:43,413 [Thread-48] INFO org.pidome.server.system.hardware.drivers.Drivers - Something went wrong width the hardware: MEthod does not support NID to request driver. 2014-09-06 08:49:44,424 [Thread-48] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 08:49:57,003 [Thread-59] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Method handling error org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157) ~[PiDome_Server.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0] at java.lang.reflect.Method.invoke(Method.java:483) ~[?:1.8.0] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109) [PiDome_Server.jar:?] 2014-09-06 08:49:57,356 [Thread-59] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Constructed method exception message: {data={trace=org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral\\n at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157)\\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\\n at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\\n at java.lang.reflect.Method.invoke(Method.java:483)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230)\\n at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55)\\n at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109)\\n, message=Unknown port used for peripheral}, jsonrpc=2.0, error={code=-32000, message=Server error}} 2014-09-06 08:50:21,902 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removing 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device, please wait, removing... 2014-09-06 08:50:21,924 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.devices.Devices - Stopping devices for driver org.pidome.driver.driver.nativeMySensorsDriver14 2014-09-06 08:50:21,998 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral stopped. 2014-09-06 08:50:22,025 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removed 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' 2014-09-06 08:50:43,866 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 08:50:43,975 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC ready for use 2014-09-06 08:50:43,999 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.drivers.Drivers - Something went wrong width the hardware: MEthod does not support NID to request driver. 2014-09-06 08:50:44,736 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 08:50:44,738 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Loaded and started Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC from saved configuration with: NativeMySensorsDriver14 2014-09-06 08:51:08,470 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.4 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 08:51:08,474 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.0 in device Study, error: Group 'S_MOTION' does not exist 2014-09-06 08:51:19,266 [Thread-86] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Method handling error org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157) ~[PiDome_Server.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0] at java.lang.reflect.Method.invoke(Method.java:483) ~[?:1.8.0] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109) [PiDome_Server.jar:?] 2014-09-06 08:51:19,294 [Thread-86] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Constructed method exception message: {data={trace=org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral\\n at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157)\\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\\n at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\\n at java.lang.reflect.Method.invoke(Method.java:483)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230)\\n at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55)\\n at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109)\\n, message=Unknown port used for peripheral}, jsonrpc=2.0, error={code=-32000, message=Server error}} 2014-09-06 08:51:31,244 [Thread-74] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: Index: 20, Size: 20 (0;0;3;0;9;read: 20-20-0 s=0,c=1,t=0,pt=7,l=5:15.3 20;0;1;0;0;15.3 ) 2014-09-06 08:53:42,702 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.4 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 08:53:42,710 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.1 in device Study, error: Group 'S_MOTION' does not exist 2014-09-06 08:54:47,452 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.0 in device Study, error: Group 'S_MOTION' does not exist 2014-09-06 08:55:20,153 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.1 in device Study, error: Group 'S_MOTION' does not exist 2014-09-06 08:56:58,187 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.5 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 08:57:30,887 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.4 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 08:59:10,054 [Thread-74] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.5 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 09:07:19,533 [main] TRACE org.pidome.server.system.config.SystemConfig - Libraries file paths: [file:/home/pi/pidome-server/packages/system/dep/pi4j-core.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-service.jar, file:/home/pi/pidome-server/packages/system/dep/fusesource-mqtt-client-1.7.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-gpio-extension.jar, file:/home/pi/pidome-server/packages/system/dep/jssc.jar, file:/home/pi/pidome-server/packages/system/dep/log4j-api-2.0.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-device.jar, file:/home/pi/pidome-server/packages/system/dep/native/librxtxSerial.so, file:/home/pi/pidome-server/packages/system/dep/log4j-core-2.0.jar, file:/home/pi/pidome-server/packages/system/dep/json-simple-1.1.1.jar, file:/home/pi/pidome-server/packages/system/dep/hidapi-1.1.jar, file:/home/pi/pidome-server/packages/system/PiDome_Server_Connector_library.jar] 2014-09-06 09:07:23,229 [main] INFO org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999 2014-09-06 09:07:27,403 [main] INFO org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999 2014-09-06 09:07:30,105 [main] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - JSON wrapper set. 2014-09-06 09:07:30,216 [main] INFO org.pidome.server.system.extras.SystemExtras - Initializing system extras 2014-09-06 09:07:30,229 [main] INFO org.pidome.server.system.extras.SystemExtras - LED notifications setting: false 2014-09-06 09:07:30,233 [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. 2014-09-06 09:07:30,249 [main] INFO org.pidome.server.system.extras.SystemExtras - Done initializing extras 2014-09-06 09:07:30,432 [main] DEBUG org.pidome.server.system.db.DB - Loading all databases 2014-09-06 09:07:30,901 [main] ERROR err - SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". 2014-09-06 09:07:30,904 [main] ERROR err - SLF4J: Defaulting to no-operation (NOP) logger implementation 2014-09-06 09:07:30,907 [main] ERROR err - SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 2014-09-06 09:07:34,333 [main] INFO org.pidome.server.system.extras.SystemExtras - Initializing system extras 2014-09-06 09:07:34,336 [main] INFO org.pidome.server.system.extras.SystemExtras - LED notifications setting: false 2014-09-06 09:07:34,349 [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. 2014-09-06 09:07:34,352 [main] INFO org.pidome.server.system.extras.SystemExtras - Done initializing extras 2014-09-06 09:07:34,956 [main] ERROR err - SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". 2014-09-06 09:07:34,971 [main] ERROR err - SLF4J: Defaulting to no-operation (NOP) logger implementation 2014-09-06 09:07:34,974 [main] ERROR err - SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 2014-09-06 09:07:35,011 [main] DEBUG org.pidome.server.system.db.DB - Database driver loaded and config and pooling set 2014-09-06 09:07:35,141 [main] DEBUG org.pidome.server.system.userstatus.UserStatusService - Loading user status: 1, name Awake, description: User status awake 2014-09-06 09:07:35,178 [main] DEBUG org.pidome.server.system.userstatus.UserStatusService - Loading user status: 2, name Sleeping, description: User status sleeping 2014-09-06 09:07:35,181 [main] DEBUG org.pidome.server.system.userstatus.UserStatusService - Loading user status: 3, name Unknown/Away, description: When the user is away and status is unknown 2014-09-06 09:07:35,270 [main] INFO org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 06-09-2014 09:07 2014-09-06 09:07:35,562 [main] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"UserStatusService.setUserStatus","params": {"name":"Awake","id":1} } 2014-09-06 09:07:36,001 [main] DEBUG org.pidome.server.system.dayparts.DayPartsService - Loading day part: 1, name Morning, description: The morning day part 2014-09-06 09:07:36,020 [main] DEBUG org.pidome.server.system.dayparts.DayPartsService - Loading day part: 2, name Afternoon, description: The Afternoon day part 2014-09-06 09:07:36,023 [main] DEBUG org.pidome.server.system.dayparts.DayPartsService - Loading day part: 3, name Evening, description: The evening day part 2014-09-06 09:07:36,026 [main] DEBUG org.pidome.server.system.dayparts.DayPartsService - Loading day part: 4, name Night, description: The night day part 2014-09-06 09:07:36,132 [main] DEBUG org.pidome.server.system.presence.PresenceService - Loading presence: 1, name Home, description: At Home 2014-09-06 09:07:36,154 [main] DEBUG org.pidome.server.system.presence.PresenceService - Loading presence: 2, name Away, description: Not at Home 2014-09-06 09:07:36,158 [main] DEBUG org.pidome.server.system.presence.PresenceService - Loading presence: 4, name Vacation, description: At Vacation 2014-09-06 09:07:36,171 [main] DEBUG org.pidome.server.system.presence.PresenceService - Loading presence: 5, name At Work, description: At Work. 2014-09-06 09:07:36,177 [main] INFO org.pidome.server.system.presence.PresenceService - Set presence to Home at 06-09-2014 09:07 2014-09-06 09:07:36,213 [main] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"PresenceService.setPresence","params": {"name":"Home","id":1} } 2014-09-06 09:07:38,833 [main] DEBUG org.pidome.server.services.macros.MacroDB - Found 4 macros 2014-09-06 09:07:41,437 [main] INFO org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 06-09-2014 09:07 2014-09-06 09:07:42,173 [main] DEBUG org.pidome.server.system.packages.Packages - Instance request 2014-09-06 09:07:42,176 [main] DEBUG org.pidome.server.system.packages.Packages - Instance initializing 2014-09-06 09:07:42,235 [main] INFO org.pidome.server.system.presence.PresenceService - Set presence to Home at 06-09-2014 09:07 2014-09-06 09:07:42,588 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/PiDome.Peripherals/PiDome_Peripherals.jar added to loader for main package 'PiDome.Peripherals' 2014-09-06 09:07:42,601 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: PiDome.Peripherals 2014-09-06 09:07:42,665 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/PiDome.Drivers/PiDome_Drivers.jar added to loader for main package 'PiDome.Drivers' 2014-09-06 09:07:42,668 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: PiDome.Drivers 2014-09-06 09:07:42,751 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/PiDome.Devices/PiDome_Devices.jar added to loader for main package 'PiDome.Devices' 2014-09-06 09:07:42,753 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: PiDome.Devices 2014-09-06 09:07:42,834 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.Plugins/PiDome_Plugins.jar added to loader for main package 'Pidome.Plugins' 2014-09-06 09:07:42,836 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: Pidome.Plugins 2014-09-06 09:07:42,914 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.MySensors/Pidome.MySensors.jar added to loader for main package 'Pidome.MySensors' 2014-09-06 09:07:42,917 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: Pidome.MySensors 2014-09-06 09:07:43,025 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.PhilipsHue/lib/huesdkresources.jar added to loader for main package 'Pidome.PhilipsHue' 2014-09-06 09:07:43,028 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.PhilipsHue/lib/huelocalsdk.jar added to loader for main package 'Pidome.PhilipsHue' 2014-09-06 09:07:43,060 [main] TRACE org.pidome.server.system.packages.PackageLibraryLoader - Library paths for this package: [file:/home/pi/pidome-server/packages/system/dep/pi4j-core.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-service.jar, file:/home/pi/pidome-server/packages/system/dep/fusesource-mqtt-client-1.7.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-gpio-extension.jar, file:/home/pi/pidome-server/packages/system/dep/jssc.jar, file:/home/pi/pidome-server/packages/system/dep/log4j-api-2.0.jar, file:/home/pi/pidome-server/packages/system/dep/pi4j-device.jar, file:/home/pi/pidome-server/packages/system/dep/native/librxtxSerial.so, file:/home/pi/pidome-server/packages/system/dep/log4j-core-2.0.jar, file:/home/pi/pidome-server/packages/system/dep/json-simple-1.1.1.jar, file:/home/pi/pidome-server/packages/system/dep/hidapi-1.1.jar, file:/home/pi/pidome-server/packages/system/PiDome_Server_Connector_library.jar, file:/home/pi/pidome-server/packages/user/Pidome.PhilipsHue/lib/huesdkresources.jar, file:/home/pi/pidome-server/packages/user/Pidome.PhilipsHue/lib/huelocalsdk.jar] 2014-09-06 09:07:43,065 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.PhilipsHue/Pidome.PhilipsHue.jar added to loader for main package 'Pidome.PhilipsHue' 2014-09-06 09:07:43,081 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: Pidome.PhilipsHue 2014-09-06 09:07:43,130 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/Pidome.Kodi/Pidome.Kodi.jar added to loader for main package 'Pidome.Kodi' 2014-09-06 09:07:43,132 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: Pidome.Kodi 2014-09-06 09:07:43,194 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/PiDome.KlikAanKlikUitArduino/PiDome.KlikAanKlikUitArduino.jar added to loader for main package 'PiDome.KlikAanKlikUitArduino' 2014-09-06 09:07:43,197 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: PiDome.KlikAanKlikUitArduino 2014-09-06 09:07:43,272 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - file:/home/pi/pidome-server/packages/user/PiDome.I2C/PiDome.I2C.jar added to loader for main package 'PiDome.I2C' 2014-09-06 09:07:43,275 [main] DEBUG org.pidome.server.system.packages.PackageLibraryLoader - Loaded package: PiDome.I2C 2014-09-06 09:07:44,587 [main] DEBUG org.pidome.server.system.hardware.Hardware - Added listener: org.pidome.server.system.hardware.devices.Devices 2014-09-06 09:07:44,601 [main] DEBUG org.pidome.server.system.hardware.peripherals.Peripherals - Added eventlistener: org.pidome.server.system.hardware.devices.Devices 2014-09-06 09:07:44,628 [main] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Added listener: org.pidome.server.system.hardware.devices.Devices 2014-09-06 09:07:45,290 [main] DEBUG org.pidome.server.system.network.Network - Autodiscovery of network interface addresses 2014-09-06 09:07:45,373 [main] DEBUG org.pidome.server.system.network.Network - Found ip address/10.0.0.13/24 [/10.0.0.255] 2014-09-06 09:07:45,375 [main] DEBUG org.pidome.server.system.network.Network - Found broadcast address/10.0.0.255 2014-09-06 09:07:45,392 [main] DEBUG org.pidome.server.system.network.Network - Found subnet /255.255.255.0 2014-09-06 09:07:45,396 [main] DEBUG org.pidome.server.system.network.Network - Event: AVAILABLE 2014-09-06 09:07:45,452 [main] INFO org.pidome.server.services.provider.CertGen - Generating certificate(s), please wait...... 2014-09-06 09:07:51,089 [main] INFO org.pidome.server.services.provider.CertGen - Generating certificate(s), please wait...... 2014-09-06 09:08:00,660 [TriggerTimeRun::09:08] DEBUG org.pidome.server.services.triggerservice.TriggerService - Updating Sunset and Sunrise to 20:19, 07:01 2014-09-06 09:08:04,958 [main] INFO org.pidome.server.services.provider.CertGen - Certificate(s) generated. 2014-09-06 09:08:04,978 [main] INFO org.pidome.server.system.network.Network - Network interface loaded 2014-09-06 09:08:05,827 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket ssl service started: 10.0.0.13 - 8089 2014-09-06 09:08:05,889 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal server has started 2014-09-06 09:08:05,902 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal SSL server has started 2014-09-06 09:08:06,008 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service 2014-09-06 09:08:06,101 [Socket] INFO org.pidome.server.services.socketservice.SocketService - Active, waiting for connections on ip: 10.0.0.13/10.0.0.13 and port: 11000 2014-09-06 09:08:06,598 [main] INFO org.pidome.server.system.hardware.Hardware - Hardware discovery started 2014-09-06 09:08:06,393 [SocketSSL] ERROR org.pidome.server.services.socketservice.SocketService - Message server could not be started java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) at javax.net.ssl.DefaultSSLServerSocketFactory.throwException(SSLServerSocketFactory.java:160) ~[?:1.8.0] at javax.net.ssl.DefaultSSLServerSocketFactory.createServerSocket(SSLServerSocketFactory.java:188) ~[?:1.8.0] at org.pidome.server.services.socketservice.SocketService$2.run(SocketService.java:121) [PiDome_Server.jar:?] Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext) at java.security.Provider$Service.newInstance(Provider.java:1619) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) ~[?:1.8.0] at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) ~[?:1.8.0] at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) ~[?:1.8.0] at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:113) ~[?:1.8.0] at org.pidome.server.services.socketservice.SocketService$2.run(SocketService.java:120) ~[PiDome_Server.jar:?] Caused by: java.security.PrivilegedActionException at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext.getDefaultKeyManager(SSLContextImpl.java:766) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext.(SSLContextImpl.java:675) ~[?:1.8.0] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0] at java.lang.reflect.Constructor.newInstance(Constructor.java:408) ~[?:1.8.0] at java.lang.Class.newInstance(Class.java:433) ~[?:1.8.0] at java.security.Provider$Service.newInstance(Provider.java:1593) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) ~[?:1.8.0] at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) ~[?:1.8.0] at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) ~[?:1.8.0] at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:113) ~[?:1.8.0] at org.pidome.server.services.socketservice.SocketService$2.run(SocketService.java:120) ~[PiDome_Server.jar:?] Caused by: java.io.FileNotFoundException: resources/crtstr/crt.ks (No such file or directory) at java.io.FileInputStream.open(Native Method) ~[?:1.8.0] at java.io.FileInputStream.(FileInputStream.java:131) ~[?:1.8.0] at java.io.FileInputStream.(FileInputStream.java:87) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext$2.run(SSLContextImpl.java:770) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext$2.run(SSLContextImpl.java:767) ~[?:1.8.0] at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext.getDefaultKeyManager(SSLContextImpl.java:766) ~[?:1.8.0] at sun.security.ssl.SSLContextImpl$DefaultSSLContext.(SSLContextImpl.java:675) ~[?:1.8.0] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0] at java.lang.reflect.Constructor.newInstance(Constructor.java:408) ~[?:1.8.0] at java.lang.Class.newInstance(Class.java:433) ~[?:1.8.0] at java.security.Provider$Service.newInstance(Provider.java:1593) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:236) ~[?:1.8.0] at sun.security.jca.GetInstance.getInstance(GetInstance.java:164) ~[?:1.8.0] at javax.net.ssl.SSLContext.getInstance(SSLContext.java:156) ~[?:1.8.0] at javax.net.ssl.SSLContext.getDefault(SSLContext.java:96) ~[?:1.8.0] at javax.net.ssl.SSLServerSocketFactory.getDefault(SSLServerSocketFactory.java:113) ~[?:1.8.0] at org.pidome.server.services.socketservice.SocketService$2.run(SocketService.java:120) ~[PiDome_Server.jar:?] 2014-09-06 09:08:07,321 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Server information layer ready for use 2014-09-06 09:08:10,575 [main] INFO org.pidome.server.services.provider.CertGen - Certificate(s) generated. 2014-09-06 09:08:10,594 [main] INFO org.pidome.server.system.network.Network - Network interface loaded 2014-09-06 09:08:10,598 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Server broadcast service 2014-09-06 09:08:10,731 [main] INFO org.pidome.server.services.network.BroadcastService - Broadcast message: 'DOMCONTROL:10.0.0.13-SCREEN:DOMCONTROL:11000-SCREENSSL:DOMCONTROL:11001' 2014-09-06 09:08:10,741 [SERVICE:BroadcastServer] INFO org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds 2014-09-06 09:08:10,757 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Trigger service 2014-09-06 09:08:10,780 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Websocket service 2014-09-06 09:08:10,868 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerDB - Found 4 triggers 2014-09-06 09:08:11,200 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Got 1 parent rules in Set Night 2014-09-06 09:08:11,204 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Creating AND rules 2014-09-06 09:08:11,239 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Creating values equation from the following data: [{itemtype=daytime, matchvalue=00:00, matchtype=GREATERTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}, {itemtype=daytime, matchvalue=06:00, matchtype=LESSTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}] 2014-09-06 09:08:11,288 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 00:00, method: GREATERTHEN, days: ALL 2014-09-06 09:08:11,351 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket service started: 10.0.0.13 - 8088 2014-09-06 09:08:11,386 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:08 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:08:11,394 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Devices service 2014-09-06 09:08:11,410 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 06:00, method: LESSTHEN, days: ALL 2014-09-06 09:08:11,424 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:08 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:08:11,427 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Total amount of equations created: 2 2014-09-06 09:08:11,630 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Got 1 parent rules in Set Morning 2014-09-06 09:08:11,632 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Creating AND rules 2014-09-06 09:08:11,636 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Creating values equation from the following data: [{itemtype=daytime, matchvalue=05:59, matchtype=GREATERTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}, {itemtype=daytime, matchvalue=12:00, matchtype=LESSTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}] 2014-09-06 09:08:11,694 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 05:59, method: GREATERTHEN, days: ALL 2014-09-06 09:08:11,698 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:08 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:08:11,721 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 12:00, method: LESSTHEN, days: ALL 2014-09-06 09:08:11,724 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:08 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:08:11,745 [main] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevices - prepare 2014-09-06 09:08:11,727 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Total amount of equations created: 2 2014-09-06 09:08:11,810 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Got 1 parent rules in Set Afternoon 2014-09-06 09:08:11,812 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Creating AND rules 2014-09-06 09:08:11,816 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Creating values equation from the following data: [{itemtype=daytime, matchvalue=11:59, matchtype=GREATERTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}, {itemtype=daytime, matchvalue=18:00, matchtype=LESSTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}] 2014-09-06 09:08:11,864 [main] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Added listener: org.pidome.server.system.hardware.peripherals.usb.USBDevices 2014-09-06 09:08:11,866 [main] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevices - Using linux USB 2014-09-06 09:08:11,847 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 11:59, method: GREATERTHEN, days: ALL 2014-09-06 09:08:11,870 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:08 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:08:11,873 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 18:00, method: LESSTHEN, days: ALL 2014-09-06 09:08:11,877 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:08 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 18:00(18:00) 2014-09-06 09:08:11,898 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Total amount of equations created: 2 2014-09-06 09:08:11,921 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Got 1 parent rules in Set Evening 2014-09-06 09:08:11,923 [TriggerService::TriggersPreLoader] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Creating AND rules 2014-09-06 09:08:11,927 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Creating values equation from the following data: [{itemtype=daytime, matchvalue=17:59, matchtype=GREATERTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}, {itemtype=daytime, matchvalue=23:59, matchtype=LESSTHEN, occurrence=ALL, timetype=FIXED, occurrencename=Every day, timetypename=Fixed time}] 2014-09-06 09:08:11,990 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 17:59, method: GREATERTHEN, days: ALL 2014-09-06 09:08:11,994 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:08 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:08:11,997 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Have a time equation with value: 23:59, method: LESSTHEN, days: ALL 2014-09-06 09:08:12,014 [main] INFO org.pidome.server.system.hardware.Hardware - Hardware discovery started 2014-09-06 09:08:12,033 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:08 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 23:59(23:59) 2014-09-06 09:08:12,069 [TriggerService::TriggersPreLoader] TRACE org.pidome.server.services.triggerservice.TriggerEvent - Total amount of equations created: 2 2014-09-06 09:08:12,137 [main] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.Peripheral - New peripheral: TYPE_SERVER 2014-09-06 09:08:12,170 [main] DEBUG org.pidome.server.system.hardware.peripherals.server.ServerDevice - The local server "device" 2014-09-06 09:08:12,218 [main] DEBUG org.pidome.server.system.hardware.peripherals.server.ServerDevices - Event: DEVICE_ADDED 2014-09-06 09:08:12,227 [main] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_ADDED 2014-09-06 09:08:12,257 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.peripherals.pidomeServerPeripheral from PiDome.Peripherals 2014-09-06 09:08:12,280 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.peripherals.pidomeServerPeripheral.PidomeServerPeripheral from PiDome.Peripherals 2014-09-06 09:08:12,655 [main] INFO org.pidome.server.system.hardware.devices.Devices - Device: The PiDome Server self has been loaded 2014-09-06 09:08:12,683 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB 2014-09-06 09:08:12,721 [main] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Server information layer ready for use 2014-09-06 09:08:12,724 [main] DEBUG org.pidome.server.system.hardware.peripherals.Peripherals - Event: DRIVER_LOADED 2014-09-06 09:08:12,744 [main] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Server information layer 2014-09-06 09:08:12,747 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.driver.nativeServerDriver from PiDome.Drivers 2014-09-06 09:08:12,769 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.driver.nativeServerDriver.NativeServerDriver from PiDome.Drivers 2014-09-06 09:08:13,028 [main] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Set peripheral listener: org.pidome.driver.driver.nativeServerDriver.NativeServerDriver 2014-09-06 09:08:13,041 [main] DEBUG org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Added listener: org.pidome.driver.peripherals.pidomeServerPeripheral.PidomeServerPeripheral 2014-09-06 09:08:13,044 [main] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Event: DRIVER_LOADED 2014-09-06 09:08:13,074 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Found devices: [org.pidome.driver.device.pidomeServerDevice] 2014-09-06 09:08:13,077 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Loading declared devices for device: org.pidome.driver.device.pidomeServerDevice 2014-09-06 09:08:13,092 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Found device ids: [1] 2014-09-06 09:08:13,161 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Loading device instance id: 1 2014-09-06 09:08:13,167 [main] DEBUG org.pidome.server.system.packages.Packages - Found installed device id '1' (The PiDome Server self), trying to retrieve 'org.pidome.driver.device.pidomeServerDevice' from package '3' for loading 2014-09-06 09:08:13,191 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.device.pidomeServerDevice from PiDome.Devices 2014-09-06 09:08:13,206 [main] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice from PiDome.Devices 2014-09-06 09:08:13,697 [main] DEBUG org.pidome.server.connector.drivers.devices.Device - Setting filter : java.lang.Object 2014-09-06 09:08:13,711 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Loaded device data: {friendlyname=The PiDome Server self, settings=, address=null, type=0, driver=org.pidome.driver.driver.nativeServerDriver, xml= PiDome Server Some server data. This data is calculated system wide. Except for the memory usage which is from the PiDome server application , name=Rasp server, location=1, fixed=true, id=1, category=2, device=org.pidome.driver.device.pidomeServerDevice, favorite=true, devicebaseid=1, screenX=725, screenY=392} 2014-09-06 09:08:14,771 [main] DEBUG org.pidome.server.connector.drivers.devices.DeviceStructure - Set canonical device base name: org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice:PiDome Server 2014-09-06 09:08:15,610 [main] DEBUG org.pidome.server.connector.drivers.devices.DeviceStructure - There are no options to set 2014-09-06 09:08:15,974 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 09:08:16,429 [main] DEBUG org.pidome.server.connector.drivers.devices.DeviceStructure - Created device options: {} 2014-09-06 09:08:16,533 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Reload categories 2014-09-06 09:08:16,549 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 1:Unknown 2014-09-06 09:08:16,564 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 2:PiDome 2014-09-06 09:08:16,566 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 3:Lighting 2014-09-06 09:08:16,602 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 4:Heating 2014-09-06 09:08:16,605 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 5:Locks 2014-09-06 09:08:16,607 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 6:Media 2014-09-06 09:08:16,630 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 7:Switches 2014-09-06 09:08:16,633 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 8:Remote 2014-09-06 09:08:16,636 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 9:Universal sensor 2014-09-06 09:08:16,639 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 10:Motion 2014-09-06 09:08:16,642 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded category: 11:Display 2014-09-06 09:08:16,645 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Reload sub categories 2014-09-06 09:08:16,659 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 1:Common 2014-09-06 09:08:16,662 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 2:PiDome Server 2014-09-06 09:08:16,671 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 3:Common 2014-09-06 09:08:16,673 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 4:Common 2014-09-06 09:08:16,676 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 5:Common 2014-09-06 09:08:16,689 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 6:Common 2014-09-06 09:08:16,692 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 7:Common 2014-09-06 09:08:16,695 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 8:Common 2014-09-06 09:08:16,697 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 9:Common 2014-09-06 09:08:16,710 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 10:Common 2014-09-06 09:08:16,713 [main] DEBUG org.pidome.server.system.categories.BaseCategories - Loaded sub category: 11:Common 2014-09-06 09:08:16,855 [main] DEBUG org.pidome.server.system.location.BaseLocations - Reload 2014-09-06 09:08:16,875 [main] DEBUG org.pidome.server.system.location.BaseLocations - Loaded location: {name=Location unknown, screenW=0, fixed=true, id=1, floor=1, floorname=Floor unknown, screenX=0, screenH=0, screenY=0} 2014-09-06 09:08:16,894 [main] DEBUG org.pidome.server.system.hardware.devices.Devices - Attaching: driver NativeServerDriver to device org.pidome.driver.device.pidomeServerDevice 2014-09-06 09:08:16,897 [main] DEBUG org.pidome.server.connector.drivers.devices.Device - Added driver listener: org.pidome.driver.driver.nativeServerDriver.NativeServerDriver 2014-09-06 09:08:16,910 [main] DEBUG org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Added listener: org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice 2014-09-06 09:08:16,920 [main] INFO org.pidome.server.system.hardware.devices.Devices - Device: The PiDome Server self has been loaded 2014-09-06 09:08:17,091 [main] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Driver NativeServerDriver on Server information layer on port {Internally used device map} is ready for use 2014-09-06 09:08:17,094 [main] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareAdded","params": {"friendlyname":"Server information layer"} } 2014-09-06 09:08:17,130 [USB-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB 2014-09-06 09:08:17,146 [Thread-8-discovery-timer-60] DEBUG org.pidome.server.system.hardware.Hardware - Started Thread-8 watcher (interrupts after 60 seconds) 2014-09-06 09:08:17,224 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.serial.SerialUtils - Setting new known ports list: /dev/ttyUSB0:/dev/ttyAMA0 2014-09-06 09:08:19,890 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 09:08:19,931 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO 2014-09-06 09:08:20,277 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 09:08:20,358 [Serial-discovery] ERROR org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral driver PidomeNativeSerial can not be started: Temporary disabled 2014-09-06 09:08:20,403 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C 2014-09-06 09:08:20,782 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - New TTY:'/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0' device added, please wait 2014-09-06 09:08:21,164 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Path: /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 2014-09-06 09:08:21,166 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device name: FT232 USB-Serial (UART) IC 2014-09-06 09:08:21,168 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device id: 6001 2014-09-06 09:08:21,191 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device port: /dev/ttyUSB0 2014-09-06 09:08:21,193 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device vendor id: 0403 2014-09-06 09:08:21,195 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device vendor name: Future Technology Devices International, Ltd 2014-09-06 09:08:21,214 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Event: DEVICE_ADDED, /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 2014-09-06 09:08:21,263 [USB-discovery] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.Peripheral - New peripheral: TYPE_USB 2014-09-06 09:08:21,265 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevice - New USB device 2014-09-06 09:08:21,268 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 09:08:21,291 [USB-discovery] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevices - Event: DEVICE_ADDED 2014-09-06 09:08:21,294 [USB-discovery] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_ADDED 2014-09-06 09:08:21,296 [USB-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.peripherals.pidomeNativeUSBSerial from PiDome.Peripherals 2014-09-06 09:08:21,298 [USB-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial from PiDome.Peripherals 2014-09-06 09:08:21,491 [USB-discovery] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareAdded","params": {"friendlyname":"Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC"} } 2014-09-06 09:08:21,612 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Raspberry GPIO I2C ready for use 2014-09-06 09:08:21,851 [main] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 09:08:21,861 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 09:08:21,882 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service 2014-09-06 09:08:21,890 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service 2014-09-06 09:08:22,795 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:08:22,816 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:08:22,844 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 48.7 2014-09-06 09:08:22,848 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '48.7' to datatype: FLOAT 2014-09-06 09:08:22,883 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:08:23,003 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 48.7 2014-09-06 09:08:23,080 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 48.7 2014-09-06 09:08:23,121 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:08:23,123 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:08:23,125 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 73.44 2014-09-06 09:08:23,128 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '73.44' to datatype: FLOAT 2014-09-06 09:08:23,180 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:08:23,184 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:08:23,186 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:08:23,241 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 11.75 2014-09-06 09:08:23,243 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '11.75' to datatype: FLOAT 2014-09-06 09:08:23,245 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:08:23,258 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":48.7,"group":"values"} } 2014-09-06 09:08:23,262 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 73.44 2014-09-06 09:08:23,265 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":73.44,"group":"values"} } 2014-09-06 09:08:23,300 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:08:23,308 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:08:23,311 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.85 2014-09-06 09:08:23,313 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.85' to datatype: FLOAT 2014-09-06 09:08:23,315 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:08:23,315 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 11.75 2014-09-06 09:08:23,320 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":11.75,"group":"values"} } 2014-09-06 09:08:23,322 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.85 2014-09-06 09:08:23,325 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.85,"group":"values"} } 2014-09-06 09:08:23,385 [pool-6-thread-1] DEBUG org.pidome.server.system.datastorage.RoundRobinDataStorage - Database /home/pi/pidome-server/databases/devices/1.data connected 2014-09-06 09:08:23,942 [main] INFO org.pidome.server.services.network.BroadcastService - Broadcast message: 'DOMCONTROL:10.0.0.13-SCREEN:DOMCONTROL:11000-SCREENSSL:DOMCONTROL:11001' 2014-09-06 09:08:24,011 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service 2014-09-06 09:08:24,014 [SERVICE:BroadcastServer] INFO org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds 2014-09-06 09:08:24,132 [WebsocketSelector41] ERROR org.pidome.server.services.clients.http.WebHttpWSService - Websocket error: Address already in use 2014-09-06 09:08:24,107 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket service started: 10.0.0.13 - 8088 2014-09-06 09:08:24,198 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service 2014-09-06 09:08:24,299 [pool-6-thread-1] DEBUG org.pidome.server.system.datastorage.RoundRobinDataStorage - New datatype set for storing: [org.pidome.server.system.datastorage.RoundRobinDataStorageField@144fd2a, org.pidome.server.system.datastorage.RoundRobinDataStorageField@98d228, org.pidome.server.system.datastorage.RoundRobinDataStorageField@1c9e97c, org.pidome.server.system.datastorage.RoundRobinDataStorageField@1bfbc69] 2014-09-06 09:08:24,310 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 73.44 2014-09-06 09:08:24,430 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 11.75 2014-09-06 09:08:24,504 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.85 2014-09-06 09:08:25,314 [USB-discovery] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 09:08:25,341 [Serial-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO 2014-09-06 09:08:25,360 [Thread-12-discovery-timer-60] DEBUG org.pidome.server.system.hardware.Hardware - Started Thread-12 watcher (interrupts after 60 seconds) 2014-09-06 09:08:25,420 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 09:08:25,430 [Serial-discovery] DEBUG org.pidome.server.system.hardware.peripherals.serial.SerialUtils - Setting new known ports list: /dev/ttyUSB0:/dev/ttyAMA0 2014-09-06 09:08:25,438 [Serial-discovery] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.Peripheral - New peripheral: TYPE_SERIAL 2014-09-06 09:08:25,460 [Serial-discovery] DEBUG org.pidome.server.system.hardware.peripherals.serial.SerialDevice - New GPIO Serial device 2014-09-06 09:08:25,463 [Serial-discovery] DEBUG org.pidome.server.system.hardware.peripherals.serial.SerialDevices - Event: DEVICE_ADDED 2014-09-06 09:08:25,501 [Serial-discovery] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_ADDED 2014-09-06 09:08:25,504 [Serial-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.peripherals.pidomeNativeSerial from PiDome.Peripherals 2014-09-06 09:08:25,506 [Serial-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.peripherals.pidomeNativeSerial.PidomeNativeSerial from PiDome.Peripherals 2014-09-06 09:08:25,618 [Serial-discovery] ERROR org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral driver PidomeNativeSerial can not be started: Temporary disabled 2014-09-06 09:08:25,640 [Serial-discovery] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareAdded","params": {"friendlyname":"Serial device speed 57600 baud, 8N1"} } 2014-09-06 09:08:25,653 [I2C-discovery] INFO org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C 2014-09-06 09:08:25,660 [Thread-14-discovery-timer-60] DEBUG org.pidome.server.system.hardware.Hardware - Started Thread-14 watcher (interrupts after 60 seconds) 2014-09-06 09:08:25,692 [I2C-discovery] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.Peripheral - New peripheral: TYPE_I2C 2014-09-06 09:08:25,694 [I2C-discovery] DEBUG org.pidome.server.system.hardware.peripherals.i2c.I2CDevice - New GPIO I2C device 2014-09-06 09:08:24,212 [HTTP service provider] INFO org.pidome.server.system.webservice.DefaultHttpServer - HTTP Webservice started at ip: 10.0.0.13/10.0.0.13, on port: 8080, max threads: 50 2014-09-06 09:08:25,697 [I2C-discovery] DEBUG org.pidome.server.system.hardware.peripherals.i2c.I2CDevices - Event: DEVICE_ADDED 2014-09-06 09:08:25,770 [I2C-discovery] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_ADDED 2014-09-06 09:08:25,790 [I2C-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.peripherals.pidomeNativeI2CBus from PiDome.Peripherals 2014-09-06 09:08:25,791 [I2C-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.peripherals.pidomeNativeI2CBus.PidomeNativeI2CBus from PiDome.Peripherals 2014-09-06 09:08:26,138 [I2C-discovery] DEBUG org.pidome.driver.peripherals.pidomeNativeI2CBus.PidomeNativeI2CBus - Starting peripheral driver for revision: 000f 2014-09-06 09:08:26,173 [I2C-discovery] DEBUG org.pidome.driver.peripherals.pidomeNativeI2CBus.PidomeNativeI2CBus - Going to use bus number: 1 2014-09-06 09:08:26,892 [I2C-discovery] ERROR err - Sep 06, 2014 9:08:26 AM com.pi4j.util.NativeLibraryLoader loadLibraryFromResource WARNING: The temporary file already exists [/tmp/libpi4j.so]; attempting to delete it now. 2014-09-06 09:08:27,003 [I2C-discovery] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Raspberry GPIO I2C ready for use 2014-09-06 09:08:27,005 [I2C-discovery] DEBUG org.pidome.server.system.hardware.peripherals.Peripherals - Event: DRIVER_LOADED 2014-09-06 09:08:27,007 [I2C-discovery] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Raspberry GPIO I2C 2014-09-06 09:08:27,028 [I2C-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.driver.nativeDefaultI2CDriver from PiDome.I2C 2014-09-06 09:08:27,030 [I2C-discovery] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.driver.nativeDefaultI2CDriver.NativeDefaultI2CDriver from PiDome.I2C 2014-09-06 09:08:27,295 [I2C-discovery] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Set peripheral listener: org.pidome.driver.driver.nativeDefaultI2CDriver.NativeDefaultI2CDriver 2014-09-06 09:08:27,297 [I2C-discovery] DEBUG org.pidome.driver.driver.nativeDefaultI2CDriver.NativeDefaultI2CDriver - Added listener: org.pidome.driver.peripherals.pidomeNativeI2CBus.PidomeNativeI2CBus 2014-09-06 09:08:27,319 [I2C-discovery] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Event: DRIVER_LOADED 2014-09-06 09:08:27,327 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Found devices: [org.pidome.driver.device.i2cLtsLc, org.pidome.driver.device.bareboneI2CDevice, org.pidome.driver.device.pidomeTrippleReflectorSensorsI2CBoard] 2014-09-06 09:08:27,349 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Loading declared devices for device: org.pidome.driver.device.i2cLtsLc 2014-09-06 09:08:27,354 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Found device ids: [] 2014-09-06 09:08:27,356 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Loading declared devices for device: org.pidome.driver.device.bareboneI2CDevice 2014-09-06 09:08:27,391 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Found device ids: [] 2014-09-06 09:08:27,393 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Loading declared devices for device: org.pidome.driver.device.pidomeTrippleReflectorSensorsI2CBoard 2014-09-06 09:08:27,397 [I2C-discovery] DEBUG org.pidome.server.system.hardware.devices.Devices - Found device ids: [] 2014-09-06 09:08:27,419 [I2C-discovery] DEBUG org.pidome.server.system.hardware.drivers.Drivers - Driver NativeDefaultI2CDriver on Raspberry GPIO I2C on port {Auto discovery by driver} is ready for use 2014-09-06 09:08:27,421 [I2C-discovery] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareAdded","params": {"friendlyname":"Raspberry GPIO I2C"} } 2014-09-06 09:08:27,460 [main] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started 2014-09-06 09:08:27,463 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Messenger plugin service 2014-09-06 09:08:27,467 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service 2014-09-06 09:08:27,471 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started 2014-09-06 09:08:27,490 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Utility usage plugin service 2014-09-06 09:08:27,492 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service 2014-09-06 09:08:27,509 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Devices plugin service 2014-09-06 09:08:27,512 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service 2014-09-06 09:08:27,549 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service HTTPS service 2014-09-06 09:08:27,553 [main] DEBUG org.pidome.server.services.clients.http.WebHttpsService - HTTPS service config loaded 2014-09-06 09:08:27,615 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service HTTP service 2014-09-06 09:08:27,618 [main] DEBUG org.pidome.server.services.clients.http.WebHttpService - HTTP service config loaded 2014-09-06 09:08:27,679 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service User status service 2014-09-06 09:08:27,681 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Presence service 2014-09-06 09:08:27,683 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Secure Websocket service 2014-09-06 09:08:27,750 [HTTP service provider] ERROR org.pidome.server.system.webservice.DefaultHttpServer - Port already in use 2014-09-06 09:08:27,907 [PluginService::Start:Messenger plugin service] DEBUG org.pidome.server.services.plugins.PluginService - Found plugins: {} 2014-09-06 09:08:27,927 [PluginService::Start:Utility usage plugin service] DEBUG org.pidome.server.services.plugins.PluginService - Found plugins: {} 2014-09-06 09:08:27,923 [PluginService::Start:Devices plugin service] DEBUG org.pidome.server.services.plugins.PluginService - Found plugins: {} 2014-09-06 09:08:29,521 [main] INFO org.pidome.server.services.clients.http.WebHttpWSService - Websocket ssl service started: 10.0.0.13 - 8089 2014-09-06 09:08:29,524 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Remotes plugin service 2014-09-06 09:08:29,527 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service 2014-09-06 09:08:29,532 [WebsocketSelector39] ERROR org.pidome.server.services.clients.http.WebHttpWSService - Websocket error: Address already in use 2014-09-06 09:08:29,590 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Macro service 2014-09-06 09:08:29,596 [PluginService::Start:Remotes plugin service] DEBUG org.pidome.server.services.plugins.PluginService - Found plugins: {} 2014-09-06 09:08:29,614 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Socket service 2014-09-06 09:08:29,679 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal server has started 2014-09-06 09:08:29,719 [main] INFO org.pidome.server.services.socketservice.SocketService - Client display terminal SSL server has started 2014-09-06 09:08:29,723 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Day part service 2014-09-06 09:08:29,725 [main] DEBUG org.pidome.server.services.ServiceController - Attempting to start service Media plugin service 2014-09-06 09:08:29,727 [main] INFO org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service 2014-09-06 09:08:30,921 [PluginService::Start:Media plugin service] DEBUG org.pidome.server.services.plugins.PluginService - Found plugins: {} 2014-09-06 09:08:29,684 [Socket] ERROR org.pidome.server.services.socketservice.SocketService - Message server could not be started java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) ~[?:1.8.0] at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:382) ~[?:1.8.0] at java.net.ServerSocket.bind(ServerSocket.java:375) ~[?:1.8.0] at java.net.ServerSocket.(ServerSocket.java:237) ~[?:1.8.0] at org.pidome.server.services.socketservice.SocketService$1.run(SocketService.java:106) [PiDome_Server.jar:?] 2014-09-06 09:08:33,201 [HTTPS Service provider] ERROR org.pidome.server.system.webservice.DefaultHttpsServer - Port already in use 2014-09-06 09:08:35,618 [HTTPS Service provider] INFO org.pidome.server.system.webservice.DefaultHttpsServer - HTTPS Webservice started at ip: 10.0.0.13/10.0.0.13, on port: 8443, max threads: 50 2014-09-06 09:08:37,577 [SocketSSL] INFO org.pidome.server.services.socketservice.SocketService - Active, waiting for connections on ip: 10.0.0.13/10.0.0.13 and port: 11001 2014-09-06 09:09:00,668 [TriggerTimeRun::09:09] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:09 in trigger event 'Set Night' 2014-09-06 09:09:00,672 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:09:00,675 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:09:00,677 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:09:00,679 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:09:00,689 [TriggerTimeRun::09:09] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:09 in trigger event 'Set Morning' 2014-09-06 09:09:00,691 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:09:00,694 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:09 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:09:00,713 [TriggerTimeRun::09:09] INFO org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Morning 2014-09-06 09:09:00,717 [TriggerTimeRun::09:09] DEBUG org.pidome.server.services.macros.MacroService - MACROSERVICE: Running macro id '1' invoked from commandline 2014-09-06 09:09:00,725 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"MacroService.runMacro","params": {"id":1} } 2014-09-06 09:09:00,739 [TriggerTimeRun::09:09] INFO org.pidome.server.system.dayparts.DayPartsService - Set daypart to Morning at 06-09-2014 09:09 2014-09-06 09:09:00,757 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DayPartService.setDayPart","params": {"name":"Morning","id":1} } 2014-09-06 09:09:00,760 [TriggerTimeRun::09:09] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:09 in trigger event 'Set Afternoon' 2014-09-06 09:09:00,762 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:09:00,765 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:09:00,767 [TriggerTimeRun::09:09] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:09 in trigger event 'Set Evening' 2014-09-06 09:09:00,769 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:09:00,772 [TriggerTimeRun::09:09] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:09 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:09:00,975 [TriggerTimeRun::09:09] INFO org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Morning 2014-09-06 09:09:01,051 [TriggerTimeRun::09:09] INFO org.pidome.server.system.dayparts.DayPartsService - Set daypart to Morning at 06-09-2014 09:09 2014-09-06 09:09:12,743 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:09:12,758 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:09:12,761 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 48.2 2014-09-06 09:09:12,764 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '48.2' to datatype: FLOAT 2014-09-06 09:09:12,766 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:09:12,780 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 48.2 2014-09-06 09:09:12,783 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":48.2,"group":"values"} } 2014-09-06 09:09:12,786 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 48.2 2014-09-06 09:09:12,790 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:09:12,792 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:09:12,794 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 39.75 2014-09-06 09:09:12,796 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '39.75' to datatype: FLOAT 2014-09-06 09:09:12,804 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:09:12,815 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 39.75 2014-09-06 09:09:12,835 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:09:12,837 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:09:12,844 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":39.75,"group":"values"} } 2014-09-06 09:09:12,853 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 9.53 2014-09-06 09:09:12,855 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '9.53' to datatype: FLOAT 2014-09-06 09:09:12,862 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 39.75 2014-09-06 09:09:12,857 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:09:12,866 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 9.53 2014-09-06 09:09:12,870 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:09:12,872 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:09:12,874 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.78 2014-09-06 09:09:12,876 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.78' to datatype: FLOAT 2014-09-06 09:09:12,868 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":9.53,"group":"values"} } 2014-09-06 09:09:12,868 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:09:12,909 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.78 2014-09-06 09:09:12,915 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.78,"group":"values"} } 2014-09-06 09:09:12,947 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 9.53 2014-09-06 09:09:12,989 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.78 2014-09-06 09:10:00,670 [TriggerTimeRun::09:10] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:10 in trigger event 'Set Night' 2014-09-06 09:10:00,673 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:10:00,675 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:10:00,680 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:10:00,683 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:10:00,685 [TriggerTimeRun::09:10] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:10 in trigger event 'Set Morning' 2014-09-06 09:10:00,690 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:10:00,695 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:10 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:10:00,697 [TriggerTimeRun::09:10] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:10 in trigger event 'Set Afternoon' 2014-09-06 09:10:00,699 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:10:00,702 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:10:00,704 [TriggerTimeRun::09:10] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:10 in trigger event 'Set Evening' 2014-09-06 09:10:00,706 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:10:00,708 [TriggerTimeRun::09:10] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:10 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:10:12,932 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:10:12,942 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:10:12,944 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 47.1 2014-09-06 09:10:12,946 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '47.1' to datatype: FLOAT 2014-09-06 09:10:12,948 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:10:12,951 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 47.1 2014-09-06 09:10:12,954 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":47.1,"group":"values"} } 2014-09-06 09:10:12,957 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 47.1 2014-09-06 09:10:12,967 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:10:12,969 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:10:12,971 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 11.09 2014-09-06 09:10:12,973 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '11.09' to datatype: FLOAT 2014-09-06 09:10:12,976 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:10:12,996 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 11.09 2014-09-06 09:10:13,003 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":11.09,"group":"values"} } 2014-09-06 09:10:13,009 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 11.09 2014-09-06 09:10:13,019 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:10:13,021 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:10:13,023 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 10.69 2014-09-06 09:10:13,025 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '10.69' to datatype: FLOAT 2014-09-06 09:10:13,043 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:10:13,050 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 10.69 2014-09-06 09:10:13,057 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":10.69,"group":"values"} } 2014-09-06 09:10:13,085 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 10.69 2014-09-06 09:10:13,109 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:10:13,111 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:10:13,113 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.76 2014-09-06 09:10:13,115 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.76' to datatype: FLOAT 2014-09-06 09:10:13,117 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:10:13,157 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.76 2014-09-06 09:10:13,172 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.76,"group":"values"} } 2014-09-06 09:10:13,181 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.76 2014-09-06 09:10:52,438 [WebSocketWorker-17] DEBUG org.pidome.server.services.clients.http.WebHttpWSService - New connection: 10.0.0.24 - / 2014-09-06 09:11:00,680 [TriggerTimeRun::09:11] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:11 in trigger event 'Set Night' 2014-09-06 09:11:00,682 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:11:00,684 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:11:00,719 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:11:00,721 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:11:00,723 [TriggerTimeRun::09:11] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:11 in trigger event 'Set Morning' 2014-09-06 09:11:00,725 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:11:00,727 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:11 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:11:00,738 [TriggerTimeRun::09:11] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:11 in trigger event 'Set Afternoon' 2014-09-06 09:11:00,740 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:11:00,742 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:11:00,744 [TriggerTimeRun::09:11] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:11 in trigger event 'Set Evening' 2014-09-06 09:11:00,753 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:11:00,756 [TriggerTimeRun::09:11] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:11 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:11:13,176 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:11:13,185 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:11:13,187 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 47.6 2014-09-06 09:11:13,189 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '47.6' to datatype: FLOAT 2014-09-06 09:11:13,191 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:11:13,194 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 47.6 2014-09-06 09:11:13,196 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":47.6,"group":"values"} } 2014-09-06 09:11:13,200 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 47.6 2014-09-06 09:11:13,221 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:11:13,223 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:11:13,225 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 20.94 2014-09-06 09:11:13,227 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '20.94' to datatype: FLOAT 2014-09-06 09:11:13,245 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:11:13,254 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 20.94 2014-09-06 09:11:13,256 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":20.94,"group":"values"} } 2014-09-06 09:11:13,260 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:11:13,261 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:11:13,264 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 12.49 2014-09-06 09:11:13,269 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '12.49' to datatype: FLOAT 2014-09-06 09:11:13,271 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:11:13,274 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 12.49 2014-09-06 09:11:13,276 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":12.49,"group":"values"} } 2014-09-06 09:11:13,279 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:11:13,286 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:11:13,288 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.75 2014-09-06 09:11:13,290 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.75' to datatype: FLOAT 2014-09-06 09:11:13,292 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:11:13,302 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.75 2014-09-06 09:11:13,304 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.75,"group":"values"} } 2014-09-06 09:11:13,310 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 20.94 2014-09-06 09:11:13,371 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 12.49 2014-09-06 09:11:13,441 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.75 2014-09-06 09:11:20,939 [Thread-47] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC ready for use 2014-09-06 09:11:20,949 [Thread-47] INFO org.pidome.server.system.hardware.drivers.Drivers - Something went wrong width the hardware: MEthod does not support NID to request driver. 2014-09-06 09:11:21,424 [Thread-47] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 09:12:00,743 [TriggerTimeRun::09:12] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:12 in trigger event 'Set Night' 2014-09-06 09:12:00,745 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:12:00,747 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:12:00,750 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:12:00,752 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:12:00,754 [TriggerTimeRun::09:12] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:12 in trigger event 'Set Morning' 2014-09-06 09:12:00,756 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:12:00,758 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:12 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:12:00,760 [TriggerTimeRun::09:12] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:12 in trigger event 'Set Afternoon' 2014-09-06 09:12:00,762 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:12:00,764 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:12:00,766 [TriggerTimeRun::09:12] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:12 in trigger event 'Set Evening' 2014-09-06 09:12:00,768 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:12:00,770 [TriggerTimeRun::09:12] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:12 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:12:13,363 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:12:13,365 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:12:13,367 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 47.1 2014-09-06 09:12:13,383 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '47.1' to datatype: FLOAT 2014-09-06 09:12:13,385 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:12:13,400 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 47.1 2014-09-06 09:12:13,404 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 47.1 2014-09-06 09:12:13,410 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:12:13,412 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:12:13,414 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 13.27 2014-09-06 09:12:13,416 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '13.27' to datatype: FLOAT 2014-09-06 09:12:13,402 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":47.1,"group":"values"} } 2014-09-06 09:12:13,466 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:12:13,486 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 13.27 2014-09-06 09:12:13,490 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 13.27 2014-09-06 09:12:13,490 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":13.27,"group":"values"} } 2014-09-06 09:12:13,491 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:12:13,505 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:12:13,507 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 7.71 2014-09-06 09:12:13,540 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '7.71' to datatype: FLOAT 2014-09-06 09:12:13,562 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:12:13,569 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 7.71 2014-09-06 09:12:13,579 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":7.71,"group":"values"} } 2014-09-06 09:12:13,583 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 7.71 2014-09-06 09:12:13,600 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:12:13,602 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:12:13,604 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.74 2014-09-06 09:12:13,606 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.74' to datatype: FLOAT 2014-09-06 09:12:13,608 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:12:13,635 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.74 2014-09-06 09:12:13,637 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.74,"group":"values"} } 2014-09-06 09:12:13,677 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.74 2014-09-06 09:13:00,748 [TriggerTimeRun::09:13] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:13 in trigger event 'Set Night' 2014-09-06 09:13:00,751 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:13:00,753 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:13:00,755 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:13:00,757 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:13:00,759 [TriggerTimeRun::09:13] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:13 in trigger event 'Set Morning' 2014-09-06 09:13:00,762 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:13:00,764 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:13 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:13:00,766 [TriggerTimeRun::09:13] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:13 in trigger event 'Set Afternoon' 2014-09-06 09:13:00,768 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:13:00,770 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:13:00,772 [TriggerTimeRun::09:13] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:13 in trigger event 'Set Evening' 2014-09-06 09:13:00,774 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:13:00,776 [TriggerTimeRun::09:13] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:13 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:13:01,647 [Thread-49] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: 2 (t;0) 2014-09-06 09:13:01,673 [Thread-49] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: 2 (0) 2014-09-06 09:13:02,694 [Thread-49] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: 2 (,) 2014-09-06 09:13:04,116 [Thread-88] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 09:13:05,789 [WebSocketWorker-17] DEBUG org.pidome.server.services.clients.http.WebHttpWSService - Closed connection: 10.0.0.24, - - false 2014-09-06 09:13:06,520 [WebSocketWorker-17] DEBUG org.pidome.server.services.clients.http.WebHttpWSService - New connection: 10.0.0.24 - / 2014-09-06 09:13:13,662 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:13:13,678 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:13:13,680 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 47.6 2014-09-06 09:13:13,683 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '47.6' to datatype: FLOAT 2014-09-06 09:13:13,684 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:13:13,699 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 47.6 2014-09-06 09:13:13,702 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":47.6,"group":"values"} } 2014-09-06 09:13:13,707 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 47.6 2014-09-06 09:13:13,716 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:13:13,722 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:13:13,724 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 13.58 2014-09-06 09:13:13,726 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '13.58' to datatype: FLOAT 2014-09-06 09:13:13,728 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:13:13,739 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 13.58 2014-09-06 09:13:13,750 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":13.58,"group":"values"} } 2014-09-06 09:13:13,754 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:13:13,767 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 13.58 2014-09-06 09:13:13,769 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:13:13,772 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 8.95 2014-09-06 09:13:13,774 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '8.95' to datatype: FLOAT 2014-09-06 09:13:13,775 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:13:13,783 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 8.95 2014-09-06 09:13:13,786 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":8.95,"group":"values"} } 2014-09-06 09:13:13,793 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:13:13,812 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:13:13,821 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.73 2014-09-06 09:13:13,841 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 8.95 2014-09-06 09:13:13,823 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.73' to datatype: FLOAT 2014-09-06 09:13:13,849 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:13:13,857 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.73 2014-09-06 09:13:13,860 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.73,"group":"values"} } 2014-09-06 09:13:13,898 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.73 2014-09-06 09:13:58,927 [Thread-108] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 09:14:00,206 [WebsocketSelector18] DEBUG org.pidome.server.services.clients.http.WebHttpWSService - Closed connection: 10.0.0.24, - - true 2014-09-06 09:14:00,761 [TriggerTimeRun::09:14] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:14 in trigger event 'Set Night' 2014-09-06 09:14:00,766 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:14:00,768 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:14:00,770 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:14:00,780 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:14:00,782 [TriggerTimeRun::09:14] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:14 in trigger event 'Set Morning' 2014-09-06 09:14:00,786 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:14:00,789 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:14 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:14:00,799 [TriggerTimeRun::09:14] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:14 in trigger event 'Set Afternoon' 2014-09-06 09:14:00,801 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:14:00,803 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:14:00,805 [TriggerTimeRun::09:14] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:14 in trigger event 'Set Evening' 2014-09-06 09:14:00,807 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:14:00,830 [TriggerTimeRun::09:14] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:14 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:14:00,941 [WebSocketWorker-17] DEBUG org.pidome.server.services.clients.http.WebHttpWSService - New connection: 10.0.0.24 - / 2014-09-06 09:14:10,802 [Thread-49] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: 2 (p22) 2014-09-06 09:14:13,882 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:14:13,884 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:14:13,886 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 47.1 2014-09-06 09:14:13,888 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '47.1' to datatype: FLOAT 2014-09-06 09:14:13,893 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:14:13,895 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 47.1 2014-09-06 09:14:13,900 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 47.1 2014-09-06 09:14:13,898 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":47.1,"group":"values"} } 2014-09-06 09:14:13,921 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:14:13,926 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:14:13,928 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 9.38 2014-09-06 09:14:13,939 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '9.38' to datatype: FLOAT 2014-09-06 09:14:13,944 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:14:13,958 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 9.38 2014-09-06 09:14:13,972 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 9.38 2014-09-06 09:14:13,964 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":9.38,"group":"values"} } 2014-09-06 09:14:13,990 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:14:13,992 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:14:13,995 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 10.16 2014-09-06 09:14:13,997 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '10.16' to datatype: FLOAT 2014-09-06 09:14:14,041 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:14:14,073 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 10.16 2014-09-06 09:14:14,085 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:14:14,087 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:14:14,095 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":10.16,"group":"values"} } 2014-09-06 09:14:14,111 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 10.16 2014-09-06 09:14:14,121 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.73 2014-09-06 09:14:14,123 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.73' to datatype: FLOAT 2014-09-06 09:14:14,125 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:14:14,135 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.73 2014-09-06 09:14:14,138 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.73,"group":"values"} } 2014-09-06 09:14:14,182 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.73 2014-09-06 09:14:48,472 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removing 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device, please wait, removing... 2014-09-06 09:14:48,477 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.devices.Devices - Stopping devices for driver org.pidome.driver.driver.nativeMySensorsDriver14 2014-09-06 09:14:48,544 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral stopped. 2014-09-06 09:14:48,546 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removed 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' 2014-09-06 09:14:48,528 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb-serial 2014-09-06 09:14:48,528 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: tty 2014-09-06 09:14:48,568 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Removed TTY:'/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0' device, please wait 2014-09-06 09:14:48,601 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Event: DEVICE_REMOVED, /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 2014-09-06 09:14:48,603 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removing 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device, please wait, removing... 2014-09-06 09:14:48,604 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevices - Event: DEVICE_REMOVED 2014-09-06 09:14:48,606 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_REMOVED 2014-09-06 09:14:48,608 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.Peripherals - Panic!! Stopping Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC on port /dev/ttyUSB0 2014-09-06 09:14:48,623 [Rasp USB Monitor] DEBUG org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Releasing driver 2014-09-06 09:14:48,626 [Rasp USB Monitor] DEBUG org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - No known connection on 'null' or port already closed. 2014-09-06 09:14:48,627 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.Peripherals - Event: DRIVER_UNLOAD 2014-09-06 09:14:48,653 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral stopped. 2014-09-06 09:14:48,655 [Rasp USB Monitor] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareRemoved","params": {"friendlyname":"Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC"} } 2014-09-06 09:14:48,677 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - Removed 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' 2014-09-06 09:14:48,867 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb 2014-09-06 09:14:48,991 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb 2014-09-06 09:14:50,711 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb 2014-09-06 09:14:50,823 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb 2014-09-06 09:14:51,021 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: usb-serial 2014-09-06 09:14:51,130 [Rasp USB Monitor] TRACE org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - USB event subsystem: tty 2014-09-06 09:14:51,133 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - New TTY:'/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB1/tty/ttyUSB1' device added, please wait 2014-09-06 09:14:51,331 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Path: /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB1/tty/ttyUSB1 2014-09-06 09:14:51,333 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device name: FT232 USB-Serial (UART) IC 2014-09-06 09:14:51,345 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device id: 6001 2014-09-06 09:14:51,346 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device port: /dev/ttyUSB1 2014-09-06 09:14:51,347 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device vendor id: 0403 2014-09-06 09:14:51,391 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Device vendor name: Future Technology Devices International, Ltd 2014-09-06 09:14:51,393 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Event: DEVICE_ADDED, /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB1/tty/ttyUSB1 2014-09-06 09:14:51,394 [Rasp USB Monitor] DEBUG org.pidome.server.connector.drivers.peripherals.hardware.Peripheral - New peripheral: TYPE_USB 2014-09-06 09:14:51,396 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevice - New USB device 2014-09-06 09:14:51,397 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 09:14:51,433 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.usb.USBDevices - New 'Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC' device added, please wait, adding... 2014-09-06 09:14:51,398 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.peripherals.usb.USBDevices - Event: DEVICE_ADDED 2014-09-06 09:14:51,448 [Rasp USB Monitor] DEBUG org.pidome.server.system.hardware.Hardware - New hardware event: HARDWARE_ADDED 2014-09-06 09:14:51,452 [Rasp USB Monitor] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading package org.pidome.driver.peripherals.pidomeNativeUSBSerial from PiDome.Peripherals 2014-09-06 09:14:51,454 [Rasp USB Monitor] DEBUG org.pidome.server.system.packages.PackageClassLoader - Loading class org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial from PiDome.Peripherals 2014-09-06 09:14:51,608 [Rasp USB Monitor] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - JSON String to parse: {"vid":"0403","hardwarePort":"/dev/ttyUSB1","swdriverid":"NATIVE_PIDOMEMYSENSORSDRIVER_1_4","swdriverversion":"0.0.1","pid":"6001","hwdriveroptions":{"portspeed":"115200","stopbits":"1","parity":"none","databits":"8"}} 2014-09-06 09:14:51,644 [Rasp USB Monitor] DEBUG org.pidome.server.system.rpc.PidomeJSONRPC - Parsed JSON Object: {vid=0403, hardwarePort=/dev/ttyUSB1, swdriverid=NATIVE_PIDOMEMYSENSORSDRIVER_1_4, swdriverversion=0.0.1, pid=6001, hwdriveroptions={portspeed=115200, stopbits=1, parity=none, databits=8}} 2014-09-06 09:14:51,648 [Rasp USB Monitor] DEBUG org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Got driver option(s) set: {portspeed=115200, stopbits=1, parity=none, databits=8} 2014-09-06 09:14:51,701 [Rasp USB Monitor] DEBUG org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Port 'null' init 2014-09-06 09:14:51,792 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Peripheral Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC ready for use 2014-09-06 09:14:51,795 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.drivers.Drivers - Something went wrong width the hardware: MEthod does not support NID to request driver. 2014-09-06 09:14:52,546 [Rasp USB Monitor] ERROR org.pidome.server.system.hardware.peripherals.Peripherals - Error starrting peripheral Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC from settings file ttyUSB1: Could not open port: Port name - /dev/ttyUSB1; Method name - openPort(); Exception type - Port busy. 2014-09-06 09:14:52,628 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Attached device not saved/recognized/misconfigured, can not auto load: Error starting peripheral: Could not open port: Port name - /dev/ttyUSB1; Method name - openPort(); Exception type - Port busy. 2014-09-06 09:14:52,633 [Rasp USB Monitor] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"SystemService.hardwareAdded","params": {"friendlyname":"Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC"} } 2014-09-06 09:14:53,193 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.devices.Devices - Device: Temperature has been loaded 2014-09-06 09:14:53,220 [Rasp USB Monitor] INFO org.pidome.server.system.hardware.peripherals.Peripherals - Loaded and started Future Technology Devices International, Ltd, FT232 USB-Serial (UART) IC from saved configuration with: NativeMySensorsDriver14 2014-09-06 09:15:00,798 [TriggerTimeRun::09:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:15 in trigger event 'Set Night' 2014-09-06 09:15:00,802 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:15:00,804 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:15:00,806 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:15:00,808 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:15:00,838 [TriggerTimeRun::09:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:15 in trigger event 'Set Morning' 2014-09-06 09:15:00,843 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:15:00,846 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:15 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:15:00,848 [TriggerTimeRun::09:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:15 in trigger event 'Set Afternoon' 2014-09-06 09:15:00,877 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:15:00,896 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:15:00,898 [TriggerTimeRun::09:15] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:15 in trigger event 'Set Evening' 2014-09-06 09:15:00,904 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:15:00,910 [TriggerTimeRun::09:15] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:15 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:15:14,221 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:15:14,235 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:15:14,237 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 48.7 2014-09-06 09:15:14,255 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '48.7' to datatype: FLOAT 2014-09-06 09:15:14,257 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:15:14,271 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 48.7 2014-09-06 09:15:14,273 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":48.7,"group":"values"} } 2014-09-06 09:15:14,284 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 48.7 2014-09-06 09:15:14,305 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:15:14,307 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:15:14,332 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 48.95 2014-09-06 09:15:14,357 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '48.95' to datatype: FLOAT 2014-09-06 09:15:14,375 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:15:14,395 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 48.95 2014-09-06 09:15:14,397 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":48.95,"group":"values"} } 2014-09-06 09:15:14,404 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 48.95 2014-09-06 09:15:14,404 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:15:14,433 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:15:14,435 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 12.02 2014-09-06 09:15:14,437 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '12.02' to datatype: FLOAT 2014-09-06 09:15:14,470 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:15:14,494 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 12.02 2014-09-06 09:15:14,540 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":12.02,"group":"values"} } 2014-09-06 09:15:14,497 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:15:14,559 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:15:14,576 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 12.02 2014-09-06 09:15:14,588 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.7 2014-09-06 09:15:14,609 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.7' to datatype: FLOAT 2014-09-06 09:15:14,618 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:15:14,655 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.7 2014-09-06 09:15:14,657 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.7,"group":"values"} } 2014-09-06 09:15:14,703 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.7 2014-09-06 09:15:35,831 [Thread-151] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Method handling error org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157) ~[PiDome_Server.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0] at java.lang.reflect.Method.invoke(Method.java:483) ~[?:1.8.0] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109) [PiDome_Server.jar:?] 2014-09-06 09:15:36,019 [Thread-151] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Constructed method exception message: {data={trace=org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral\\n at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157)\\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\\n at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\\n at java.lang.reflect.Method.invoke(Method.java:483)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230)\\n at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55)\\n at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109)\\n, message=Unknown port used for peripheral}, jsonrpc=2.0, error={code=-32000, message=Server error}} 2014-09-06 09:15:38,517 [Thread-155] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Method handling error org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157) ~[PiDome_Server.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0] at java.lang.reflect.Method.invoke(Method.java:483) ~[?:1.8.0] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343) [PiDome_Server.jar:?] at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55) [PiDome_Server.jar:?] at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109) [PiDome_Server.jar:?] 2014-09-06 09:15:38,594 [Thread-155] ERROR org.pidome.server.system.rpc.AbstractRPCMethodExecutor - Constructed method exception message: {data={trace=org.pidome.server.connector.drivers.peripherals.software.PeripheralSoftwareException: Unknown port used for peripheral\\n at org.pidome.server.system.rpc.HardwareServiceJSONRPCWrapper.getSoftwareDriverPresentation(HardwareServiceJSONRPCWrapper.java:157)\\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\\n at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\\n at java.lang.reflect.Method.invoke(Method.java:483)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:133)\\n at org.pidome.server.system.rpc.AbstractRPCMethodExecutor.execMethod(AbstractRPCMethodExecutor.java:103)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handleRequest(PidomeJSONRPC.java:343)\\n at org.pidome.server.system.rpc.PidomeJSONRPC.handle(PidomeJSONRPC.java:230)\\n at org.pidome.server.system.webservice.webclient.Webclient_jsonrpc.collect(Webclient_jsonrpc.java:55)\\n at org.pidome.server.system.webservice.HTTPClientHandler.run(HTTPClientHandler.java:109)\\n, message=Unknown port used for peripheral}, jsonrpc=2.0, error={code=-32000, message=Server error}} 2014-09-06 09:15:44,497 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.7 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 09:15:44,522 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.3 in device Study, error: Group 'S_MOTION' does not exist 2014-09-06 09:16:00,819 [TriggerTimeRun::09:16] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:16 in trigger event 'Set Night' 2014-09-06 09:16:00,821 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:16:00,824 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:16:00,826 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:16:00,859 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:16:00,873 [TriggerTimeRun::09:16] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:16 in trigger event 'Set Morning' 2014-09-06 09:16:00,875 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:16:00,877 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:16 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:16:00,893 [TriggerTimeRun::09:16] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:16 in trigger event 'Set Afternoon' 2014-09-06 09:16:00,896 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:16:00,898 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:16:00,914 [TriggerTimeRun::09:16] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:16 in trigger event 'Set Evening' 2014-09-06 09:16:00,917 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:16:00,945 [TriggerTimeRun::09:16] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:16 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:16:14,739 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:16:14,741 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:16:14,743 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 48.7 2014-09-06 09:16:14,745 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '48.7' to datatype: FLOAT 2014-09-06 09:16:14,747 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:16:14,778 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 48.7 2014-09-06 09:16:14,783 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":48.7,"group":"values"} } 2014-09-06 09:16:14,790 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 48.7 2014-09-06 09:16:14,841 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:16:14,844 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:16:14,845 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 100.0 2014-09-06 09:16:14,847 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '100.0' to datatype: FLOAT 2014-09-06 09:16:14,916 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:16:14,934 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 100.0 2014-09-06 09:16:14,942 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":100.0,"group":"values"} } 2014-09-06 09:16:14,960 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:16:14,978 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 100.0 2014-09-06 09:16:14,997 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:16:15,015 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 13.21 2014-09-06 09:16:15,018 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '13.21' to datatype: FLOAT 2014-09-06 09:16:15,024 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:16:15,042 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 13.21 2014-09-06 09:16:15,055 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:16:15,091 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 13.21 2014-09-06 09:16:15,071 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":13.21,"group":"values"} } 2014-09-06 09:16:15,071 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:16:15,110 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.69 2014-09-06 09:16:15,112 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.69' to datatype: FLOAT 2014-09-06 09:16:15,114 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:16:15,162 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.69 2014-09-06 09:16:15,164 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.69,"group":"values"} } 2014-09-06 09:16:15,194 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.69 2014-09-06 09:17:00,844 [TriggerTimeRun::09:17] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:17 in trigger event 'Set Night' 2014-09-06 09:17:00,846 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:17:00,862 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:17:00,864 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:17:00,866 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:17:00,868 [TriggerTimeRun::09:17] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:17 in trigger event 'Set Morning' 2014-09-06 09:17:00,900 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:17:00,902 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:17 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:17:00,904 [TriggerTimeRun::09:17] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:17 in trigger event 'Set Afternoon' 2014-09-06 09:17:00,906 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:17:00,938 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:17:00,942 [TriggerTimeRun::09:17] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:17 in trigger event 'Set Evening' 2014-09-06 09:17:00,945 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:17:00,970 [TriggerTimeRun::09:17] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:17 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:17:15,257 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:17:15,272 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:17:15,274 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 49.2 2014-09-06 09:17:15,277 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '49.2' to datatype: FLOAT 2014-09-06 09:17:15,278 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:17:15,333 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 49.2 2014-09-06 09:17:15,335 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":49.2,"group":"values"} } 2014-09-06 09:17:15,345 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 49.2 2014-09-06 09:17:15,360 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:17:15,362 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:17:15,364 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 100.0 2014-09-06 09:17:15,366 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '100.0' to datatype: FLOAT 2014-09-06 09:17:15,401 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:17:15,426 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:17:15,435 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 100.0 2014-09-06 09:17:15,427 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:17:15,466 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":100.0,"group":"values"} } 2014-09-06 09:17:15,501 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 100.0 2014-09-06 09:17:15,512 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 7.45 2014-09-06 09:17:15,532 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '7.45' to datatype: FLOAT 2014-09-06 09:17:15,534 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:17:15,550 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 7.45 2014-09-06 09:17:15,569 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":7.45,"group":"values"} } 2014-09-06 09:17:15,537 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:17:15,595 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:17:15,597 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.68 2014-09-06 09:17:15,617 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.68' to datatype: FLOAT 2014-09-06 09:17:15,641 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:17:15,640 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 7.45 2014-09-06 09:17:15,679 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.68 2014-09-06 09:17:15,682 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.68,"group":"values"} } 2014-09-06 09:17:15,762 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.68 2014-09-06 09:18:00,867 [TriggerTimeRun::09:18] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:18 in trigger event 'Set Night' 2014-09-06 09:18:00,880 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:18:00,882 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:18:00,884 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:18:00,886 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:18:00,888 [TriggerTimeRun::09:18] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:18 in trigger event 'Set Morning' 2014-09-06 09:18:00,921 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:18:00,923 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:18 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:18:00,925 [TriggerTimeRun::09:18] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:18 in trigger event 'Set Afternoon' 2014-09-06 09:18:00,927 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:18:00,970 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:18:00,971 [TriggerTimeRun::09:18] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:18 in trigger event 'Set Evening' 2014-09-06 09:18:00,973 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:18:00,976 [TriggerTimeRun::09:18] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:18 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:18:15,784 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:18:15,786 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:18:15,788 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 49.2 2014-09-06 09:18:15,806 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '49.2' to datatype: FLOAT 2014-09-06 09:18:15,808 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:18:15,830 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 49.2 2014-09-06 09:18:15,832 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":49.2,"group":"values"} } 2014-09-06 09:18:15,865 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 49.2 2014-09-06 09:18:15,883 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:18:15,885 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:18:15,887 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 100.0 2014-09-06 09:18:15,957 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '100.0' to datatype: FLOAT 2014-09-06 09:18:15,985 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:18:15,991 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 100.0 2014-09-06 09:18:15,993 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":100.0,"group":"values"} } 2014-09-06 09:18:16,031 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:18:16,033 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:18:16,035 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 8.58 2014-09-06 09:18:16,037 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '8.58' to datatype: FLOAT 2014-09-06 09:18:16,063 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 100.0 2014-09-06 09:18:16,120 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:18:16,143 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 8.58 2014-09-06 09:18:16,168 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 8.58 2014-09-06 09:18:16,172 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":8.58,"group":"values"} } 2014-09-06 09:18:16,174 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:18:16,188 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:18:16,207 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.68 2014-09-06 09:18:16,224 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.68' to datatype: FLOAT 2014-09-06 09:18:16,226 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:18:16,254 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.68 2014-09-06 09:18:16,262 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.68,"group":"values"} } 2014-09-06 09:18:16,291 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.68 2014-09-06 09:19:00,897 [TriggerTimeRun::09:19] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:19 in trigger event 'Set Night' 2014-09-06 09:19:00,903 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:19:00,905 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:19:00,907 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:19:00,924 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:19:00,925 [TriggerTimeRun::09:19] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:19 in trigger event 'Set Morning' 2014-09-06 09:19:00,954 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:19:00,956 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:19 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:19:00,958 [TriggerTimeRun::09:19] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:19 in trigger event 'Set Afternoon' 2014-09-06 09:19:00,966 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:19:00,968 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:19:00,985 [TriggerTimeRun::09:19] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:19 in trigger event 'Set Evening' 2014-09-06 09:19:00,987 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:19:01,012 [TriggerTimeRun::09:19] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:19 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:19:16,375 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:19:16,376 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:19:16,387 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 49.2 2014-09-06 09:19:16,401 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '49.2' to datatype: FLOAT 2014-09-06 09:19:16,403 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:19:16,429 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 49.2 2014-09-06 09:19:16,432 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":49.2,"group":"values"} } 2014-09-06 09:19:16,440 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 49.2 2014-09-06 09:19:16,458 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:19:16,465 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:19:16,466 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 100.0 2014-09-06 09:19:16,468 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '100.0' to datatype: FLOAT 2014-09-06 09:19:16,515 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:19:16,535 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 100.0 2014-09-06 09:19:16,564 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 100.0 2014-09-06 09:19:16,564 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":100.0,"group":"values"} } 2014-09-06 09:19:16,565 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:19:16,590 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:19:16,592 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 9.73 2014-09-06 09:19:16,594 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '9.73' to datatype: FLOAT 2014-09-06 09:19:16,637 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:19:16,678 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 9.73 2014-09-06 09:19:16,681 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":9.73,"group":"values"} } 2014-09-06 09:19:16,690 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 9.73 2014-09-06 09:19:16,702 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:19:16,704 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:19:16,706 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.67 2014-09-06 09:19:16,737 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.67' to datatype: FLOAT 2014-09-06 09:19:16,754 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:19:16,774 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.67 2014-09-06 09:19:16,796 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.67,"group":"values"} } 2014-09-06 09:19:16,808 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.67 2014-09-06 09:19:28,582 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.8 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 09:19:50,064 [Thread-137] ERROR org.pidome.driver.driver.nativeMySensorsDriver14.NativeMySensorsDriver14 - Faulty data or method handling: Index: 20, Size: 20 (0;0;3;0;9;read: 22-22-0 s=0,c=1,t=1,pt=7,l=5:19.2 22;0;1;0;1;19.2 ) 2014-09-06 09:20:01,317 [TriggerTimeRun::09:20] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:20 in trigger event 'Set Night' 2014-09-06 09:20:01,319 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:20:01,325 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:20:01,332 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 00:00(00:00) 2014-09-06 09:20:01,334 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 06:00(06:00) 2014-09-06 09:20:01,375 [TriggerTimeRun::09:20] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:20 in trigger event 'Set Morning' 2014-09-06 09:20:01,377 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 05:59(05:59) 2014-09-06 09:20:01,404 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: true for value 09:20 in equation daytime_FIXED_ALL with matchtype LESSTHEN with matchsubject 12:00(12:00) 2014-09-06 09:20:01,406 [TriggerTimeRun::09:20] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:20 in trigger event 'Set Afternoon' 2014-09-06 09:20:01,408 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:20:01,424 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 11:59(11:59) 2014-09-06 09:20:01,426 [TriggerTimeRun::09:20] DEBUG org.pidome.server.services.triggerservice.TriggerEvent - Checking for value match: daytime_FIXED_ALL - 09:20 in trigger event 'Set Evening' 2014-09-06 09:20:01,455 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:20:01,457 [TriggerTimeRun::09:20] TRACE org.pidome.server.services.triggerservice.rules.RuleSubject - Returning new result: false for value 09:20 in equation daytime_FIXED_ALL with matchtype GREATERTHEN with matchsubject 17:59(17:59) 2014-09-06 09:20:01,597 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.7 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 09:20:17,297 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:20:17,304 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: procheat - 4 bytes 2014-09-06 09:20:17,306 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: procheat - 49.2 2014-09-06 09:20:17,307 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '49.2' to datatype: FLOAT 2014-09-06 09:20:17,309 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, procheat, {} 2014-09-06 09:20:17,341 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with procheat containing 49.2 2014-09-06 09:20:17,343 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"procheat","id":1,"value":49.2,"group":"values"} } 2014-09-06 09:20:17,354 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - procheat - 49.2 2014-09-06 09:20:17,368 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:20:17,399 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: cpuusage - 4 bytes 2014-09-06 09:20:17,404 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: cpuusage - 100.0 2014-09-06 09:20:17,406 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '100.0' to datatype: FLOAT 2014-09-06 09:20:17,433 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, cpuusage, {} 2014-09-06 09:20:17,442 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with cpuusage containing 100.0 2014-09-06 09:20:17,466 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"cpuusage","id":1,"value":100.0,"group":"values"} } 2014-09-06 09:20:17,471 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:20:17,472 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: memusage - 4 bytes 2014-09-06 09:20:17,474 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: memusage - 10.86 2014-09-06 09:20:17,526 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '10.86' to datatype: FLOAT 2014-09-06 09:20:17,528 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, memusage, {} 2014-09-06 09:20:17,522 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - cpuusage - 100.0 2014-09-06 09:20:17,555 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with memusage containing 10.86 2014-09-06 09:20:17,557 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"memusage","id":1,"value":10.86,"group":"values"} } 2014-09-06 09:20:17,576 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.peripherals.hardware.PeripheralHardwareDriver - Data received from device: 4 byte(s) 2014-09-06 09:20:17,578 [pool-3-thread-1] TRACE org.pidome.driver.driver.nativeServerDriver.NativeServerDriver - Got from hardware driver: diskspace - 4 bytes 2014-09-06 09:20:17,596 [pool-3-thread-1] DEBUG org.pidome.driver.device.pidomeServerDevice.PidomeServerDevice - Handling: diskspace - 19060.66 2014-09-06 09:20:17,634 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.devicestructure.DeviceControl - Converting '19060.66' to datatype: FLOAT 2014-09-06 09:20:17,647 [pool-3-thread-1] TRACE org.pidome.server.connector.drivers.devices.Device - Called dispatchClientData: values, diskspace, {} 2014-09-06 09:20:17,644 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - memusage - 10.86 2014-09-06 09:20:17,676 [pool-5-thread-1] DEBUG org.pidome.server.connector.plugins.hooks.DeviceHook - Handling for device 1 with diskspace containing 19060.66 2014-09-06 09:20:17,688 [pool-5-thread-1] TRACE org.pidome.server.services.socketservice.SocketServiceConnectionPool - BROADCAST_ALL: {"jsonrpc":"2.0","method":"DeviceService.sendDevice","params": {"control":"diskspace","id":1,"value":19060.66,"group":"values"} } 2014-09-06 09:20:17,769 [pool-6-thread-1] DEBUG org.pidome.server.system.hardware.devices.Devices - Got storage data: 1 - values - diskspace - 19060.66 2014-09-06 09:20:35,403 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;0;1;0;0;15.8 in device Study, error: Group 'S_DOOR' does not exist 2014-09-06 09:20:35,406 [Thread-137] ERROR org.pidome.driver.device.pidomeNativeMySensorsDevice14.PidomeNativeMySensorsDevice14 - Error handling: 20;1;1;0;0;16.4 in device Study, error: Group 'S_MOTION' does not exist