Problem with Everspring SP103 in OH2

IN the process of migrating fully to OH2 and getting the last pieces to work - I still struggle with one of my Zwave devices; an Everspring SP103 motion detector.
It worked well with the same USB controller in OH1 - and OH2 also recognizes that a device exist - but just lists it as “unknown device” in the things-list (PaperUI and Habmin).

When looking at the log entries - I see that it does indeed get recognized as an SP103 - but still it shows as “unknown”. I have had it running overnight and have now just also tried to force i to wake up (tamper switch press) - but no resolve…

Anyone who can see/guess what is wrong here? I would really like this working - as it turns on our outdoor light in the driveway :wink:

Zwave Log:

2017-02-01 12:18:15.139 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 07 86 12 06 03 1C 01 04 
2017-02-01 12:18:15.139 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:APP_VERSION)
2017-02-01 12:18:15.139 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class VERSION
2017-02-01 12:18:15.140 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 8: Received COMMAND_CLASS_VERSION command V0
2017-02-01 12:18:15.140 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 8: Process Version Report
2017-02-01 12:18:15.140 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 8: Library Type        = 6 (Routing Slave)
2017-02-01 12:18:15.140 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 8: Protocol Version    = 3.28
2017-02-01 12:18:15.140 [DEBUG] [ommandclass.ZWaveVersionCommandClass] - NODE 8: Application Version = 1.4
2017-02-01 12:18:15.141 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Config, dest=8, callback=5, payload=08 02 86 11 
2017-02-01 12:18:15.141 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 07 86 12 06 03 1C 01 04 
2017-02-01 12:18:15.141 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=5, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
2017-02-01 12:18:15.141 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - APP_VERSION: Transaction complete (SendData:Request) success(true)
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - checking initialisation queue. Queue size 1.
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - message removed from queue. Queue size 0.
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - APP_VERSION: queue length(0), free to send(true)
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: loop - APP_VERSION try 1: stageAdvanced(false)
2017-02-01 12:18:15.142 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - advancing to DISCOVERY_COMPLETE
2017-02-01 12:18:15.143 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
2017-02-01 12:18:15.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery completed
2017-02-01 12:18:15.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:stelpro_stzw402_00_000
2017-02-01 12:18:15.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:everspring_sm103_00_000
2017-02-01 12:18:15.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:philio_psr04_00_000
2017-02-01 12:18:15.143 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:qubino_zmnhcd_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:qubino_zmnhcd_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:benext_p1dongle_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:nodon_softremote_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:cooper_rf9542_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgwp101_00_000
2017-02-01 12:18:15.144 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:reitz_05431_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:intermatic_ha05_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw099_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw099_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw099_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw099_00_000
2017-02-01 12:18:15.145 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:goodway_td1311_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:popp_005107_01_003
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_wcd2_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:evolve_t100_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgpb101_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgpb101_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgpb101_00_000
2017-02-01 12:18:15.146 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:reitz_06436_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_kfob_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_kfob_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_kfob_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_kfob_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fakro_zws12_00_000
2017-02-01 12:18:15.147 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fakro_zws12_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:ge_ge12725_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw095_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw095_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:homeseer_hswd100_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:remotec_zfm80_00_000
2017-02-01 12:18:15.148 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgs212_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:fibaro_fgs212_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:everspring_st814_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:rcs_tbz48_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_dsc06_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:intermatic_ha01c_00_000
2017-02-01 12:18:15.149 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:innovus_smartpower_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:wintop_ishutter_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:domitech_ze27_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:tkb_tz66d_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:danfoss_lcz251_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:cooper_rf9500_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_dsb29_00_000
2017-02-01 12:18:15.150 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_dsb29_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:reitz_064394_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw100_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw100_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw100_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:shenzhen_motionsensorin_00_000
2017-02-01 12:18:15.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:ge_zw4005_00_000
2017-02-01 12:18:15.152 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:popp_05438_00_000
2017-02-01 12:18:15.152 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:wintop_multisensor_00_000
2017-02-01 12:18:15.152 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:everspring_ad146_00_000
2017-02-01 12:18:15.152 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:intermatic_ca8900_00_000
2017-02-01 12:18:15.152 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:trane_xr524_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:leviton_vri06_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:leviton_vri06_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:benext_plugindimmer_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_dsc25_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:qubino_zmnhja_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:act_zir010_00_000
2017-02-01 12:18:15.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw088_01_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw088_01_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:aeon_zw088_01_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:devolo_phpse02_00_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:shenzhen_doorwindowsensor_00_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:prodrive_ed20_00_000
2017-02-01 12:18:15.154 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:philio_pst02b_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:mcohome_mhs411_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:shenzhen_motionsensor_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:philio_psm02_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:leviton_vrs15_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:leviton_vrs15_00_000
2017-02-01 12:18:15.155 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:ge_zw3101_00_000
2017-02-01 12:18:15.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:greenwave_gwpn6_00_000
2017-02-01 12:18:15.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:vision_zd2105_00_000
2017-02-01 12:18:15.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:yale_yrd120_00_000
2017-02-01 12:18:15.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:zwaveme_zme05431_00_000
2017-02-01 12:18:15.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Checking zwave:everspring_sp103_00_000
2017-02-01 12:18:15.157 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery resolved to thingType zwave:everspring_sp103_00_000
2017-02-01 12:18:15.157 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2017-02-01 12:18:15.158 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: loop - DISCOVERY_COMPLETE try 0: stageAdvanced(true)
2017-02-01 12:18:15.158 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 8: Serialise aborted as static stages not complete
2017-02-01 12:18:15.158 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - advancing to VERSION
2017-02-01 12:18:15.158 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent

I also have two ot those, and have previously upgraded from OH1 to OH2. I haven’t had any problems with this device.
My best guess is that Unknown Device means that openHAB hasn’t found out what device it is yet. As far as I remember they wake up very seldom so it can potential take long time, so I would suggest that you help it. If you do something like this (I assume that the inclusion is done in OH1):

  1. Empty all your Zwave logfiles (I suggest that you keep zwave logging in its own file) Make sure logging is debug
  2. (Re)start openHAB,
  3. Go to PaperUI and search for the node (just one of them).
  4. Make sure you wake up the node frequently. There should now come some logging for the node.
  5. If everythhing turns out as we hope it will manage to configure things. But have patience…

Ok - deleted the node, changed batteries in the device, made a new inclusion - this time not using the button on my Aeontec G5 stick - but using the seperate tool they provide, then stick back in my OH2 server, OH2 restart and then…

The Everspring SP103 popped up with a new node number in PaperUI and Habmin - and the channels are selectable.

I have now moved the device back out in my driveway where it used to sit - and it is still marked as “green” in Habmin - but have not managed to send me any motion alerts or anything else from the channels (alarm, batterylevel etc).

I will let it sit for a day or two. I guess it has to go through standard network heal and figure out that the Zwave devices which seem “near” as it was included, are not nessesarily in reach in its normal location.

I am keeping my fingers crossed :wink:

Thanks for the positive confirmation that it should work - as this makes it much easier locating the problem…

Hmm - the device is still on the network - but I dont see any triggers when movement occur. Also, battery and (tamper)alarms dos not show either. When looking at the “neighbours” list - it seems that it has never updated this after I moved it back to its normal location - which could explain something;

it is sitting somewhere without direct contact to the controller and have to jump through other zwave devices to get there - but somehow it never updates that.

Anyone have any ideas how this could be forced ?

Again, it worked well in OH1 with the same controller…

Have you tried to select the node in Habmain and then select Heal Device from the menu? I believe that it then will try to update the network path.
What is the distance from your controller to the unit?
How many nodes do you have in your network?
How many nodes is powered (eg. nodes that can route)

I have seen mysterious things in my network earlier, at that time I had like 20 battery devices and 2 powered devices. After adding more powered devices I have seen a more stable network.

As fas as I remeber I wasn’t really impressed off the range that the SP103 can see the controller, You could eventually try to move it a closer to your controller and then see if that helps?