Error fetching bring data: Unable to connect and retrieve data from bring about core

[tr4nt0r]

@home-assistant close

[jocamane]

@home-assistant reopen

[tr4nt0r]

@mib1185 I'm not the one trying to do anything. The BRING integration is working well. I can see all the lists and the items that are there. Errors appear in the HA core log from time to time (about 12 hours), but apparently everything is OK. I've already tried deleting the integration and putting it back together, everything goes fine, but after a while the error appears again.

Thanks

Hi @jocamane
as @mib1185 already mentioned, that error is nothing to worry about, just an error in the network communication with the Bring service, i also get these errors regularly. Bad Gateway indicates the error is on the server side and there is nothing we can do aside from wait and retry. Errors like this will always happen from time to time and operation will usually recover to normal. If an error persists you should maybe investigate, otherwise it is safe to ignore it.

I will try to update the error messages and make it sound less alarming ^^

[mib1185]

Hi,
first, please calm down - we do this all in our free spare time and it's just an error message from time to time (caused by an server side error, not HA side!). Since we are not affiliated in any kind with Bring, we can't say anything about the cause of this outage of their servers.
What we could do is fetch this particular ClientResponseError and wrap it into the UpdateFailed error, which is properly handled by HA. There would still be an entry in your log, but not such prominent. (what @tr4nt0r has also mentioned earlier in #118043 (comment))

[home-assistant]

Hey there @miaucl, @tr4nt0r, mind taking a look at this issue as it has been labeled with an integration (bring) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of bring can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign bring Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

bring documentation
bring source
_{^{(message by IssueLinks)}}

[mib1185]

message='Bad Gateway' often indicates an issue with the webservice itself, so on the very first I would suggest to try it later again

[jocamane]

@mib1185 I'm not the one trying to do anything. The BRING integration is working well. I can see all the lists and the items that are there. Errors appear in the HA core log from time to time (about 12 hours), but apparently everything is OK. I've already tried deleting the integration and putting it back together, everything goes fine, but after a while the error appears again.

Thanks

[jocamane]

This error has been happening for more than 6 months. Isn't that enough to investigate? OK

[jocamane]

No error or warning is normal in any application in the world. If there is an error, it is because something is not right, so it must be investigated.

[tr4nt0r]

No error or warning is normal in any application in the world. If there is an error, it is because something is not right, so it must be investigated.

Internet connections are never 100% reliable by nature, Services like bring can produce errors, for example if servers are overloaded with too many requests. These errors are normal, they are expected to happen. If they happen too often, only then it is required to take action. In this case especially, there is nothing i can do in the bring integration or the bring-api library to fix them, aside from throwing an error and retrying again later, which is already happening in the Integration and Home Assistant takes care of retrying later.
Also this an error on the server side. If you think this should be addressed somehow, please open a ticket directly with the company that provides the service for the Bring App. You can send an e-mail to [email protected]
Please also be aware, that we, the maintainers, are not in any way affiliated with bring and this integration is not officially supported by Bring Labs.

[jocamane]

Do not worry.
I will stop using Bring integration in Home assistant.
It's always better than having a log full of errors every day

[tr4nt0r]

Do not worry. I will stop using Bring integration in Home assistant. It's always better than having a log full of errors every day

I'm ok with that. I'm doing this for free in my spare time and don't get paid for it. If you don't like it, don't use it🤷‍♂️

Also please refer to this passage of the License:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

[jocamane]

exactly

[jocamane]

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

Regarding the software, I have nothing to do with it

[tr4nt0r]

Hi, first, please calm down - we do this all in our free spare time and it's just an error message from time to time (caused by an server side error, not HA side!). Since we are not affiliated in any kind with Bring, we can't say anything about the cause of this outage of their servers. What we could do is fetch this particular ClientResponseError and wrap it into the UpdateFailed error, which is properly handled by HA. There would still be an entry in your log, but not such prominent. (what @tr4nt0r has also mentioned earlier in #118043 (comment))

ClientResponseError is already handled by UpdateFailed, hence the first message in the error log

Error fetching bring data: Unable to connect and retrieve data from bring

The second error log comes from the upstream library, which logs an error with the full stack trace. This has already been addressed, the current version 0.7.1 of bring-api is a lot less talkative and will log these messages only if debug is enabled.

The library will be updated to v0.7.1 in the next Home Assistant main release

• #115532