Skip to content

Latest commit

 

History

History
69 lines (46 loc) · 2.67 KB

HELP.md

File metadata and controls

69 lines (46 loc) · 2.67 KB
Raw

Help

This project was developed using a bridge with firmware version 2.4.1. The legacy non-X bridge is also supported but with limited functionality.

The bridges are codenamed:

  • Bridge1 with 1.6 firmware or lower (legacy)
  • Bridge2 with 1.7.3 firmware or 2.x (aka "X")
  • Bridge3 with 2.5.8 firmware

Ensure that your firmware is up to date. Some X bridges ship with old firmware.

Unfortunately there is no way to manually initiate firmware updates. If your devices does not have the 2.x firmware installed even if using a registered Nexa account, Contact support. From my understanding they establish a remote connection and can perform the firmware update.

I can't connect

Ensure that you're connecting to the correct IP and with the correct credentials.

The factory login is nexa / nexa.

I don't see any sensor values

If you have registered a new device in the App/Web UI you have to reload the integration first. This is done from the integration settings and the hamburger menu on the card shown on the page. If it still does not show up, see connection issues;

Note that the Nexa Bridge in some cases does not expose all of your sensor values. It is not a regular z-wave interface, but a custom API. There is an issue that tracks tested devices.

How do I use my stateless switches ?

You should be able to use the events nexa_bridge_x_custom_event for automation where the type field contains the event from the device.

I'm still having issues. Help!

Create a new issue on github with a description of the problem and copies of any errors from HA logs, and preferrably data dumps from your bridge.

There's also a discord server where you can ask for help, but using Github is always preferred.

Providing data dumps can be done with utilities like Postman.

The most critical data comes from http://<bridge-ip-address>/v1/info and http://<bridge-ip-address>/v1/nodes and can be accessed using nexa as both username and password with Digest Authentication enabled.

Some of this data can contain personal information (like location in the "info"), so make sure to censor this before attaching to the issue.

Enabling debug logs

This can be viewed from Settings -> System -> Logs -> LOAD FULL LOGS.

For more verbose information from this integration, add the following to your configuration.yaml file:

logger:
  logs:
    custom_components.nexa_bridge_x: debug