SP103 not working in test app on Homey V5.0

[marcus-karlsson]

SP103 used to work in old App prior to SDK3.
Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm.
If I add SP103 as generic zwave device it reports motion by turning device on.

I see these events in the log when paired as everspring SP103 device
:
2020-11-03T14:13:06.584Z
Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff
2020-11-03T14:13:06.584Z
Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255}
2020-11-03T14:13:06.799Z
Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff
2020-11-03T14:13:06.799Z
Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255}
2020-11-03T14:13:06.889Z
Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff
2020-11-03T14:13:06.890Z
Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255}
Filter

[ralfvd]

Can you submit a app diagnostic report after a motion detection? This can be done via the app settings. Then I can see how the app responds to the event. Thanks!

…

On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson ***@***.***> wrote: SP103 used to work in old App prior to SDK3. Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. If I add SP103 as generic zwave device it reports motion by turning device on. I see these events in the log when paired as everspring SP103 device : 2020-11-03T14:13:06.584Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.584Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} 2020-11-03T14:13:06.799Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.799Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} 2020-11-03T14:13:06.889Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.890Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} Filter — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm and after that triggered tamper switch.Then ran diagnostics..Device ID in zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd <notifications@github.com> wrote: Can you submit a app diagnostic report after a motion detection? This can be done via the app settings. Then I can see how the app responds to the event. Thanks! On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson <notifications@github.com> wrote:

SP103 used to work in old App prior to SDK3. Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. If I add SP103 as generic zwave device it reports motion by turning device on. I see these events in the log when paired as everspring SP103 device : 2020-11-03T14:13:06.584Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.584Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} 2020-11-03T14:13:06.799Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.799Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} 2020-11-03T14:13:06.889Z Node[80]: Received application command for COMMAND_CLASS_BASIC, data: 0x01ff 2020-11-03T14:13:06.890Z Node[80]: [COMMAND_CLASS_BASIC] {"Value (Raw)":{"type":"Buffer","data":[255]},"Value":255} Filter — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> .

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[ralfvd]

Hi, I've changed some code for SP103 motion trigger (not the tamper alarm yet). I don't have the device myself, so the app might crash on usage. Version 2.1.0 is now available as test, let me know if that works for you. Then I can try to add the tamper alarm as well. Thanks! Regards On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson <notifications@github.com> wrote:

…

Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm and after that triggered tamper switch.Then ran diagnostics..Device ID in zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < ***@***.***> wrote: Can you submit a app diagnostic report after a motion detection? This can be done via the app settings. Then I can see how the app responds to the event. Thanks! On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson ***@***.***> wrote: > SP103 used to work in old App prior to SDK3. > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. > If I add SP103 as generic zwave device it reports motion by turning device > on. > > I see these events in the log when paired as everspring SP103 device > : > 2020-11-03T14:13:06.584Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.584Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > 2020-11-03T14:13:06.799Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.799Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > 2020-11-03T14:13:06.889Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.890Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > Filter > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#48>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > . > —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Created a new diagnostic report:   0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to 2.1.0 and removed/paired sp103b a few times. Still not triggering motion alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in zwave log.Regards Marcus On 12 Nov 2020 22:32, ralfvd <notifications@github.com> wrote: Hi, I've changed some code for SP103 motion trigger (not the tamper alarm yet). I don't have the device myself, so the app might crash on usage. Version 2.1.0 is now available as test, let me know if that works for you. Then I can try to add the tamper alarm as well. Thanks! Regards On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson <notifications@github.com> wrote:

Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm and after that triggered tamper switch.Then ran diagnostics..Device ID in zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < ***@***.***> wrote: Can you submit a app diagnostic report after a motion detection? This can be done via the app settings. Then I can see how the app responds to the event. Thanks! On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson ***@***.***> wrote: > SP103 used to work in old App prior to SDK3. > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. > If I add SP103 as generic zwave device it reports motion by turning device > on. > > I see these events in the log when paired as everspring SP103 device > : > 2020-11-03T14:13:06.584Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.584Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > 2020-11-03T14:13:06.799Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.799Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > 2020-11-03T14:13:06.889Z > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > 0x01ff > 2020-11-03T14:13:06.890Z > Node[80]: [COMMAND_CLASS_BASIC] {"Value > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > Filter > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#48>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > . > —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> .

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[ralfvd]

Hi Marcus, I've. built a new version 2.1.3 ; hopefully that will gain more insight. You don't necesarily need to re-pair the devices ; I need to pick up the 255 values, but it is not succeeding so far ;-) Everspring has sometimes a bit of a weird non-standard way of doing things. On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson <notifications@github.com> wrote:

…

