"Unknown Error" when logging in

[PaleFlyer]

I had this running for 3+ months, and it suddenly died last month on me (On roughly May 18th). Not sure what happened, but I also lost the Garmin Connect integration (never really used, so meh) and the Hatch integration for my boys white noise makers (for full disclosure on everything that died.)

I just tried reinstalling the integration, as I keep getting this "unknown error" when I try to login. I deleted my account off the integration as I thought it might have been like a bad API key loaded or something, but it doesn't seem to want to let me login now. I can still see the device in the Emporia app, but I'm lost on trying to figure out what to do at this point, as I don't know if something in my network is preventing the integration from talking, or if I'm just being dumb, and forgetting which password is in use.

[magico13]

Hmm, not sure what would be different. I'm assuming you're on a relatively new version of Home Assistant and not a really old one, I'm not sure how far back is still functional, especially since the Python version must be 3.12 now I believe.

The email and password you use should be the same as you use for the app, not the one used for the Emporia forum. Make sure you can connect via the app if you're still having trouble logging in. If you keep getting errors only with Home Assistant, see if you can get more details from the logs. The Unknown Error doesn't help much but there might be a stack trace or another embedded error that gives more details as to what is wrong and/or where exactly it failed.

[PaleFlyer]

I found out Snort was blocking the plugin for some reason. So it was my router with Snort running in blocking mode.

…

On Sat, Jun 22, 2024, 20:20 Mike Marvin ***@***.***> wrote: Hmm, not sure what would be different. I'm assuming you're on a relatively new version of Home Assistant and not a really old one, I'm not sure how far back is still functional, especially since the Python version must be 3.12 now I believe. The email and password you use should be the same as you use for the app, not the one used for the Emporia forum. Make sure you can connect via the app if you're still having trouble logging in. If you keep getting errors only with Home Assistant, see if you can get more details from the logs. The Unknown Error doesn't help much but there might be a stack trace or another embedded error that gives more details as to what is wrong and/or where exactly it failed. — Reply to this email directly, view it on GitHub <#284 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRUFXBLSIC45623AOUWLYLZIYIDBAVCNFSM6AAAAABJQJSVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUGI3DCOBQGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[adamtar]

I found out Snort was blocking the plugin for some reason. So it was my router with Snort running in blocking mode.
…
On Sat, Jun 22, 2024, 20:20 Mike Marvin @.> wrote: Hmm, not sure what would be different. I'm assuming you're on a relatively new version of Home Assistant and not a really old one, I'm not sure how far back is still functional, especially since the Python version must be 3.12 now I believe. The email and password you use should be the same as you use for the app, not the one used for the Emporia forum. Make sure you can connect via the app if you're still having trouble logging in. If you keep getting errors only with Home Assistant, see if you can get more details from the logs. The Unknown Error doesn't help much but there might be a stack trace or another embedded error that gives more details as to what is wrong and/or where exactly it failed. — Reply to this email directly, view it on GitHub <#284 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRUFXBLSIC45623AOUWLYLZIYIDBAVCNFSM6AAAAABJQJSVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUGI3DCOBQGA . You are receiving this because you authored the thread.Message ID: @.>

@PaleFlyer how'd you identify this in your router? I have an asus gt-axe16000. I am trying to figure out if mine is doing the same thing. Thank you.

[PaleFlyer]

I found out Snort was blocking the plugin for some reason. So it was my router with Snort running in blocking mode.
…
On Sat, Jun 22, 2024, 20:20 Mike Marvin @.> wrote: Hmm, not sure what would be different. I'm assuming you're on a relatively new version of Home Assistant and not a really old one, I'm not sure how far back is still functional, especially since the Python version must be 3.12 now I believe. The email and password you use should be the same as you use for the app, not the one used for the Emporia forum. Make sure you can connect via the app if you're still having trouble logging in. If you keep getting errors only with Home Assistant, see if you can get more details from the logs. The Unknown Error doesn't help much but there might be a stack trace or another embedded error that gives more details as to what is wrong and/or where exactly it failed. — Reply to this email directly, view it on GitHub <#284 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRUFXBLSIC45623AOUWLYLZIYIDBAVCNFSM6AAAAABJQJSVWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUGI3DCOBQGA . You are receiving this because you authored the thread.Message ID: _@**.**_>

@PaleFlyer how'd you identify this in your router? I have an asus gt-axe16000. I am trying to figure out if mine is doing the same thing. Thank you.

Snort is an intrustion detection/prevention/blocking program, which to my knowledge you can't run on an ASUS router. (It's similar to Suricata). Unifi has something similar, but to my knowledge even if you were running OpenWRT/Tomato/equivalent, "residential" grade routers just don't have the horsepower to run an IP/ID protocol, and still maintain decent speeds, as it has a noticable impact on commercial grade equipment.