Zwave Everspring SP815-1 pet immune motion senor

kovacsi2899 · November 1, 2021, 6:49am

Hi, Yes I’m the one who is trying to do it. This is based on my other devices XML Everspring SP816 what is very similar motion sensor to this one Everspring SP815. There are some slight differences that’s why I do check all low level settings one by one based on available specifications and information from the inclusion process. Plus this is not a unique issue with this device. Others had same and there are posts in forums about inclusion data what is useful for this update.

Update:
First xml has bee created by the binding:
network_d8a23a12__node_172.xml (11.7 KB)
I think that’s the one what we wanted to see.

kovacsi2899 · November 2, 2021, 8:14pm

I was marking this SP815 for deletion yesterday. Now as I see it is deleted from the database. Shall I create a new one based on the correct XML? OH does not creates channels till it is added in the database.

apella12 · November 2, 2021, 8:20pm

I noticed it was gone today and thought you deleted it… Maybe Chris did? Anyway, yes, use the new XML and get it started. After you are done make sure to request a review.

Bob

kovacsi2899 · November 2, 2021, 8:23pm

Thx. I do it this way and I’ll mark when I finished it. I was asking him to delete it as I was not able to refresh with the new xml plus I uploaded a wrong pdf accidentaly in the description section.

apella12 · November 2, 2021, 8:27pm

Oh ok. That explains that.

kovacsi2899 · November 3, 2021, 9:28am

I have added it to the database yesterday including all additional information. I marked it for review. Many thanks for all support so far!

kovacsi2899 · November 5, 2021, 5:46am

Yesterday I have double checked SP815 in the database: OpenSmartHouse Z-Wave Device Database
I fine tuned description and additional data fields. I think it is OK now.
Device is communicating with Openhab I see it in Zwave trace logs, temperature, humidity and motion as well. Can you tell me what is the approx timeframe of the review and it arrives to OH database?

apella12 · November 5, 2021, 2:20pm