Created a new diagnostic report: 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to 2.1.0 and removed/paired sp103b a few times. Still not triggering motion alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in zwave log.Regards Marcus On 12 Nov 2020 22:32, ralfvd ***@***.***> wrote: Hi, I've changed some code for SP103 motion trigger (not the tamper alarm yet). I don't have the device myself, so the app might crash on usage. Version 2.1.0 is now available as test, let me know if that works for you. Then I can try to add the tamper alarm as well. Thanks! Regards On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson ***@***.***> wrote: > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm > and after that triggered tamper switch.Then ran diagnostics..Device ID in > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > ***@***.***> wrote: > Can you submit a app diagnostic report after a motion detection? This can > be done via the app settings. Then I can see how the app responds to the > event. > > Thanks! > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < ***@***.***> > > wrote: > > > SP103 used to work in old App prior to SDK3. > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. > > If I add SP103 as generic zwave device it reports motion by turning > device > > on. > > > > I see these events in the log when paired as everspring SP103 device > > : > > 2020-11-03T14:13:06.584Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.584Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > 2020-11-03T14:13:06.799Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.799Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > 2020-11-03T14:13:06.889Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.890Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > Filter > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <#48>, or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > > > . > > > > > —You are receiving this because you authored the thread.Reply to this > email directly, view it on GitHub, or unsubscribe. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #48 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> > . > —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Still no luck. Sent another diagnostic report:  6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov 2020 09:22, ralfvd <notifications@github.com> wrote: Hi Marcus, I've. built a new version 2.1.3 ; hopefully that will gain more insight. You don't necesarily need to re-pair the devices ; I need to pick up the 255 values, but it is not succeeding so far ;-) Everspring has sometimes a bit of a weird non-standard way of doing things. On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson <notifications@github.com> wrote:

Created a new diagnostic report: 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to 2.1.0 and removed/paired sp103b a few times. Still not triggering motion alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in zwave log.Regards Marcus On 12 Nov 2020 22:32, ralfvd ***@***.***> wrote: Hi, I've changed some code for SP103 motion trigger (not the tamper alarm yet). I don't have the device myself, so the app might crash on usage. Version 2.1.0 is now available as test, let me know if that works for you. Then I can try to add the tamper alarm as well. Thanks! Regards On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson ***@***.***> wrote: > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm > and after that triggered tamper switch.Then ran diagnostics..Device ID in > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > ***@***.***> wrote: > Can you submit a app diagnostic report after a motion detection? This can > be done via the app settings. Then I can see how the app responds to the > event. > > Thanks! > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < ***@***.***> > > wrote: > > > SP103 used to work in old App prior to SDK3. > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion alarm. > > If I add SP103 as generic zwave device it reports motion by turning > device > > on. > > > > I see these events in the log when paired as everspring SP103 device > > : > > 2020-11-03T14:13:06.584Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.584Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > 2020-11-03T14:13:06.799Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.799Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > 2020-11-03T14:13:06.889Z > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > 0x01ff > > 2020-11-03T14:13:06.890Z > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > Filter > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <#48>, or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > > > . > > > > > —You are receiving this because you authored the thread.Reply to this > email directly, view it on GitHub, or unsubscribe. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #48 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> > . > —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ> .

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[ralfvd]

2.1.4 is now available. if this doesn't work, I need to delve deeper into it, and try to simulate the behaviour with one of the Everspring devices I do have in my possession. Fingers crossed ! ;-) On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson <notifications@github.com> wrote:

…

Still no luck. Sent another diagnostic report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov 2020 09:22, ralfvd ***@***.***> wrote: Hi Marcus, I've. built a new version 2.1.3 ; hopefully that will gain more insight. You don't necesarily need to re-pair the devices ; I need to pick up the 255 values, but it is not succeeding so far ;-) Everspring has sometimes a bit of a weird non-standard way of doing things. On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson ***@***.***> wrote: > Created a new diagnostic report: > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > 2.1.0 and removed/paired sp103b a few times. Still not triggering motion > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in zwave > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < ***@***.***> > wrote: > Hi, > > I've changed some code for SP103 motion trigger (not the tamper alarm > yet). > I don't have the device myself, so the app might crash on usage. > > Version 2.1.0 is now available as test, let me know if that works for you. > Then I can try to add the tamper alarm as well. > > Thanks! Regards > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < ***@***.***> > > wrote: > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion alarm > > and after that triggered tamper switch.Then ran diagnostics..Device ID > in > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > ***@***.***> wrote: > > Can you submit a app diagnostic report after a motion detection? This > can > > be done via the app settings. Then I can see how the app responds to the > > event. > > > > Thanks! > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > ***@***.***> > > > > wrote: > > > > > SP103 used to work in old App prior to SDK3. > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > alarm. > > > If I add SP103 as generic zwave device it reports motion by turning > > device > > > on. > > > > > > I see these events in the log when paired as everspring SP103 device > > > : > > > 2020-11-03T14:13:06.584Z > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > > 0x01ff > > > 2020-11-03T14:13:06.584Z > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > 2020-11-03T14:13:06.799Z > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > > 0x01ff > > > 2020-11-03T14:13:06.799Z > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > 2020-11-03T14:13:06.889Z > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, data: > > > 0x01ff > > > 2020-11-03T14:13:06.890Z > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > Filter > > > > > > — > > > You are receiving this because you are subscribed to this thread. > > > Reply to this email directly, view it on GitHub > > > <#48>, or unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > > > > > > . > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > email directly, view it on GitHub, or unsubscribe. > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < > #48 (comment)>, > > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> > > > . > > > > > —You are receiving this because you authored the thread.Reply to this > email directly, view it on GitHub, or unsubscribe. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #48 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ> > . > —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Well, Crossing the fingers made all the difference. Now it works. Thanks! Of course One always want more so now it would be nice to have the tamper switch working. That is COMMAN_CLASS_ALARM 2020-11-13T09:20:57.391Z Node[92]: Received application command for COMMAND_CLASS_ALARM, data: 0x0501112020-11-13T09:20:57.392Z Node[92]: [COMMAND_CLASS_ALARM] {"Alarm Type (Raw)":{"type":"Buffer","data":[1]},"Alarm Type":1,"Alarm Level (Raw)":{"type":"Buffer","data":[17]},"Alarm Level":17} Regards Marcus 13 november 2020 10:12:29 +01:00, skrev ralfvd <notifications@github.com>:

