Hello
I recently post my misadventure with Zwave Sensor using by defaut Access Control to send door state
The original post is here : viewtopic.php?t=40115
So, I just post here too to ask for en enhancement to manage those devices. Is it possible to bind the door switch to Access Control.
Aeotec tell me that binary sensor is now deprecated for thant
If it could help, it reports in Hardware with an ID like "zwavejs2mqtt_0xc7bf3f61_56-113-0-Access_Control-Door_state", Type "General/Text"
And the text values are : "Window/door is closed" or "Window/door is open in regular position"
I can take screenshots or send information from zwavejsui / domoticz if needed
Thank you
MQTT ZwaveJsUi and Zwave Notification : Enhancement
Moderator: leecollings
- cbartetzko
- Posts: 27
- Joined: Sunday 25 December 2016 9:24
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2023.1
- Location: Speyer/Germany
- Contact:
Re: MQTT ZwaveJsUi and Zwave Notification : Enhancement
Recognition of text based door/window sensors in Domoticz would be nice, I agree.
A possible workaraound in the meantime is defining a binary sensor in ZwaveJsUI-HomeAssistant-Section.
This worked well for me:
viewtopic.php?p=301578#p301578
This is an example HASS Device JSON Definition for a Fibaro Sensor (could be adapted to any brand sensor):
{
"type": "sensor",
"object_id": "notification_access_control_door_state",
"discovery_payload": {
"value_template": "{{ {22: \"Window/door is open\",23: \"Window/door is closed\",5632: \"Window/door is open in regular position\",5633: \"Window/door is open in tilt position\"}[value_json.value] | default(value_json.value) }}",
"icon": "mdi:alarm-light",
"state_topic": "zwave/EG_WZ_Terassentür/113/0/Access_Control/Door_state",
"json_attributes_topic": "zwave/EG_WZ_Terassentür/113/0/Access_Control/Door_state",
"device": {
"identifiers": [
"zwavejs2mqtt_0xc26d12e5_node41"
],
"manufacturer": "Fibargroup",
"model": "Door Opening Sensor (FGK101)",
"name": "EG_WZ_Terassentür",
"sw_version": "3.2"
},
"name": "EG_WZ_Terassentür_notification_access_control_door_state",
"unique_id": "zwavejs2mqtt_0xc26d12e5_41-113-0-Access_Control-Door_state"
},
"discoveryTopic": "sensor/EG_WZ_Terassentür/notification_access_control_door_state/config",
"values": [
"113-0-Access Control-Door state"
],
"persistent": true,
"ignoreDiscovery": false,
"id": "sensor_notification_access_control_door_state"
}
A possible workaraound in the meantime is defining a binary sensor in ZwaveJsUI-HomeAssistant-Section.
This worked well for me:
viewtopic.php?p=301578#p301578
This is an example HASS Device JSON Definition for a Fibaro Sensor (could be adapted to any brand sensor):
{
"type": "sensor",
"object_id": "notification_access_control_door_state",
"discovery_payload": {
"value_template": "{{ {22: \"Window/door is open\",23: \"Window/door is closed\",5632: \"Window/door is open in regular position\",5633: \"Window/door is open in tilt position\"}[value_json.value] | default(value_json.value) }}",
"icon": "mdi:alarm-light",
"state_topic": "zwave/EG_WZ_Terassentür/113/0/Access_Control/Door_state",
"json_attributes_topic": "zwave/EG_WZ_Terassentür/113/0/Access_Control/Door_state",
"device": {
"identifiers": [
"zwavejs2mqtt_0xc26d12e5_node41"
],
"manufacturer": "Fibargroup",
"model": "Door Opening Sensor (FGK101)",
"name": "EG_WZ_Terassentür",
"sw_version": "3.2"
},
"name": "EG_WZ_Terassentür_notification_access_control_door_state",
"unique_id": "zwavejs2mqtt_0xc26d12e5_41-113-0-Access_Control-Door_state"
},
"discoveryTopic": "sensor/EG_WZ_Terassentür/notification_access_control_door_state/config",
"values": [
"113-0-Access Control-Door state"
],
"persistent": true,
"ignoreDiscovery": false,
"id": "sensor_notification_access_control_door_state"
}
-
- Posts: 27
- Joined: Thursday 17 November 2016 21:22
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2023.1
- Contact:
Re: MQTT ZwaveJsUi and Zwave Notification : Enhancement
Thank you for your workaround.
I'm not very familiar with HASS Device JSON Definition. But I will learn
With aeotec workaround, it's ok too.
I submit this enhancement to make it easier for all users
I'm not very familiar with HASS Device JSON Definition. But I will learn

With aeotec workaround, it's ok too.
I submit this enhancement to make it easier for all users
Who is online
Users browsing this forum: No registered users and 1 guest