Chris does this about twice a week. If I’m waiting I check this site and click on the database updates to see what files have changed (to see if the changes I’m looking for are included. Then I check this site to see if the .jar is compiled. As a note, depending on what version of OH3 you are running, you may need to update Xstream or you could get karaf errors.

Bob

kovacsi2899 · November 14, 2021, 7:11am

Hello,

Sorry for the late reply just I was doing the testing.
I have installed the snaphot version of Zwave binding and database roll out was succesfull. Many thanks for that! Now all channels are operational:

All channels are refreshing values. However Burglar channel does not change status when it senses motion. Here is the Zwave trace about status change:

On:

2021-11-14 07:51:41.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Application Command Request (ALIVE:DONE)
2021-11-14 07:51:41.375 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: resetResendCount initComplete=true isDead=false
2021-11-14 07:51:41.375 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2021-11-14 07:51:41.375 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: SECURITY NOT required on COMMAND_CLASS_ALARM
2021-11-14 07:51:41.375 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 172: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2021-11-14 07:51:41.375 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 172: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2021-11-14 07:51:41.375 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 172: Alarm Type = BURGLAR (0)
2021-11-14 07:51:41.375 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 172: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2021-11-14 07:51:41.375 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 172: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2021-11-14 07:51:41.375 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter processing NOTIFICATION
2021-11-14 07:51:41.375 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter NOTIFICATION event is 8, type OnOffType
2021-11-14 07:51:41.375 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter processing NOTIFICATION
2021-11-14 07:51:41.375 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter NOTIFICATION event is 8, type OnOffType
2021-11-14 07:51:41.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Commands processed 1.
2021-11-14 07:51:41.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@13cfa139.
2021-11-14 07:51:41.376 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-11-14 07:51:41.376 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-11-14 07:51:41.376 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

Off:

2021-11-14 07:51:57.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Application Command Request (ALIVE:DONE)
2021-11-14 07:51:57.108 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: resetResendCount initComplete=true isDead=false
2021-11-14 07:51:57.109 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2021-11-14 07:51:57.109 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 172: SECURITY NOT required on COMMAND_CLASS_ALARM
2021-11-14 07:51:57.109 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 172: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2021-11-14 07:51:57.109 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 172: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2021-11-14 07:51:57.109 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 172: Alarm Type = BURGLAR (0)
2021-11-14 07:51:57.109 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 172: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2021-11-14 07:51:57.109 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 172: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2021-11-14 07:51:57.109 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter processing NOTIFICATION
2021-11-14 07:51:57.109 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter NOTIFICATION event is 0, type OnOffType
2021-11-14 07:51:57.109 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 172: Updating channel state zwave:device:d81afdcb64:node172:alarm_burglar to OFF [OnOffType]
2021-11-14 07:51:57.109 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter processing NOTIFICATION
2021-11-14 07:51:57.109 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 172: Alarm converter NOTIFICATION event is 0, type OnOffType
2021-11-14 07:51:57.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Commands processed 1.
2021-11-14 07:51:57.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 172: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@30a1a40d.
2021-11-14 07:51:57.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-11-14 07:51:57.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-11-14 07:51:57.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

I was checking 3 motion sensors XML to compare this section: Everspring SP515 (this one) SP817 and Aeon Multisensor 6 (ZW100).
SP815:


</channel>
-<channel id="alarm_burglar" typeId="alarm_burglar">
<label>Alarm (burglar)</label>
-<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
</properties>
</channel>

SP817:


</channel>
-<channel id="alarm_motion" typeId="alarm_motion">
<label>Motion Alarm</label>
-<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
</properties>
</channel>

ZW100:


</channel>
-<channel id="alarm_motion" typeId="alarm_motion">
<label>Motion Alarm</label>
-<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR, event=8</property>
</properties>
</channel>

I see two differences. Label of the channel, and SP815 operates with event=8 like ZW100.
In ZW100 evemt=8 has one additional data – ,event=8:

-<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR, event=8</property>
</properties>

May be that is the reason that event is not recognized. Where should I continue testing? Shall we change the database or I can try to change locally?

kovacsi2899 · November 14, 2021, 7:56am

Update:

I have modified this channel in org.openhab.core.thing.Thing Jason file manually.
Remove and readd item. Now it works. Here is how it looks like now:

    {
      "acceptedItemType": "Switch",
      "kind": "STATE",
      "uid": {
        "segments": [
          "zwave",
          "device",
          "d81afdcb64",
          "node172",
          "alarm_motion"
        ],
        "uid": "zwave:device:d81afdcb64:node172:alarm_motion"
      },
      "channelTypeUID": {
        "segments": [
          "zwave",
          "alarm_motion"
        ],
        "uid": "zwave:alarm_motion"
      },
      "label": "Alarm (motion)",
      "description": "Indicates if the burglar alarm is triggered",
      "configuration": {
        "properties": {}
      },
      "properties": {
        "binding:*:OnOffType": "COMMAND_CLASS_ALARM;type\u003dBURGLAR, event\u003d8"
      },
      "defaultTags": []
    },

We need to check what should be changed as Openhab will recreate this file based on database in case of any update and my manual change will be lost.

kovacsi2899 · November 15, 2021, 9:30pm

I have checked configuration parameters are working. I have changed Off interval to 180 sec and it changes in 3 minutes. So now I think the database should slightly modified as I’m suggesting. Pls check and advise how to proceed.

chris · November 15, 2021, 10:31pm

To be clear, you propose to change the channel type to alarm_motion? If so, that seems fine from my quick look. Please feel free to update.

kovacsi2899 · November 16, 2021, 4:47am

After all tests yes. I have already modified the database accordingly. I’m not satisfied with called “Power” channel what supposed to be tamper channel. I’m doing some tests on that as well. I think it has same issue. Then I submit for approval.

kovacsi2899 · November 16, 2021, 9:16pm

So I have finished all tests. Both alarm and tamper channel are working fine with modified parameters. I have corrected in the database and submit it approval again. As soon as it rolles through I’ll update the binding and test it again. Many thanks for all support so far.

chris · November 16, 2021, 11:50pm

Thanks @kovacsi2899. This is now merged into the binding so hopefully it’s all good

kovacsi2899 · November 17, 2021, 10:19pm

Many thanks Chris! I have checked the last snapshot. Now all channels are working after adding thing in the new version. I think we can close the topic with success.

chris · November 17, 2021, 10:26pm

Thanks @kovacsi2899