…

2.1.4 is now available. if this doesn't work, I need to delve deeper into it, and try to simulate the behaviour with one of the Everspring devices I do have in my possession. Fingers crossed ! ;-) On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson ***@***.***> wrote: > Still no luck. Sent another diagnostic > report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov 2020 > 09:22, ralfvd ***@***.***> wrote: > Hi Marcus, > > I've. built a new version 2.1.3 ; hopefully that will gain more insight. > You don't necesarily need to re-pair the devices ; I need to pick up the > 255 values, but it is not succeeding so far ;-) Everspring has sometimes a > bit of a weird non-standard way of doing things. > > On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson ***@***.***> > > wrote: > > > Created a new diagnostic report: > > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > > 2.1.0 and removed/paired sp103b a few times. Still not triggering motion > > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in > zwave > > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < > ***@***.***> > > wrote: > > Hi, > > > > I've changed some code for SP103 motion trigger (not the tamper alarm > > yet). > > I don't have the device myself, so the app might crash on usage. > > > > Version 2.1.0 is now available as test, let me know if that works for > you. > > Then I can try to add the tamper alarm as well. > > > > Thanks! Regards > > > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < > ***@***.***> > > > > wrote: > > > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion > alarm > > > and after that triggered tamper switch.Then ran diagnostics..Device ID > > in > > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > > ***@***.***> wrote: > > > Can you submit a app diagnostic report after a motion detection? This > > can > > > be done via the app settings. Then I can see how the app responds to > the > > > event. > > > > > > Thanks! > > > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > > ***@***.***> > > > > > > wrote: > > > > > > > SP103 used to work in old App prior to SDK3. > > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > > alarm. > > > > If I add SP103 as generic zwave device it reports motion by turning > > > device > > > > on. > > > > > > > > I see these events in the log when paired as everspring SP103 device > > > > : > > > > 2020-11-03T14:13:06.584Z > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > data: > > > > 0x01ff > > > > 2020-11-03T14:13:06.584Z > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > 2020-11-03T14:13:06.799Z > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > data: > > > > 0x01ff > > > > 2020-11-03T14:13:06.799Z > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > 2020-11-03T14:13:06.889Z > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > data: > > > > 0x01ff > > > > 2020-11-03T14:13:06.890Z > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > Filter > > > > > > > > — > > > > You are receiving this because you are subscribed to this thread. > > > > Reply to this email directly, view it on GitHub > > > > <#48>, or > unsubscribe > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ> > > > > > > > > > > . > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > email directly, view it on GitHub, or unsubscribe. > > > > > > — > > > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > > > < > > > #48 (comment)>, > > > > > > or unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ> > > > > > > . > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > email directly, view it on GitHub, or unsubscribe. > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < > #48 (comment)>, > > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ> > > > . > > > > > —You are receiving this because you authored the thread.Reply to this > email directly, view it on GitHub, or unsubscribe. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#48 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALLQM7F2PZXLW2P3PBD5L3DSPTZ73ANCNFSM4TTXRZNQ>.

[ralfvd]

Great! I will also take a look at the tamper alarm. If I remember correctly, I had to disable that in a previous version as the reports of the sp103 weren’t too reliable. But we’ll give it another go! Can you submit one more diagnostic with the motion alarm working? Thanks for the help! On Fri, 13 Nov 2020 at 11:06, marcus-karlsson <notifications@github.com> wrote:

…

