-
-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AussieBroadBand Fails #95665
Comments
Hey there @nickw444, @Bre77, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) aussie_broadband documentation |
@yaleman we have another new service class. service['type']='Hardware' |
We do indeed! I'd love a PR please, I've got a lot on at the moment. 😅 |
If you guys need any information that will help fix this, I am happy to provide. For your information the account I am trying to use with is a business account with 1 VoIP Server, 1 PABX service, and 3 NBN connections (2 FTTN and 1 FTTP). |
The library's been updated, someone now needs to update it in Home Assistant and test. |
Already have. Still get error.
Specifically it says List index out of range.
I have 4 accounts in total added, and 3 working (standard just internet on those accounts) and 1 (the business account) is the only one not working.
…On Sat, 26 Aug 2023, 12:48 pm James Hodgkinson, ***@***.***> wrote:
The library's been updated <https://pypi.org/project/pyaussiebb/>,
someone now needs to update it in Home Assistant and test.
—
Reply to this email directly, view it on GitHub
<#95665 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA57WUQLXUBLLHMMDVAPKJLXXFPYXANCNFSM6AAAAAAZ2WH6IY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Then you're going to have to provide something more than "List index out of range" please, because that's decidedly NOT specific. You already ignored the original error message and posted about it on the wrong github repo, how about giving me something to work with. |
I'll get onto this @yaleman, thanks for picking up my slack on this one. |
Just updated to 2023.9.0 and the problem is still there. 1 out ofr 4 of my services will not load. The error message I get is: 400, message='Bad Request', url=URL('https://myaussie-api.aussiebroadband.com.au/broadband/2345798/usage') And for reference, after logging into myaussie, when I go to the link in the error message I get this: {"message":"This service is not a broadband service."} The account in question has 2 x VoIP Services, 2 FTTN NBN Services, 1 Fibre Service and 1 Hardware |
That'll probably be the ID for the Hardware or something, can you look at the response to https://myaussie-api.aussiebroadband.com.au/services when you log into myaussie? |
|
Yep, that's the hardware. |
Why is this closed? THe problem and error is still there. Just applied all updates minutes ago and the error still exists. This is NOT SOLVED/FIXED. |
Home Assistant closes issues automatically when targeted by a PR. Are you getting the same error as the original issue, or a new error saying it's not a broadband service? I believe the latter is expected behaviour. You said only three services work, is that your 2x NBN and 1x Fibre? If so it sounds like everything is working as expected. |
Not everything works as expected. I have 3 separate accounts. 2 of the accounts work perfectly. It's the one with the above error that errors. How is an error expected functionality?? The account with an error, has 2 Fibre and a FTTN service, and a Hosted PBX service. Nothing shows for anything under that account. The error stops anything from coming thru for that account. The json dump I posted last, is from that account, and nothing shows in Home Assistant. I simply get an error on the addon and then nothing works. Personally an outright error should never be expected behaviour. It should fail cleanly, as in if it is indeed the hardware part that is causing the problem. Ignore it then. This should then allow at least the broadband services to work. |
I think it wasn't clear. When I said I had 3 services working, I mean, accounts. 3 separate accounts, each with only a single broadband service on them and nothing more. The error one, is a 4th Account, that has 3 NBN services and the Hosted PBX. |
Right, I understand now. I've spoken with @yaleman and we'll need to establish a new path forward given the pyAussieBB library and Home Assistant are currently incompatible. |
This one should be patchable in the same way as the previous fix, with a silent ignore-errors handler for that device type in... wherever the error's occurring. |
@home-assistant reopen |
Found the actual root cause, PR has been raised to fix this. Its my fault for not looking at the full error message in the first place, because the issue was rather simple. |
Thanks heaps. I'm not familiar with the placing/patching process, how long can I expect before this fix should be in? |
Either in a few days or a month. |
The fixes have been shipped in 2023.10.0b7, so will also be in 2023.10 |
Ive updated and still broken. Home Assistant 2023.10.0 Is there any information I can share to help get this fixed? |
A fresh copy of your logs where is failing in a new issue would be best. |
How do I get them? The error message I get is "Service 2345798 was unrecognised" I also enabled debug logs a while ago but I cant find anything in the logs, but not sure I am looking in the correct place. |
The only thing I can find in the logs is this: 2023-10-09 13:55:21.316 WARNING (MainThread) [homeassistant.config_entries] Config entry 'allsetsolutions' for aussie_broadband integration not ready yet: Service 2345798 was unrecognised; Retrying in background |
If it's still looking for that hardware item, Home Assistant has probably kept that entity going - try and disable it or something.
…On 2023-10-09 13:11 Shaun Williams wrote:
The only thing I can find in the logs is this:
2023-10-09 13:55:21.316 WARNING (MainThread) [homeassistant.config_entries] Config entry 'allsetsolutions' for aussie_broadband integration not ready yet: Service 2345798 was unrecognised; Retrying in background
—
Reply to this email directly, view it on GitHub <#95665 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJB7A7MFEGPBX7NOYMAR3X6NTMJAVCNFSM6AAAAAAZ2WH6I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGI4DQMRVGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Try to remove your Aussie Broadband account from Home Assistant and add it back again. |
Already tried removing and readding several times, just the entity and also the entire addon too. On 2 different systems as well. I get the same error. |
Why is this closed? Ive now done another update to 2023.10.1 and this is still not fixed? |
@home-assistant reopen |
What is happening with this? Is there anything I should be doing? |
This isn't a full-time job for the people helping you @eangulus, I'm sure it'll get looked at when someone has time. |
I wasn't hurrying anyone. I was simply making sure I have done everything I needed to do for this to then get picked up and looked at. I didn't know if anyone was waiting on logs, or more information from me. |
@eangulus can you please go to devices and see if you can find Service 2345798 (its name will be whatever its called in MyAussie). If you can click on it, click the pencil in the top right, and disable it, then restart Home Assistant. |
Just tried on one system where I don't have any other accounts other than the troubled one, there are no devices at all from the ABB add-on. I did check for already disabled devices too. I will check my home one where I have 3 different accounts. |
Just letting everyone know that nothing has changed (still fails) as of version: Core 2023.12.1 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
This should not be closed, as it hasnt been fixed yet. |
The problem
Have a myAussie account, with 3 NBN services and a Voip Service on it. This account fails in HA.
I have 3 other seperate accounts, each with a single NBN service and nothing else on theme, and they all work perfectly.
What version of Home Assistant Core has the issue?
core-2023.6.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
AussieBroadband
Link to integration documentation on our website
No response
Diagnostics information
Logger: homeassistant.components.aussie_broadband
Source: components/aussie_broadband/init.py:48
Integration: Aussie Broadband (documentation, issues)
First occurred: 7:38:43 PM (8 occurrences)
Last logged: 7:43:42 PM
Unexpected error fetching 2345798 data: list index out of range
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/aussie_broadband/init.py", line 45, in async_update_data
return await client.get_usage(service_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aussiebb/asyncio/init.py", line 404, in get_usage
self.validate_service_type(service)
File "/usr/local/lib/python3.11/site-packages/aussiebb/baseclass.py", line 116, in validate_service_type
raise UnrecognisedServiceType(
aussiebb.exceptions.UnrecognisedServiceType: Service type service['type']='Hardware' service['name']='Hardware' - not recognised - please raise an issue about this - https://github.com/yaleman/aussiebb/issues/new
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/aussie_broadband/init.py", line 48, in async_update_data
f"Service {service_id} of type '{services[service_id]['type']}' was"
~~~~~~~~^^^^^^^^^^^^
IndexError: list index out of range
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: