Legacy Nexa Bridge Connectivity Issues

[passatraggaren]

I have some issues adding my legacy bridge+.
I can add the device and the name of the device shows up but no entites. And the integration fails.

From the debug logging:
2024-01-09 11:02:56.043 DEBUG (MainThread) [custom_components.nexa_bridge_x.nexa] GET http://192.168.0.18/v1/nodes/1013: 200
2024-01-09 11:02:56.146 DEBUG (MainThread) [custom_components.nexa_bridge_x.nexa] GET http://192.168.0.18/v1/nodes/1017: 200
2024-01-09 11:03:18.652 DEBUG (MainThread) [custom_components.nexa_bridge_x.nexa] Finished fetching Nexa Bridge X Coordinator data in 25.010 seconds (success: False)

Would be great to get some assistance :)

/Christoffer

[andersevenrud]

It just dawned on me that this is probably a timeout. It says "25 seconds" in your log, which is the same as the timeout value set in this integration.

Can you try editing this line inside your HA installation to something like 60?

And restart HA afterwards

ha-nexa-bridge-x/custom_components/nexa_bridge_x/const.py

Line 27 in d718a7e

POLL_TIMEOUT = 25

It would also be nice to see the timing in the Finished fetching Nexa Bridge X Coordinator data messages afterwards to get a sense of how long it takes on your setup, because I think maybe this timeout should be increased.

[passatraggaren]

I modified the timeout to 60 and got the same error, increased it to 300 and still got the same error.

24-01-15 15:58:48.808 DEBUG (MainThread) [custom_components.nexa_bridge_x.nexa] GET http://192.168.0.18/v1/nodes/1048: 200
2024-01-15 16:03:47.364 DEBUG (MainThread) [custom_components.nexa_bridge_x.nexa] Finished fetching Nexa Bridge X Coordinator data in 300.011 seconds (success: False)

[andersevenrud]

That's a shame. In #15 I ran to into something similar for another user, which is why I already increased this timeout value once.

Sadly, I don't own a legacy bridge, so I don't really know where to go from here. Do you know how to work with tools like Postman to perform API requests ?

[passatraggaren]

Never used Postman but i've installed it and managed to make a couple of api calls to my Nexa.
Do you want me to try something with Postman?

[andersevenrud]

What you could try is to do a GET request to http://192.168.0.18/v1/nodes and then the same for http://192.168.0.18/v1/nodes/<id> for the ones that show up and use the associated ids.

Do you want me to try something with Postman?

If you've already got something then just stick with that. The most interesting part here would be how long it takes for the requests of all of this. Maybe there is a buggy device here or something.

[andersevenrud]

Did you get a chance to check this out ?

[passatraggaren]

No not yet, I started with the integration of my solarpanels and heating system instead. I might give the old Nexa one more try later on, I'll let you know! Thanks!

[sonite]

GET via postman: http://192.168.1.2/v1/nodes/1082
{
"code": 401,
"description": "The request requires user authentication",
"homeRef": "/",
"reasonPhrase": "Unauthorized",
"uri": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2"
}

[andersevenrud]

@sonite API calls requires Digest Authentication with the username nexa and password nexa.