I can't connect!

[Cleanerx01]

Using the right IP and nexa as username and password without success.

Nexa Bridge 3 2.5.8

[andersevenrud]

Have you checked the HA logs ? It might give some hints about what's going on here.

[Cleanerx01]

No I can't see anything in the logs.

I have tried to log in to my IP address through the browser using nexa as username and password, but without success :-(

Den ons 6 nov. 2024 13:03Anders Evenrud @.***> skrev:

Have you checked the HA logs ? It might give some hints about what's going on here.

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2459569735, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PD6ABEHLHYJXERIAUTZ7IARDAVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJZGU3DSNZTGU . You are receiving this because you authored the thread.Message ID: @.***>

[andersevenrud]

I have tried to log in to my IP address through the browser using nexa as username and password, but without success :-(

Hm. According to Nexa all devices ship with nexa / nexa as username / password for all bridges, so that's a bit strange 🤔

Did you get this device second hand or a returned item in a store ?

[andersevenrud]

I see that you have the firmware 2.5.8, which is undocumented (from what I can see). I also went to their website and it seems that they now sell a "Bridge 3", which is black instead of white. I was not aware of this.

Maybe you have this newer device ?

[Cleanerx01]

Yes it's a Bridge 3 but the login should still work!

I bought it new a month ago! I explained to the support that nexa-nexa is not working, maybe I get an answer tomorrow!

Den ons 6 nov. 2024 17:43Anders Evenrud @.***> skrev:

I see that you have the firmware 2.5.8, which is undocumented (from what I can see). I also went to their website and it seems that they now sell a "Bridge 3", which is black instead of white. I was not aware of this.

Maybe you have this newer device ?

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2460274048, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PB7BDDGQJJ2QIIQIK3Z7JBJNAVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQGI3TIMBUHA . You are receiving this because you authored the thread.Message ID: @.***>

[andersevenrud]

Aha. I personally do not have access to a Bridge 3 (or the firmware), so let's hope support comes through with some info 🤞

[andersevenrud]

Just a heads-up regarding this integration. Currently, there is a check to see if it is a "Bridge1" or "Bridge2" (aka "Bridge X") depending on the checkbox in the login form shown in HA.

So if your bridge identifies itself as "Bridge3" when the integration tries to connect you will get an error. If this is the case, could you provide me with a couple of samples of data from your bridge API ?

It is fairly simple to perform and some examples are provided in my help documentation. I can assist if needed (either here or on discord, which is linked in the docs).

This will show if the firmware is fully compatible, and I can update the check to accept "Bridge3" and publish a new release of the integration.

[Cleanerx01]

Den ons 6 nov. 2024 21:56Anders Evenrud @.***> skrev:

Just a heads-up regarding this integration. Currently, there is a check to see if it is a "Bridge1" or "Bridge2" (aka "Bridge X") depending on the checkbox in the login form shown in HA.

So if your bridge identifies itself as "Bridge3" when the integration tries to connect you will get an error. If this is the case, could you provide me with a couple of samples of data from your bridge API ?

It is fairly simple to perform and some examples are provided in my help documentation https://github.com/andersevenrud/ha-nexa-bridge-x/blob/main/HELP.md#im-still-having-issues-help. I can assist if needed (either here or on discord, which is linked in the docs).

This will show if the firmware is fully compatible, and I can update the check to accept "Bridge3" and publish a new release of the integration.

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2460761648, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PBW6KB2LUBOPZAA7ALZ7J667AVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQG43DCNRUHA . You are receiving this because you authored the thread.Message ID: @.***>

[Cleanerx01]

I'm pretty new to all this so I might be doing something wrong! Below is an example, when I click on "open link" I never get there!

Den mån 11 nov. 2024 10:30JG Infotainment @.***> skrev:

Den ons 6 nov. 2024 21:56Anders Evenrud @.***> skrev:

Just a heads-up regarding this integration. Currently, there is a check to see if it is a "Bridge1" or "Bridge2" (aka "Bridge X") depending on the checkbox in the login form shown in HA.

So if your bridge identifies itself as "Bridge3" when the integration tries to connect you will get an error. If this is the case, could you provide me with a couple of samples of data from your bridge API ?

It is fairly simple to perform and some examples are provided in my help documentation https://github.com/andersevenrud/ha-nexa-bridge-x/blob/main/HELP.md#im-still-having-issues-help. I can assist if needed (either here or on discord, which is linked in the docs).

This will show if the firmware is fully compatible, and I can update the check to accept "Bridge3" and publish a new release of the integration.

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2460761648, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PBW6KB2LUBOPZAA7ALZ7J667AVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQG43DCNRUHA . You are receiving this because you authored the thread.Message ID: @.***>

[andersevenrud]

The image from your email does not show up. Something must have gone wrong in sending.

[Cleanerx01]

Den mån 11 nov. 2024 14:44Anders Evenrud @.***> skrev:

The image from your email does not show up. Something must have gone wrong in sending.

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2468214079, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PG6BH6LIRTLEVHCARD2ACYCJAVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGIYTIMBXHE . You are receiving this because you authored the thread.Message ID: @.***>

[andersevenrud]

Something must have gone wrong in sending.

You probably need to go directly to the issue on Github and comment there instead of putting attachments into email responses.

[Cleanerx01]

Are you Swedish or Norwegian? Can I contact you via messenger or e-mail?

Den mån 11 nov. 2024 21:01Anders Evenrud @.***> skrev:

Something must have gone wrong in sending.

You probably need to go directly to the issue on Github and comment there instead of putting attachments into email responses.

— Reply to this email directly, view it on GitHub https://github.com/andersevenrud/ha-nexa-bridge-x/issues/50#issuecomment-2468930417, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMMO4PHYTRKPYNSUC6FMA3T2AEEIVAVCNFSM6AAAAABRIRVV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYHEZTANBRG4 . You are receiving this because you authored the thread.Message ID: @.***>

[andersevenrud]

Norwegian :) You can contact me on gmail (same username as on github).

[andersevenrud]

Conclusion from discussion via email: Bridge3 firmware is basically same as Bridge2. Support has been added.