Well, Crossing the fingers made all the difference. Now it works. Thanks! Of course One always want more so now it would be nice to have the tamper switch working. That is COMMAN_CLASS_ALARM 2020-11-13T09:20:57.391Z Node[92]: Received application command for COMMAND_CLASS_ALARM, data: 0x0501112020-11-13T09:20:57.392Z Node[92]: [COMMAND_CLASS_ALARM] {"Alarm Type (Raw)":{"type":"Buffer","data":[1]},"Alarm Type":1,"Alarm Level (Raw)":{"type":"Buffer","data":[17]},"Alarm Level":17} Regards Marcus 13 november 2020 10:12:29 +01:00, skrev ralfvd ***@***.***>: > > 2.1.4 is now available. if this doesn't work, I need to delve deeper into > it, and try to simulate the behaviour with one of the Everspring devices I > do have in my possession. > > > Fingers crossed ! ;-) > > > > > On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson < ***@***.***> > wrote: > > > > Still no luck. Sent another diagnostic > > report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov 2020 > > 09:22, ralfvd ***@***.***> wrote: > > Hi Marcus, > > > > I've. built a new version 2.1.3 ; hopefully that will gain more insight. > > You don't necesarily need to re-pair the devices ; I need to pick up the > > 255 values, but it is not succeeding so far ;-) Everspring has sometimes a > > bit of a weird non-standard way of doing things. > > > > On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson < ***@***.***> > > > > wrote: > > > > > Created a new diagnostic report: > > > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > > > 2.1.0 and removed/paired sp103b a few times. Still not triggering motion > > > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in > > zwave > > > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < > > ***@***.***> > > > wrote: > > > Hi, > > > > > > I've changed some code for SP103 motion trigger (not the tamper alarm > > > yet). > > > I don't have the device myself, so the app might crash on usage. > > > > > > Version 2.1.0 is now available as test, let me know if that works for > > you. > > > Then I can try to add the tamper alarm as well. > > > > > > Thanks! Regards > > > > > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < > > ***@***.***> > > > > > > wrote: > > > > > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion > > alarm > > > > and after that triggered tamper switch.Then ran diagnostics..Device ID > > > in > > > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > > > ***@***.***> wrote: > > > > Can you submit a app diagnostic report after a motion detection? This > > > can > > > > be done via the app settings. Then I can see how the app responds to > > the > > > > event. > > > > > > > > Thanks! > > > > > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > > > ***@***.***> > > > > > > > > wrote: > > > > > > > > > SP103 used to work in old App prior to SDK3. > > > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > > > alarm. > > > > > If I add SP103 as generic zwave device it reports motion by turning > > > > device > > > > > on. > > > > > > > > > > I see these events in the log when paired as everspring SP103 device > > > > > : > > > > > 2020-11-03T14:13:06.584Z > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > data: > > > > > 0x01ff > > > > > 2020-11-03T14:13:06.584Z > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > 2020-11-03T14:13:06.799Z > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > data: > > > > > 0x01ff > > > > > 2020-11-03T14:13:06.799Z > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > 2020-11-03T14:13:06.889Z > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > data: > > > > > 0x01ff > > > > > 2020-11-03T14:13:06.890Z > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > Filter > > > > > > > > > > — > > > > > You are receiving this because you are subscribed to this thread. > > > > > Reply to this email directly, view it on GitHub > > > > > <#48>, or > > unsubscribe > > > > > < > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > — > > > > You are receiving this because you commented. > > > > Reply to this email directly, view it on GitHub > > > > < > > > > > #48 (comment) >, > > > > > > > > > or unsubscribe > > > > < > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ > > > > > > > > > > . > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > email directly, view it on GitHub, or unsubscribe. > > > > > > — > > > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > > > < > > #48 (comment) >, > > > > > or unsubscribe > > > < > > https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ > > > > > > . > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > email directly, view it on GitHub, or unsubscribe. > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < #48 (comment) >, > > or unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ > > > . > > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub < #48 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ALLQM7F2PZXLW2P3PBD5L3DSPTZ73ANCNFSM4TTXRZNQ >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQA2CYCRJ3SW3H32ZSTSPUAJNANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Perfect, Let me know if you need another diag report or test I got the sensor on my desk right now so I can easily run a few test cycles. Regards Marcus 13 november 2020 11:21:32 +01:00, skrev ralfvd <notifications@github.com>:

…

