PiDome - Waiting for gateway



  • Hi all
    I have a Raspberry Pi 3 running the PiDome Controller and the Raspberry Pi Serial gateway as per https://www.mysensors.org/build/raspberry
    My configuration for the Serial gateway is as follow

    root@mmm_gateway:~# cd /opt/temp/mmm_gateway/MySensors/examples_linux/
    root@mmm_gateway:/opt/temp/mmm_gateway/MySensors/examples_linux# cat mysGateway.cpp 
    #include <iostream>
    #include <cstdio>
    #include <unistd.h>
    
    // For more options run ./configure --help
    
    // Config file
    //#define MY_LINUX_CONFIG_FILE "/etc/mysensors.dat"
    
    // How many clients should be able to connect to this gateway (default 1)
    #define MY_GATEWAY_MAX_CLIENTS 10
    
    // Serial config
    // Enable this if you are using an Arduino connected to the USB
    //#define MY_LINUX_SERIAL_PORT "/dev/ttyACM0"
    // Enable this if you need to connect to a controller running on the same device
    #define MY_IS_SERIAL_PTY
    // Choose a symlink name for the PTY device
    #define MY_LINUX_SERIAL_PTY "/dev/ttyMySensorsGateway"
    //MySensorsGateway
    // Grant access to the specified system group for the serial device
    #define MY_LINUX_SERIAL_GROUPNAME "tty"
    
    // MQTT options
    //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
    //#define MY_PORT 1883
    //#define MY_MQTT_CLIENT_ID "mysensors-1"
    //#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
    //#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
    
    // Enable these if your MQTT broker requires usenrame/password
    //#define MY_MQTT_USER "username"
    //#define MY_MQTT_PASSWORD "password"
    
    // Flash leds on rx/tx/err
    #define MY_DEFAULT_ERR_LED_PIN 12  // Error LED pin
    #define MY_DEFAULT_RX_LED_PIN  16  // Receive LED pin
    #define MY_DEFAULT_TX_LED_PIN  18  // Transmit LED pin
    // Inverse the blinking feature
    //#define MY_WITH_LEDS_BLINKING_INVERSE
    
    // Enable software signing
    //#define MY_SIGNING_SOFT
    // Enable signing related debug
    //#define MY_DEBUG_VERBOSE_SIGNING
    // Enable this to request signatures from nodes that in turn request signatures from gateway
    //#define MY_SIGNING_REQUEST_SIGNATURES
    // Enable this to have gateway require all nodes in the network to sign messages sent to it
    // Note: MY_SIGNING_REQUEST_SIGNATURES must also be set
    //#define MY_SIGNING_GW_REQUEST_SIGNATURES_FROM_ALL
    
    #include <MySensors.h>
    
    void setup() { 
    }
    
    void presentation() {
      // Present locally attached sensors here    
    }
    
    void loop() {
      // Send locally attached sensors data here
    }
    root@mmm_gateway:/opt/temp/mmm_gateway/MySensors/examples_linux# 
    
    

    I start the Serial Gateway as follow and it starts successfully

    root@mmm_gateway:/opt/temp/mmm_gateway/MySensors/examples_linux# ./mysGateway -d
    mysGateway: Starting gateway...
    mysGateway: Protocol version - 2.0.1-beta
    mysGateway: MCO:BGN:INIT GW,CP=RNNG---,VER=2.0.1-beta
    mysGateway: TSF:LRT:OK
    mysGateway: TSM:INIT
    mysGateway: TSM:INIT:TSP OK
    mysGateway: TSM:INIT:GW MODE
    mysGateway: TSM:READY
    mysGateway: MCO:REG:NOT NEEDED
    mysGateway: MCO:BGN:STP
    mysGateway: MCO:BGN:INIT OK,ID=0,PAR=0,DIS=0,REG=1
    mysGateway: TSF:MSG:READ,120-120-0,s=1,c=1,t=0,pt=7,l=5,sg=0:26.2
    mysGateway: TSF:MSG:READ,120-120-0,s=2,c=1,t=1,pt=2,l=2,sg=0:38
    mysGateway: TSF:MSG:READ,120-120-0,s=255,c=3,t=0,pt=1,l=1,sg=0:29
    
    

    As you can see there is a temperature sensor on a SenseBender
    The /dev/tty device starts up as well and I can see some information in the file

    ^Cpi@mmm_gateway:~ $ sudo tail -f /dev/ttyMySensorsGateway 
    0;255;3;0;14;Gateway startup complete.
    0;255;0;0;18;2.0.1-beta
    120;1;1;0;0;26.2
    120;2;1;0;1;38
    120;255;3;0;0;29
    120;1;1;0;0;26.2
    120;2;1;0;1;38
    120;1;1;0;0;26.1
    120;2;1;0;1;38
    120;255;3;0;0;29
    106;255;3;0;0;86
    106;255;4;0;0;FFFFFFFFFFFFFFFF0300
    106;255;0;0;17;2.0.0
    106;255;3;0;11;Sensebender Micro
    106;255;3;0;12;1.4
    106;1;0;0;6;
    106;2;0;0;7;
    120;255;3;0;0;25
    120;255;4;0;0;FFFFFFFFFFFFFFFF0300
    120;255;0;0;17;2.0.0
    120;255;3;0;6;0
    120;255;3;0;11;Sensebender Micro
    120;255;3;0;12;1.4
    120;1;0;0;6;
    120;2;0;0;7;
    
    

    The PiDome installation seem to be ok as well, I can stop and start it

    pi@mmm_gateway:~ $ sudo systemctl status pidome-server.service 
    ● pidome-server.service - LSB: PiDome Home Automation/Domotica server.
       Loaded: loaded (/etc/init.d/pidome-server)
       Active: active (running) since Sun 2016-11-13 12:09:45 SAST; 9min ago
      Process: 2809 ExecStart=/etc/init.d/pidome-server start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/pidome-server.service
               ├─ 717 /opt/pidome/pidome-server/jre/bin/java -Xbootclasspath/p:libs/alpn-boot-8.1.7.v20160121.jar -XshowSettings:properties -Dlog4j.configurationFile=config/log4j2.xml -Djava.awt.headless=true -Dfile.encoding=UTF-8 -jar pidome-server.jar
               └─2815 /opt/pidome/pidome-server/jre/bin/java -Xbootclasspath/p:libs/alpn-boot-8.1.7.v20160121.jar -XshowSettings:properties -Dlog4j.configurationFile=config/log4j2.xml -Djava.awt.headless=true -Dfile.encoding=UTF-8 -jar pidome-server.jar
    
    Nov 13 12:09:45 mmm_gateway pidome-server[2809]: Initializing PiDome server, please wait for server start........ starting up.
    Nov 13 12:09:45 mmm_gateway systemd[1]: Started LSB: PiDome Home Automation/Domotica server..
    pi@mmm_gateway:~ $ sudo systemctl stop pidome-server.service 
    pi@mmm_gateway:~ $ sudo systemctl status pidome-server.service 
    ● pidome-server.service - LSB: PiDome Home Automation/Domotica server.
       Loaded: loaded (/etc/init.d/pidome-server)
       Active: inactive (dead) since Sun 2016-11-13 12:19:30 SAST; 4s ago
      Process: 4338 ExecStop=/etc/init.d/pidome-server stop (code=exited, status=0/SUCCESS)
      Process: 2809 ExecStart=/etc/init.d/pidome-server start (code=exited, status=0/SUCCESS)
    
    Nov 13 12:09:45 mmm_gateway pidome-server[2809]: Initializing PiDome server, please wait for server start........ starting up.
    Nov 13 12:09:45 mmm_gateway systemd[1]: Started LSB: PiDome Home Automation/Domotica server..
    Nov 13 12:19:30 mmm_gateway systemd[1]: Stopping LSB: PiDome Home Automation/Domotica server....
    Nov 13 12:19:30 mmm_gateway pidome-server[4338]: Stopping PiDome server, please wait... removing PID file /var/run/pidome.pid, done.
    Nov 13 12:19:30 mmm_gateway systemd[1]: Stopped LSB: PiDome Home Automation/Domotica server..
    pi@mmm_gateway:~ $ sudo systemctl start pidome-server.service 
    pi@mmm_gateway:~ $ sudo systemctl status pidome-server.service 
    ● pidome-server.service - LSB: PiDome Home Automation/Domotica server.
       Loaded: loaded (/etc/init.d/pidome-server)
       Active: active (running) since Sun 2016-11-13 12:19:46 SAST; 1s ago
      Process: 4338 ExecStop=/etc/init.d/pidome-server stop (code=exited, status=0/SUCCESS)
      Process: 4372 ExecStart=/etc/init.d/pidome-server start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/pidome-server.service
               ├─ 717 /opt/pidome/pidome-server/jre/bin/java -Xbootclasspath/p:libs/alpn-boot-8.1.7.v20160121.jar -XshowSettings:properties -Dlog4j.configurationFile=config/log4j2.xml -Djava.awt.headless=true -Dfile.encoding=UTF-8 -jar pidome-server.jar
               └─4378 /opt/pidome/pidome-server/jre/bin/java -Xbootclasspath/p:libs/alpn-boot-8.1.7.v20160121.jar -XshowSettings:properties -Dlog4j.configurationFile=config/log4j2.xml -Djava.awt.headless=true -Dfile.encoding=UTF-8 -jar pidome-server.jar
    
    Nov 13 12:19:46 mmm_gateway pidome-server[4372]: Initializing PiDome server, please wait for server start........ starting up.
    Nov 13 12:19:46 mmm_gateway systemd[1]: Started LSB: PiDome Home Automation/Domotica server..
    pi@mmm_gateway:~ $ 
    
    

    I've defined the custom port, see image
    0_1479032464623_image.png

    But the driver just says waiting for gateway, never changes
    0_1479032524928_image.png

    Even when I turn on the device discovery and cycle the SenseBenders, nothing happens
    0_1479032588376_image.png

    I really like the PiDome interface, but there does not seem to be a lot of information on it, and hence very difficult to troubleshoot, does anyone have an idea on how to fix this please

    Regards



  • Some errors in the logfile on the PiDome that I do not have a clue what they are about

    root@mmm_gateway:/opt/pidome/pidome-server/logs/system# tail -f appLog.txt 
    	2016-11-13 12:24:40,368 [main] WARN  org.pidome.server.PiDomeServerBoot - Running server with security manager disabled. This is the case as long the server is in alpha state.
    2016-11-13 12:24:40,386 [main] WARN  org.pidome.server.PiDomeServerBoot - There is no default locale present in the config file, will default to: en_GB
    2016-11-13 12:24:40,387 [main] INFO  org.pidome.server.PiDomeServerBoot - Starting server with build: 0.1-SNAPSHOT-2016-09-22.698 on platform: Linux (arm)
    2016-11-13 12:24:40,507 [main] INFO  com.zaxxer.hikari.HikariDataSource - DBConnectionPool_PiDomeServer - is starting.
    2016-11-13 12:24:42,455 [main] INFO  org.pidome.misc.utils.TimeUtils - Setting timezone data: Europe/Amsterdam, 51.950000, 4.449999
    2016-11-13 12:24:42,575 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Initializing RPC
    2016-11-13 12:24:42,897 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: PackageService
    2016-11-13 12:24:42,964 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: DashboardService
    2016-11-13 12:24:42,966 [main] ERROR org.pidome.server.services.http.rpc.PidomeJSONRPC - RPC namespace 'JSONService' has been misconfigured!
    2016-11-13 12:24:42,967 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: JSONService
    2016-11-13 12:24:42,995 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: DataModifierService
    2016-11-13 12:24:43,081 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: LocationService
    2016-11-13 12:24:43,122 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: MessengerService
    2016-11-13 12:24:43,170 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: WeatherService
    2016-11-13 12:24:43,222 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: RemotesService
    2016-11-13 12:24:43,281 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: CategoryService
    2016-11-13 12:24:43,320 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: HardwareService
    2016-11-13 12:24:43,355 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: AccessControllerService
    2016-11-13 12:24:43,442 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: ClientService
    2016-11-13 12:24:43,518 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserService
    2016-11-13 12:24:43,536 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: PluginService
    2016-11-13 12:24:43,733 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: DeviceService
    2016-11-13 12:24:43,861 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: MediaService
    2016-11-13 12:24:43,929 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: EventService
    2016-11-13 12:24:43,958 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: UserStatusService
    2016-11-13 12:24:43,997 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: UtilityMeasurementService
    2016-11-13 12:24:44,022 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: GraphService
    2016-11-13 12:24:44,032 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: PlatformService
    2016-11-13 12:24:44,089 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: TriggerService
    2016-11-13 12:24:44,124 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: AutomationRulesService
    2016-11-13 12:24:44,157 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: SystemService
    2016-11-13 12:24:44,195 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: ScenesService
    2016-11-13 12:24:44,226 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: DayPartService
    2016-11-13 12:24:44,272 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: MacroService
    2016-11-13 12:24:44,305 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: PresenceService
    2016-11-13 12:24:44,349 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done initializing RPC namespace: DevicePluginService
    2016-11-13 12:24:44,353 [main] INFO  org.pidome.server.services.http.rpc.PidomeJSONRPC - Done Initializing RPC
    2016-11-13 12:24:44,360 [main] INFO  org.pidome.server.system.extras.SystemExtras - Initializing system extras
    2016-11-13 12:24:44,361 [main] INFO  org.pidome.server.system.extras.SystemExtras - LED notifications setting: false
    2016-11-13 12:24:44,363 [main] INFO  org.pidome.server.system.extras.DataNotificationLeds - Led notification pins are disabled. If you want to enable this got to http://pidome.org on how to enable this.
    2016-11-13 12:24:44,363 [main] INFO  org.pidome.server.system.extras.SystemExtras - Done initializing extras
    2016-11-13 12:24:44,383 [main] INFO  org.pidome.server.system.network.Network - Autodiscovery of network interface addresses
    2016-11-13 12:24:44,409 [main] INFO  org.pidome.server.system.network.Network - Network interface loaded
    2016-11-13 12:24:44,582 [main] INFO  org.pidome.server.system.network.http.HttpServer - Starting 'HTTPS Management Webservice'
    2016-11-13 12:24:46,434 [main] INFO  org.pidome.server.system.network.http.HttpServer - 'HTTPS Management Webservice' started
    2016-11-13 12:24:46,541 [main] INFO  org.pidome.server.services.accesscontrollers.AccesControllersService - Loading access controller devices wrappers
    2016-11-13 12:24:47,112 [main] INFO  org.pidome.server.system.hardware.Hardware - Hardware discovery started
    2016-11-13 12:24:47,131 [main] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Server information layer' hardware driver using saved configuration.
    2016-11-13 12:24:47,134 [main] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'ServerDevicePeripheral' for loading Server information layer.
    2016-11-13 12:24:47,170 [main] INFO  org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Server information layer
    2016-11-13 12:24:47,217 [main] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:47,590 [main] ERROR org.pidome.server.system.hardware.devices.Devices - Problem with loaded device info: null
    java.lang.NullPointerException
    	at java.io.StringReader.<init>(StringReader.java:50) ~[?:1.8.0_91]
    	at org.json.simple.parser.JSONParser.parse(JSONParser.java:79) ~[json-simple-1.1.1.jar:?]
    	at org.json.simple.parser.JSONParser.parse(JSONParser.java:75) ~[json-simple-1.1.1.jar:?]
    	at org.pidome.server.system.hardware.devices.Devices.loadSingleDeviceInstance(Devices.java:325) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.devices.Devices.loadDriverDevices(Devices.java:224) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.devices.Devices.handleDriverEvent(Devices.java:1752) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.drivers.Drivers._fireDriverEvent(Drivers.java:322) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.drivers.Drivers.setPheripheralSoftwareDriver(Drivers.java:132) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.drivers.Drivers.handlePeripheralEvent(Drivers.java:252) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals._firePeripheralEvent(Peripherals.java:513) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals.startPeripheralInitialization(Peripherals.java:348) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals.finalizeDriverInit(Peripherals.java:207) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals.loadDriverByVidPid(Peripherals.java:163) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals.loadPeripheralDriver(Peripherals.java:111) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.Peripherals.hardwareChange(Peripherals.java:459) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.Hardware._fireHardwareEvent(Hardware.java:274) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.Hardware.deviceMutation(Hardware.java:236) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.server.ServerDevices._fireDeviceEvent(ServerDevices.java:57) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.server.ServerDevices.start(ServerDevices.java:63) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.Hardware.discoveryDoneHandler(Hardware.java:280) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.HardwareRoot._fireDiscoveryDoneEvent(HardwareRoot.java:85) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.peripherals.server.ServerDevices.discover(ServerDevices.java:46) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.Hardware.discover(Hardware.java:140) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.system.hardware.Hardware.start(Hardware.java:110) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.services.hardware.DeviceService.start(DeviceService.java:925) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.services.ServiceController.startAllServers(ServiceController.java:172) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    	at org.pidome.server.PiDomeServerBoot.main(PiDomeServerBoot.java:123) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    2016-11-13 12:24:47,619 [main] ERROR org.pidome.server.system.hardware.devices.Devices - Device 'org.pidome.driver.device.pidomeServerDevice', not found in packages or instantiation error: Incorrect device specs loaded: null
    2016-11-13 12:24:47,620 [main] INFO  org.pidome.server.system.hardware.drivers.Drivers - Driver NativeServerDriver on Server information layer on port {Internally used device map} is ready for use
    2016-11-13 12:24:47,709 [USB-discovery] INFO  org.pidome.server.system.hardware.Hardware - Started peripherals discovery on USB
    2016-11-13 12:24:47,710 [Serial-discovery] INFO  org.pidome.server.system.hardware.Hardware - Started peripherals discovery on Serial GPIO
    2016-11-13 12:24:47,720 [I2C-discovery] INFO  org.pidome.server.system.hardware.Hardware - Started peripherals discovery on I2C
    2016-11-13 12:24:47,722 [main] INFO  org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started
    2016-11-13 12:24:47,741 [main] INFO  org.pidome.server.system.userstatus.UserStatusService - Set user status to Awake at 13-11-2016 11:24
    2016-11-13 12:24:47,742 [I2C-discovery] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry GPIO I2C' hardware driver using saved configuration.
    2016-11-13 12:24:47,743 [I2C-discovery] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOI2C' for loading Raspberry GPIO I2C.
    2016-11-13 12:24:47,748 [User-defined-serials-discovery] INFO  org.pidome.server.system.hardware.Hardware - Started user defined serial devices discovery
    2016-11-13 12:24:47,809 [main] INFO  org.pidome.server.system.presence.PresenceService - Set presence to Home at 13-11-2016 11:24
    2016-11-13 12:24:47,850 [main] INFO  org.pidome.server.services.clients.socketservice.SocketService - Client display terminal server has started
    2016-11-13 12:24:47,871 [Serial-discovery] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Raspberry Pi GPIO Serial' hardware driver using saved configuration.
    2016-11-13 12:24:47,873 [Serial-discovery] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'GPIOSerial' for loading Raspberry Pi GPIO Serial.
    2016-11-13 12:24:47,888 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Data modifiers plugin service
    2016-11-13 12:24:47,889 [I2C-discovery] ERROR err - Uncaught exception by Thread[I2C-discovery,5,main]:
    2016-11-13 12:24:47,897 [I2C-discovery] ERROR err - java.lang.NumberFormatException: For input string: "a02082"
    2016-11-13 12:24:47,905 [I2C-discovery] ERROR err - 	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
    2016-11-13 12:24:47,906 [I2C-discovery] ERROR err - 	at java.lang.Integer.parseInt(Integer.java:580)
    2016-11-13 12:24:47,907 [I2C-discovery] ERROR err - 	at java.lang.Integer.parseInt(Integer.java:615)
    2016-11-13 12:24:47,909 [I2C-discovery] ERROR err - 	at org.pidome.driver.peripherals.pidomeNativeI2CBus.PidomeNativeI2CBus.initDriver(PidomeNativeI2CBus.java:47)
    2016-11-13 12:24:47,915 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.PeripheralController.initHardwareDriver(PeripheralController.java:231)
    2016-11-13 12:24:47,924 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.PeripheralController.startPeripheralInitialization(PeripheralController.java:194)
    2016-11-13 12:24:47,926 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.Peripherals.startPeripheralInitialization(Peripherals.java:343)
    2016-11-13 12:24:47,919 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Media plugin service
    2016-11-13 12:24:47,928 [Serial-discovery] INFO  org.pidome.server.system.hardware.Hardware - Done peripherals discovery on Serial GPIO
    2016-11-13 12:24:47,928 [User-defined-serials-discovery] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'MySensors_Serial_Port' hardware driver using saved configuration.
    2016-11-13 12:24:47,929 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.Peripherals.finalizeDriverInit(Peripherals.java:207)
    2016-11-13 12:24:47,931 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.Peripherals.loadDriverByVidPid(Peripherals.java:163)
    2016-11-13 12:24:47,932 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.Peripherals.loadPeripheralDriver(Peripherals.java:111)
    2016-11-13 12:24:47,933 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.Peripherals.hardwareChange(Peripherals.java:459)
    2016-11-13 12:24:47,934 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.Hardware._fireHardwareEvent(Hardware.java:274)
    2016-11-13 12:24:47,935 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.Hardware.deviceMutation(Hardware.java:236)
    2016-11-13 12:24:47,936 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.i2c.I2CDevices._fireDeviceEvent(I2CDevices.java:57)
    2016-11-13 12:24:47,937 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.i2c.I2CDevices.start(I2CDevices.java:63)
    2016-11-13 12:24:47,938 [User-defined-serials-discovery] INFO  org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Initializing hardware driver: PiDome User custom serial device
    2016-11-13 12:24:47,939 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.Hardware.discoveryDoneHandler(Hardware.java:280)
    2016-11-13 12:24:47,961 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.HardwareRoot._fireDiscoveryDoneEvent(HardwareRoot.java:85)
    2016-11-13 12:24:47,962 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.peripherals.i2c.I2CDevices.discover(I2CDevices.java:46)
    2016-11-13 12:24:47,963 [I2C-discovery] ERROR err - 	at org.pidome.server.system.hardware.Hardware$3.run(Hardware.java:167)
    2016-11-13 12:24:47,973 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Utility usage plugin service
    2016-11-13 12:24:48,007 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Messenger plugin service
    2016-11-13 12:24:48,045 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Remotes plugin service
    2016-11-13 12:24:48,125 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Devices plugin service
    2016-11-13 12:24:48,143 [User-defined-serials-discovery] INFO  org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Serial running in noOp mode (Connection handled by peripheral software driver instead of peripheral hardware driver) on port '/dev/ttyMySensorsGateway': false
    2016-11-13 12:24:48,145 [User-defined-serials-discovery] INFO  org.pidome.driver.peripherals.pidomeNativeUSBSerial.PidomeNativeUSBSerial - Starting hardware driver: PiDome User custom serial device
    2016-11-13 12:24:48,149 [main] INFO  org.pidome.server.services.plugins.PluginService - Starting plugin service: Weather plugins service
    2016-11-13 12:24:48,162 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.services.plugins.PluginService - Starting 'MQTT Server hook' (PiDome MQTT Broker) with the 'Devices plugin service' plugin service
    2016-11-13 12:24:48,204 [User-defined-serials-discovery] INFO  org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: MySensors_Serial_Port
    2016-11-13 12:24:48,223 [PluginService::Start:Weather plugins service] INFO  org.pidome.server.services.plugins.PluginService - Starting 'PiDome Buienradar' (PiDome Buienradar) with the 'Weather plugins service' plugin service
    2016-11-13 12:24:48,394 [User-defined-serials-discovery] INFO  org.pidome.server.system.hardware.drivers.Drivers - Driver NativeMySensorsDriver14 on MySensors_Serial_Port on port /dev/ttyMySensorsGateway is ready for use
    2016-11-13 12:24:48,396 [User-defined-serials-discovery] INFO  org.pidome.server.system.hardware.Hardware - Done user defined serial devices discovery
    2016-11-13 12:24:48,414 [main] INFO  org.pidome.server.services.network.BroadcastService - Broadcast message: '{"SRV":"192.168.1.48","UP":8080,"DP":11000,"UA":"SRV","SSL":true,"DA":"SRV"}'
    2016-11-13 12:24:48,417 [SERVICE:BroadcastServer] INFO  org.pidome.server.services.network.BroadcastService - Started, sending every 7.5 seconds
    2016-11-13 12:24:48,706 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Trying to load 'Emulator for: PiDome MQTT Broker' hardware driver using saved configuration.
    2016-11-13 12:24:48,707 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.peripherals.Peripherals - Using vid 'PiDome' and pid 'HwPluginEmu' for loading Emulator for: PiDome MQTT Broker.
    2016-11-13 12:24:48,730 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.drivers.Drivers - Loading peripheral software driver for: Emulator for: PiDome MQTT Broker
    2016-11-13 12:24:48,789 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting plugin links: MQTT Server hook
    2016-11-13 12:24:48,790 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.drivers.Drivers - Is emulator plugin, setting device instance link
    2016-11-13 12:24:48,794 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.drivers.Drivers - Assigning the next installed devices to emulator plugin 'MQTT Server hook': {}
    2016-11-13 12:24:48,797 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.system.hardware.drivers.Drivers - Driver PidomeMQTTBrokerDriver on Emulator for: PiDome MQTT Broker on port 71eb159d-9539-49fb-82be-3a74ac94dc0b is ready for use
    2016-11-13 12:24:48,896 [PluginService::Start:Devices plugin service] INFO  io.moquette.server.Server - Persistent store file: 
    2016-11-13 12:24:48,899 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,097 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,142 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,189 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,208 [DisplayClientSocketSSL] ERROR org.pidome.server.services.clients.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_91]
    	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[?:1.8.0_91]
    	at java.net.ServerSocket.bind(ServerSocket.java:375) ~[?:1.8.0_91]
    	at java.net.ServerSocket.<init>(ServerSocket.java:237) ~[?:1.8.0_91]
    	at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:181) ~[?:1.8.0_91]
    	at sun.security.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:140) ~[?:1.8.0_91]
    	at sun.security.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:95) ~[?:1.8.0_91]
    	at org.pidome.server.services.clients.socketservice.SocketService$1.run(SocketService.java:106) [pidome-server.jar:0.1-SNAPSHOT-2016-09-22.698]
    2016-11-13 12:24:49,239 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,271 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,339 [USB-discovery] INFO  org.pidome.server.system.hardware.peripherals.usb.USBDevices - USB listener started
    2016-11-13 12:24:49,340 [USB-discovery] INFO  org.pidome.server.system.hardware.Hardware - Done peripherals discovery on USB
    2016-11-13 12:24:49,352 [Thread-18] ERROR org.pidome.server.system.hardware.devices.Devices - Device sql error: no such column: 'modifiers'
    2016-11-13 12:24:49,355 [Rasp USB Monitor] INFO  org.pidome.server.system.hardware.peripherals.usb.linux.RaspUsb - Usb listener started
    2016-11-13 12:24:49,464 [Thread-18] INFO  org.pidome.server.services.automations.AutomationRules - Loaded rule: CPU usage
    2016-11-13 12:24:49,930 [PluginService::Start:Devices plugin service] INFO  io.moquette.spi.impl.SimpleMessaging - Starting without ACL definition
    2016-11-13 12:24:49,981 [PluginService::Start:Devices plugin service] INFO  io.moquette.server.netty.NettyAcceptor - Server binded host: 192.168.1.48, port: 1883
    2016-11-13 12:24:49,991 [PluginService::Start:Devices plugin service] ERROR org.pidome.plugins.mqtt.pidomeMQTTBroker.PluginBrokerRunner - Could not start MQTT Service using port 1883: Address already in use
    java.net.BindException: Address already in use
    	at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_91]
    	at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_91]
    	at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_91]
    	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_91]
    	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[?:1.8.0_91]
    	at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:543) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1254) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:488) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:473) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:965) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:243) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:360) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:339) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:742) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:145) ~[netty-all-4.1.0.Final.jar:4.1.0.Final]
    	at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_91]
    2016-11-13 12:24:49,997 [PluginService::Start:Devices plugin service] INFO  org.pidome.server.services.plugins.PluginService - Started plugin: MQTT Server hook
    2016-11-13 12:24:50,313 [PluginService::Start:Weather plugins service] INFO  org.pidome.server.services.plugins.PluginService - Started plugin: PiDome Buienradar
    2016-11-13 12:25:00,582 [TriggerTimeRun::11:25] INFO  org.pidome.server.services.triggerservice.TriggerEvent - Executing trigger actions for trigger: Set Morning
    2016-11-13 12:25:00,589 [TriggerTimeRun::11:25] INFO  org.pidome.server.system.dayparts.DayPartsService - Set daypart to Morning at 13-11-2016 11:25
    


  • I guess PiDome is dead? I see no more activity on PiDome?


  • Admin

    Maybe you get more luck by posting on the PIDome forum?

    http://forum.pidome.org/



  • @hek Thanks will do


Log in to reply
 

307
Online

6.7k
Users

7.6k
Topics

80.4k
Posts

Looks like your connection to MySensors Forum was lost, please wait while we try to reconnect.