andersevenrud commented 1 year ago

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 / Bridge3

Bridge2 aka "Nexa Bridge X" (White enclosure), and latest Bridge 3 (Black enclosure).

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
:grey_question:	Nexa	NBA-002	Temperature & Humidity Sensor (Battery) [^1]
:grey_question:	Nexa	MYCR-250	Dimmer (Plug-in) [^1]
:grey_question:	Nexa	NEYCT-705	Remote (Battery) [^1]
:heavy_check_mark:	Nexa	WTH-103	Temperature & Humidity Sensor (Battery) [^3]
:heavy_check_mark:	Nexa	MYCR-1000	Switch (Plug-in) [^3]
:heavy_check_mark:	Nexa	MYCR-3500	Switch (Plug-in) [^3]
:heavy_check_mark:	Nexa	MWMR-251	Built In Reciever (Dimmer) [^4]
:heavy_check_mark:	Nexa	MWMR-2300	Built in Reciever (On/Off) [^4]

Z-wave

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

[^1]: Firmware 2.4.1 has Nexa protocols disabled ?! (@andersevenrud) [^2]: Buggy inclusion. Required multiple tries (@andersevenrud, @agit22) [^3]: Reported by @mkrase [^4]: Reported by @agit22

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)

mkrase commented 1 year ago

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

andersevenrud commented 1 year ago

@mkrase Really appreciate the feedback, thanks!

agit22 commented 10 months ago

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)

andersevenrud commented 10 months ago

@agit22 Thank you very much for the feedback!

agit22 commented 10 months ago

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.

olterman commented 7 months ago

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 7 months ago

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

olterman commented 5 months ago

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 5 months ago

@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.