Great! I will also take a look at the tamper alarm. If I remember correctly, I had to disable that in a previous version as the reports of the sp103 weren’t too reliable. But we’ll give it another go! Can you submit one more diagnostic with the motion alarm working? Thanks for the help! On Fri, 13 Nov 2020 at 11:06, marcus-karlsson ***@***.***> wrote: > Well, > > Crossing the fingers made all the difference. Now it works. Thanks! > > Of course One always want more so now it would be nice to have the tamper > switch working. That is COMMAN_CLASS_ALARM > > > 2020-11-13T09:20:57.391Z Node[92]: Received application command for > COMMAND_CLASS_ALARM, data: 0x0501112020-11-13T09:20:57.392Z Node[92]: > [COMMAND_CLASS_ALARM] {"Alarm Type > (Raw)":{"type":"Buffer","data":[1]},"Alarm Type":1,"Alarm Level > (Raw)":{"type":"Buffer","data":[17]},"Alarm Level":17} > Regards > > Marcus > 13 november 2020 10:12:29 +01:00, skrev ralfvd ***@***.***>: > > > > > 2.1.4 is now available. if this doesn't work, I need to delve deeper into > > it, and try to simulate the behaviour with one of the Everspring devices > I > > do have in my possession. > > > > > > Fingers crossed ! ;-) > > > > > > > > > > On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson < > ***@***.***> > > wrote: > > > > > > > Still no luck. Sent another diagnostic > > > report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov > 2020 > > > 09:22, ralfvd ***@***.***> wrote: > > > Hi Marcus, > > > > > > I've. built a new version 2.1.3 ; hopefully that will gain more > insight. > > > You don't necesarily need to re-pair the devices ; I need to pick up > the > > > 255 values, but it is not succeeding so far ;-) Everspring has > sometimes a > > > bit of a weird non-standard way of doing things. > > > > > > On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson < > ***@***.***> > > > > > > wrote: > > > > > > > Created a new diagnostic report: > > > > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > > > > 2.1.0 and removed/paired sp103b a few times. Still not triggering > motion > > > > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in > > > zwave > > > > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < > > > ***@***.***> > > > > wrote: > > > > Hi, > > > > > > > > I've changed some code for SP103 motion trigger (not the tamper alarm > > > > yet). > > > > I don't have the device myself, so the app might crash on usage. > > > > > > > > Version 2.1.0 is now available as test, let me know if that works for > > > you. > > > > Then I can try to add the tamper alarm as well. > > > > > > > > Thanks! Regards > > > > > > > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < > > > ***@***.***> > > > > > > > > wrote: > > > > > > > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion > > > alarm > > > > > and after that triggered tamper switch.Then ran > diagnostics..Device ID > > > > in > > > > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > > > > ***@***.***> wrote: > > > > > Can you submit a app diagnostic report after a motion detection? > This > > > > can > > > > > be done via the app settings. Then I can see how the app responds > to > > > the > > > > > event. > > > > > > > > > > Thanks! > > > > > > > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > > > > ***@***.***> > > > > > > > > > > wrote: > > > > > > > > > > > SP103 used to work in old App prior to SDK3. > > > > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > > > > alarm. > > > > > > If I add SP103 as generic zwave device it reports motion by > turning > > > > > device > > > > > > on. > > > > > > > > > > > > I see these events in the log when paired as everspring SP103 > device > > > > > > : > > > > > > 2020-11-03T14:13:06.584Z > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > data: > > > > > > 0x01ff > > > > > > 2020-11-03T14:13:06.584Z > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > 2020-11-03T14:13:06.799Z > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > data: > > > > > > 0x01ff > > > > > > 2020-11-03T14:13:06.799Z > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > 2020-11-03T14:13:06.889Z > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > data: > > > > > > 0x01ff > > > > > > 2020-11-03T14:13:06.890Z > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > Filter > > > > > > > > > > > > — > > > > > > You are receiving this because you are subscribed to this thread. > > > > > > Reply to this email directly, view it on GitHub > > > > > > <#48>, or > > > unsubscribe > > > > > > < > > > > > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to > this > > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > > > — > > > > > You are receiving this because you commented. > > > > > Reply to this email directly, view it on GitHub > > > > > < > > > > > > > > #48 (comment) > >, > > > > > > > > > > > > or unsubscribe > > > > > < > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > — > > > > You are receiving this because you commented. > > > > Reply to this email directly, view it on GitHub > > > > < > > > > #48 (comment) > >, > > > > > > > or unsubscribe > > > > < > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ > > > > > > > > > . > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > email directly, view it on GitHub, or unsubscribe. > > > > > > — > > > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > > > < > #48 (comment) > >, > > > or unsubscribe > > > < > https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ > > > > > . > > > > > > > > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub < > #48 (comment)>, > or unsubscribe < > https://github.com/notifications/unsubscribe-auth/ALLQM7F2PZXLW2P3PBD5L3DSPTZ73ANCNFSM4TTXRZNQ > >. > > > > — > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > <#48 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEDZWQA2CYCRJ3SW3H32ZSTSPUAJNANCNFSM4TTXRZNQ> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALLQM7DSXE2LDTCWLQJ5CKTSPUCCZANCNFSM4TTXRZNQ>.

