andersevenrud/ha-nexa-bridge-x

Device Support

Opened this issue · 10 comments

andersevenrud commented

This issue was created in an effort to collect information about device support.

See my gist where I collect information about this product in general and another of my gists for other z-wave products.

If your device does not show up correctly in HA (values, actions, etc.), please open a new issue.

Bridge1

The legacy (non-X) Nexa Bridge is supported (#15), but with some caveats:

  • Polling is slower because it requires more API calls
  • Power metering stats disabled since I have no data to work with (#19)
  • Bridge sometimes becomes unresponsive causing slow action responses, like toggling switches (seems to be hardware or API related)

Probably has the same nxt/z-wave device support as the Bridge2, but no detailed power metering slightly different API.

I have no way to verify that everything is working as expected, because I don't own this device. Feel free to leave a comment or open an issue.

Bridge2

Aka "Nexa Bridge X".

Supported Protocols

  • Z-Wave / Z-Wave+ (Gen5)
  • System Nexa / NXT (433MHz)
  • Fire & Safety (FS-558)

Supported Capabilities

Implemented device capabilities:

  • Binary switch
  • Switch level
  • Temperature
  • Humidity
  • Luminance
  • Media (Volume/Pause/Mute)
  • Notification (Contact/Motion/Smoke/Water/Twilight)

And the following undocumented capabilities:

  • Power (W/A/V/kWh)
  • Battery (Percentage)
  • Notification (Intrusion)
  • Custom Events (for push switches, etc)

Exposed bridge custom metrics:

  • Current power usage (combined and per device)
  • Total power usage (today/yesterday/week/month)

Supported Devices

Any smart devices that supports capabilities noted above should work out of the box.

This is a list of reported devices:

if you have a device not listed below feel free to leave a comment.

System Nexa / NXT (433MHz)

Manufacturer Model Description
❔ Nexa NBA-002 Temperature & Humidity Sensor (Battery) 1
❔ Nexa MYCR-250 Dimmer (Plug-in) 1
❔ Nexa NEYCT-705 Remote (Battery) 1
✔️ Nexa WTH-103 Temperature & Humidity Sensor (Battery) 2
✔️ Nexa MYCR-1000 Switch (Plug-in) 2
✔️ Nexa MYCR-3500 Switch (Plug-in) 2
✔️ Nexa MWMR-251 Built In Reciever (Dimmer) 3
✔️ Nexa MWMR-2300 Built in Reciever (On/Off) 3

Z-wave

Manufacturer Model Description
✔️ Nexa AD-147 Dimmer (Plug-in)
✔️ Nexa ZPR-111 Switch w/energy meter (Plug-in)
✔️ Nexa ZDS-102 Door/Window Sensor (Battery)
✔️ Nexa ZRT-106 Thermostatic Radiator 2
✔️ Nexa ZSD-109 Smoke Detector 2
✔️ Nexa AN-179 Built In Reciever (On/Off) 3
✔️ Fibaro FGWPE/F-102 Switch w/energy meter (Plug-in)
✔️ Fibaro FGSD-002 Smoke Sensor 3
✔️ Aeotec aërQ Temperature & Humidity Sensor (Battery)
✔️ Namron ? 1 Channel switch / dimmer (Battery) 4
✔️ Namron K4 2 Channel switch (Battery) 43
✔️ Namron K8 4 Channel switch (Battery) 43

Discoveries

  • The server on the Nexa Bridge X includes workarounds for sensors that reports broken values (like the infamous 31 bit random flip in metering that causes huge negative numbers. Nexa actually has this defect in their own products)
  • This bridge does not fully respect the z-wave standards when it comes to API exposure, which means some data is missing and events, names etc. might actually diverge from their actual function. An example is the certain environmental sensors with humidity warnings or leak detection can be reported as a fire alarm.
  • The interview process when doing device inclusion can hang in certain cases
  • If the capability is not supported by the bridge, you won't get any control at all in HA
  • Battery levels reporting seems narrow (I get 50% on a device that reports ~60% on zwavejs)

Footnotes

  1. Firmware 2.4.1 has Nexa protocols disabled ?! (@andersevenrud) ↩ ↩2 ↩3

  2. Reported by @mkrase ↩ ↩2 ↩3 ↩4 ↩5

  3. Reported by @agit22 ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  4. Buggy inclusion. Required multiple tries (@andersevenrud, @agit22) ↩ ↩2 ↩3

mkrase commented

Hi. Great work!
The following devices also seem to work:
NXT: WTH-103 Temperature & Humidity Sensor (Battery)
NXT: MYCR-1000 and MYCR-3500 – PLUG-IN ON/OFF
Z-Wave: ZRT-106 Thermostatic Radiator (partly only, no time/date is set)* (is a rebranded Everspring AC301)
Z-Wave: ZSD-109 smoke detector
*But even the bridge does not set the date/time of the Thermostat

  • 👍1
andersevenrud commented

@mkrase Really appreciate the feedback, thanks!

agit22 commented

Currently using these devices, all working
NXT: MWMR-251 Built In Reciever (Dimmer)
NXT: MWMR-2300 Built in Reciever (On/Off)
Z-Wave: AN-179 Built In Reciever (On/Off)
Z-Wave: Fibaro Smoke Sensor FGSD-002 (Reports Battery, Temperature, Smoke Sensor and Tamper Sensor)

  • 👍1
andersevenrud commented

@agit22 Thank you very much for the feedback!

agit22 commented

Z-Wave: Namron K4 2ch switch (Reports Last keypress and battery)
Z-Wave: Namron K8 4ch switch (Reports Last keypress and battery)

Very buggy inclusion into the Bridge X gateway, takes multiple attempts. Once included, shows up without any problems in the integration.

  • 👍1
olterman commented

The nexa remote for MYC-4 correctly gives HA 1 binary sensor, but the sensor does not register any on or off events.

andersevenrud commented

@olterman From HA to the device, the other way around, or both ?

olterman commented

Nexa MLT-1924/1925 PUSH BUTTON - does not show up as a device in HA. the button works on the Nexa Bridge but does not show up in Home Assistant. (the other problem is that on the bridge it always shows as putton pushed .... wich means to use it in an integration one must use last event updated or something)

Here is what v1/nodes show
{
"id": "LLyDHieHFLqEERa3",
"name": "Doorbell",
"type": "Extended",
"category": "",
"hideInApp": false,
"ignoreInRoomAction": false,
"broken": false,
"locked": false,
"favorite": false,
"favoriteCapability": "",
"roomId": "4",
"roomName": "Hallen",
"extraInfo": {
"id": "nexa_systemnexa",
"customEvents": [],
"customActions": []
},
"capabilities": [
"notificationPushButton"
],
"tags": [],
"periodicEvents": [],
"minMax": {

},
"lastEvents": {
  "notificationPushButton": {
    "value": true,
    "prevValue": true,
    "time": "2024-06-03T14:35:26.816Z",
    "name": "notificationPushButton"
  }
}

}

andersevenrud commented

@olterman It looks like this device is using a capability (notificationPushButton) that is not documented by Nexa.

Could you open a new issue for this and I will fix it ASAP.

andersevenrud commented

@olterman I went ahead and just pushed a fix for this and did a new release. If you come across any other issues, please open a new issue.