[ralfvd]

Can you submit a diagnostic report after a motion detection? Then I can check if I 100 % correctly implemented the code (so it is futureproof ;-) ) Thanks On Fri, Nov 13, 2020 at 11:29 AM marcus-karlsson <notifications@github.com> wrote:

…

Perfect, Let me know if you need another diag report or test I got the sensor on my desk right now so I can easily run a few test cycles. Regards Marcus 13 november 2020 11:21:32 +01:00, skrev ralfvd ***@***.***>: > > Great! > > > I will also take a look at the tamper alarm. If I remember correctly, I had > to disable that in a previous version as the reports of the sp103 weren’t > too reliable. > > > But we’ll give it another go! > > > Can you submit one more diagnostic with the motion alarm working? > > > Thanks for the help! > > > On Fri, 13 Nov 2020 at 11:06, marcus-karlsson ***@***.***> > wrote: > > > > Well, > > > > Crossing the fingers made all the difference. Now it works. Thanks! > > > > Of course One always want more so now it would be nice to have the tamper > > switch working. That is COMMAN_CLASS_ALARM > > > > > > 2020-11-13T09:20:57.391Z Node[92]: Received application command for > > COMMAND_CLASS_ALARM, data: 0x0501112020-11-13T09:20:57.392Z Node[92]: > > [COMMAND_CLASS_ALARM] {"Alarm Type > > (Raw)":{"type":"Buffer","data":[1]},"Alarm Type":1,"Alarm Level > > (Raw)":{"type":"Buffer","data":[17]},"Alarm Level":17} > > Regards > > > > Marcus > > 13 november 2020 10:12:29 +01:00, skrev ralfvd < ***@***.***>: > > > > > > > > 2.1.4 is now available. if this doesn't work, I need to delve deeper into > > > it, and try to simulate the behaviour with one of the Everspring devices > > I > > > do have in my possession. > > > > > > > > > Fingers crossed ! ;-) > > > > > > > > > > > > > > > On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson < > > ***@***.***> > > > wrote: > > > > > > > > > > Still no luck. Sent another diagnostic > > > > report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov > > 2020 > > > > 09:22, ralfvd ***@***.***> wrote: > > > > Hi Marcus, > > > > > > > > I've. built a new version 2.1.3 ; hopefully that will gain more > > insight. > > > > You don't necesarily need to re-pair the devices ; I need to pick up > > the > > > > 255 values, but it is not succeeding so far ;-) Everspring has > > sometimes a > > > > bit of a weird non-standard way of doing things. > > > > > > > > On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson < > > ***@***.***> > > > > > > > > wrote: > > > > > > > > > Created a new diagnostic report: > > > > > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > > > > > 2.1.0 and removed/paired sp103b a few times. Still not triggering > > motion > > > > > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in > > > > zwave > > > > > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < > > > > ***@***.***> > > > > > wrote: > > > > > Hi, > > > > > > > > > > I've changed some code for SP103 motion trigger (not the tamper alarm > > > > > yet). > > > > > I don't have the device myself, so the app might crash on usage. > > > > > > > > > > Version 2.1.0 is now available as test, let me know if that works for > > > > you. > > > > > Then I can try to add the tamper alarm as well. > > > > > > > > > > Thanks! Regards > > > > > > > > > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < > > > > ***@***.***> > > > > > > > > > > wrote: > > > > > > > > > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion > > > > alarm > > > > > > and after that triggered tamper switch.Then ran > > diagnostics..Device ID > > > > > in > > > > > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > > > > > ***@***.***> wrote: > > > > > > Can you submit a app diagnostic report after a motion detection? > > This > > > > > can > > > > > > be done via the app settings. Then I can see how the app responds > > to > > > > the > > > > > > event. > > > > > > > > > > > > Thanks! > > > > > > > > > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > > > > > ***@***.***> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > SP103 used to work in old App prior to SDK3. > > > > > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > > > > > alarm. > > > > > > > If I add SP103 as generic zwave device it reports motion by > > turning > > > > > > device > > > > > > > on. > > > > > > > > > > > > > > I see these events in the log when paired as everspring SP103 > > device > > > > > > > : > > > > > > > 2020-11-03T14:13:06.584Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.584Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > 2020-11-03T14:13:06.799Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.799Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > 2020-11-03T14:13:06.889Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.890Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > Filter > > > > > > > > > > > > > > — > > > > > > > You are receiving this because you are subscribed to this thread. > > > > > > > Reply to this email directly, view it on GitHub > > > > > > > <#48>, or > > > > unsubscribe > > > > > > > < > > > > > > > > > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to > > this > > > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > > > > > — > > > > > > You are receiving this because you commented. > > > > > > Reply to this email directly, view it on GitHub > > > > > > < > > > > > > > > > > > #48 (comment) > > >, > > > > > > > > > > > > > > > or unsubscribe > > > > > > < > > > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > > > — > > > > > You are receiving this because you commented. > > > > > Reply to this email directly, view it on GitHub > > > > > < > > > > > > #48 (comment) > > >, > > > > > > > > > or unsubscribe > > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > — > > > > You are receiving this because you commented. > > > > Reply to this email directly, view it on GitHub > > > > < > > #48 (comment) > > >, > > > > or unsubscribe > > > > < > > https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ > > > > > > > . > > > > > > > > > > > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub < > > #48 (comment) >, > > or unsubscribe < > > https://github.com/notifications/unsubscribe-auth/ALLQM7F2PZXLW2P3PBD5L3DSPTZ73ANCNFSM4TTXRZNQ > > >. > > > > > > > — > > You are receiving this because you commented. > > > > > > Reply to this email directly, view it on GitHub > > < #48 (comment) >, > > or unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AEDZWQA2CYCRJ3SW3H32ZSTSPUAJNANCNFSM4TTXRZNQ > > > . > > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub < #48 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ALLQM7DSXE2LDTCWLQJ5CKTSPUCCZANCNFSM4TTXRZNQ >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQHBQ6ITV6RUSFL2FWTSPUDABANCNFSM4TTXRZNQ> .

[marcus-karlsson]

Sent one now... maybe two. Not sure if first one was sent.f0164bfc-9937-4ea0-8c58-d9ad3e5f2925Motion was triggered 3 times and then diag was captured.RegardsMarcusOn 13 Nov 2020 12:51, ralfvd <notifications@github.com> wrote: Can you submit a diagnostic report after a motion detection? Then I can check if I 100 % correctly implemented the code (so it is futureproof ;-) ) Thanks On Fri, Nov 13, 2020 at 11:29 AM marcus-karlsson <notifications@github.com> wrote:

Perfect, Let me know if you need another diag report or test I got the sensor on my desk right now so I can easily run a few test cycles. Regards Marcus 13 november 2020 11:21:32 +01:00, skrev ralfvd ***@***.***>: > > Great! > > > I will also take a look at the tamper alarm. If I remember correctly, I had > to disable that in a previous version as the reports of the sp103 weren’t > too reliable. > > > But we’ll give it another go! > > > Can you submit one more diagnostic with the motion alarm working? > > > Thanks for the help! > > > On Fri, 13 Nov 2020 at 11:06, marcus-karlsson ***@***.***> > wrote: > > > > Well, > > > > Crossing the fingers made all the difference. Now it works. Thanks! > > > > Of course One always want more so now it would be nice to have the tamper > > switch working. That is COMMAN_CLASS_ALARM > > > > > > 2020-11-13T09:20:57.391Z Node[92]: Received application command for > > COMMAND_CLASS_ALARM, data: 0x0501112020-11-13T09:20:57.392Z Node[92]: > > [COMMAND_CLASS_ALARM] {"Alarm Type > > (Raw)":{"type":"Buffer","data":[1]},"Alarm Type":1,"Alarm Level > > (Raw)":{"type":"Buffer","data":[17]},"Alarm Level":17} > > Regards > > > > Marcus > > 13 november 2020 10:12:29 +01:00, skrev ralfvd < ***@***.***>: > > > > > > > > 2.1.4 is now available. if this doesn't work, I need to delve deeper into > > > it, and try to simulate the behaviour with one of the Everspring devices > > I > > > do have in my possession. > > > > > > > > > Fingers crossed ! ;-) > > > > > > > > > > > > > > > On Fri, Nov 13, 2020 at 9:55 AM marcus-karlsson < > > ***@***.***> > > > wrote: > > > > > > > > > > Still no luck. Sent another diagnostic > > > > report: 6524df39-d3d6-49b6-a546-faab18f54023Regards MarcusOn 13 Nov > > 2020 > > > > 09:22, ralfvd ***@***.***> wrote: > > > > Hi Marcus, > > > > > > > > I've. built a new version 2.1.3 ; hopefully that will gain more > > insight. > > > > You don't necesarily need to re-pair the devices ; I need to pick up > > the > > > > 255 values, but it is not succeeding so far ;-) Everspring has > > sometimes a > > > > bit of a weird non-standard way of doing things. > > > > > > > > On Fri, Nov 13, 2020 at 9:10 AM marcus-karlsson < > > ***@***.***> > > > > > > > > wrote: > > > > > > > > > Created a new diagnostic report: > > > > > 0af549fb-fab7-4146-b26b-efd7781ec05fStill not working. Updated app to > > > > > 2.1.0 and removed/paired sp103b a few times. Still not triggering > > motion > > > > > alarm but can still see COMMAND_CLASS_BASIC setting to value 255 in > > > > zwave > > > > > log.Regards Marcus On 12 Nov 2020 22:32, ralfvd < > > > > ***@***.***> > > > > > wrote: > > > > > Hi, > > > > > > > > > > I've changed some code for SP103 motion trigger (not the tamper alarm > > > > > yet). > > > > > I don't have the device myself, so the app might crash on usage. > > > > > > > > > > Version 2.1.0 is now available as test, let me know if that works for > > > > you. > > > > > Then I can try to add the tamper alarm as well. > > > > > > > > > > Thanks! Regards > > > > > > > > > > On Thu, Nov 12, 2020 at 9:33 PM marcus-karlsson < > > > > ***@***.***> > > > > > > > > > > wrote: > > > > > > > > > > > Sent one now:197a3bc7-7e7f-44a9-a95d-bef2b6afe68eTriggered motion > > > > alarm > > > > > > and after that triggered tamper switch.Then ran > > diagnostics..Device ID > > > > > in > > > > > > zwave is 88...RegardsMarcusOn 12 Nov 2020 21:23, ralfvd < > > > > > > ***@***.***> wrote: > > > > > > Can you submit a app diagnostic report after a motion detection? > > This > > > > > can > > > > > > be done via the app settings. Then I can see how the app responds > > to > > > > the > > > > > > event. > > > > > > > > > > > > Thanks! > > > > > > > > > > > > On Thu, Nov 12, 2020 at 9:14 PM marcus-karlsson < > > > > > ***@***.***> > > > > > > > > > > > > wrote: > > > > > > > > > > > > > SP103 used to work in old App prior to SDK3. > > > > > > > Now in 2.0.9 on V5.0 .0-rc38 it pairs OK but do not report motion > > > > > alarm. > > > > > > > If I add SP103 as generic zwave device it reports motion by > > turning > > > > > > device > > > > > > > on. > > > > > > > > > > > > > > I see these events in the log when paired as everspring SP103 > > device > > > > > > > : > > > > > > > 2020-11-03T14:13:06.584Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.584Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > 2020-11-03T14:13:06.799Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.799Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > 2020-11-03T14:13:06.889Z > > > > > > > Node[80]: Received application command for COMMAND_CLASS_BASIC, > > > > data: > > > > > > > 0x01ff > > > > > > > 2020-11-03T14:13:06.890Z > > > > > > > Node[80]: [COMMAND_CLASS_BASIC] {"Value > > > > > > > (Raw)":{"type":"Buffer","data":[255]},"Value":255} > > > > > > > Filter > > > > > > > > > > > > > > — > > > > > > > You are receiving this because you are subscribed to this thread. > > > > > > > Reply to this email directly, view it on GitHub > > > > > > > <#48>, or > > > > unsubscribe > > > > > > > < > > > > > > > > > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQHWR46EUY555IVHJTTSPQ625ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to > > this > > > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > > > > > — > > > > > > You are receiving this because you commented. > > > > > > Reply to this email directly, view it on GitHub > > > > > > < > > > > > > > > > > > #48 (comment) > > >, > > > > > > > > > > > > > > > or unsubscribe > > > > > > < > > > > > > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAISWRNR7RQP5RBVT3SPRA73ANCNFSM4TTXRZNQ > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > > > — > > > > > You are receiving this because you commented. > > > > > Reply to this email directly, view it on GitHub > > > > > < > > > > > > #48 (comment) > > >, > > > > > > > > > or unsubscribe > > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/AEDZWQAS5XIZXYY73KANOZLSPTSY5ANCNFSM4TTXRZNQ > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > —You are receiving this because you authored the thread.Reply to this > > > > email directly, view it on GitHub, or unsubscribe. > > > > > > > > — > > > > You are receiving this because you commented. > > > > Reply to this email directly, view it on GitHub > > > > < > > #48 (comment) > > >, > > > > or unsubscribe > > > > < > > https://github.com/notifications/unsubscribe-auth/AEDZWQCJ7ODFATEEJ56MBXLSPTYBFANCNFSM4TTXRZNQ > > > > > > > . > > > > > > > > > > > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub < > > #48 (comment) >, > > or unsubscribe < > > https://github.com/notifications/unsubscribe-auth/ALLQM7F2PZXLW2P3PBD5L3DSPTZ73ANCNFSM4TTXRZNQ > > >. > > > > > > > — > > You are receiving this because you commented. > > > > > > Reply to this email directly, view it on GitHub > > < #48 (comment) >, > > or unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AEDZWQA2CYCRJ3SW3H32ZSTSPUAJNANCNFSM4TTXRZNQ > > > . > > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub < #48 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ALLQM7DSXE2LDTCWLQJ5CKTSPUCCZANCNFSM4TTXRZNQ >. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDZWQHBQ6ITV6RUSFL2FWTSPUDABANCNFSM4TTXRZNQ> .

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.