-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
Error setting up entry Netgear LM1200 for netgear_lte #108524
Comments
Hey there @tkdrob, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) netgear_lte documentation |
As another data point I'm seeing the same issue after I upgrade from a Netgear M1 -> M2. |
I'm seeing the same thing. I have a Netgear LB2120. Logger: homeassistant.config_entries Error setting up entry Netgear LB2120 for netgear_lte in HA v2024.1.6
|
Upgrading to HA 2024.1.6 has fixed the issue for me with the Netgear MR2100 |
I have recently acquired an LM1200 and can't figure out how to get HA to send or receive SMS. The integration seems to be working because I can see the SMS inbound message count increase when i send sms to the device, and I can use the delete SMS service but can't figure out how to retrieve the SMS text or send outbound SMS |
Hi there. Please refer to the docs for information on receiving SMS events. https://www.home-assistant.io/integrations/netgear_lte We use Github to only track issues with the code itself as this issue is given the OP's information. If you still cannot figure it out from the instructions, please head over to the Home Assistant Community forum or the Discord channel for support. As for this issue, I have been watching the comments and was not confident the latest patch release had anything to do with this issue. I am still trying to find out why the websocket is closed when we use it almost immediately. This seems to happen on slower machines which could make the case for a race condition. I assume everyone here has only one modem? All modems should work but I just wanted to ask. Has everyone removed the yaml config? What about removing yaml, restarting, and then setting up? This config flow update went through a lot of testing but alas I can't get everything right the first time around. |
I never used the original YAML version, but only the newer one available in the GUI. It worked fine for while, then I noticed it stopped working, even after deleting the device and readding it. I got it to work again briefly once, but no luck since. I did notice that there is a 302 redirect if I attempt to use curl to the modem LTE IP address and the ip address /index.html. Is there perhaps an issue with following the redirect? |
Only one modem here. The yaml config has been removed for some time. I have removed the integration completely and re-added it with no improvement. I will note that if I restart Home Assistant, sometimes it will connect as usual, but that's maybe one out of 5 times. As far as possible slowness goes, I am running on a virtual machine on a NAS server, which does well for me most of the time, but figure it may be a data point for you. |
Additionally, I set up Debug Logging and then removed and re-added the integration. Here's what showed up in my logs. I truncated the big JSON blob that it pulled as it had a lot of personal info (messages, phone numbers, IMEI, etc) that shows it does successfully initally connect to the modem.
|
Those on 2024.1.6, please get ready to live with it as I have raised it against 2024.2.0 and it was closed. With 2024.2.0 the issue will be at least permanent error for LB2120 not sure for others. Hoping others will start reporting too. |
Since some have reported occasional issue, the developer of this code
believes it's an ad-hoc issue and my issue was closed. But I have confirmed
it's fully broken in 2024.2.0, without fixing the code L2120 is useless to
me.
…On Sat, 10 Feb 2024, 12:07 am mdo77, ***@***.***> wrote:
Those on 2024.1.6, please get ready to live with it as I have raised it
against 2024.2.0 and it was closed. With 2024.2.0 the issue will be at
least permanent error for LB2120 not sure for others. Hoping others will
start reporting too.
Sorry, not sure I'm understand your wording there. If I have LB2120 and
upgrade to 2024.2 is it fixed? Or permanently erroring?
—
Reply to this email directly, view it on GitHub
<#108524 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKPZHS5DIYJ45Q6IAVIXHLYSYNSPAVCNFSM6AAAAABCDK6J36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVHA4TSMJSHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
On 2024.2.1 with LM1200, same issue. |
I knew, convince tkdrob to fix this issue.
I have started looking at buying Huwavi LTE can't afford to wait and have
it fixed.
…On Sat, 10 Feb 2024, 10:46 am Rich Ahrens, ***@***.***> wrote:
On 2024.2.1 with LM1200, same issue.
—
Reply to this email directly, view it on GitHub
<#108524 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKPZHUNT35V7M3QD4JUB2TYS2YOXAVCNFSM6AAAAABCDK6J36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWG42DMNJWHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Broken on 2024.2.1 with my Netgear MR2100 |
Same here on 2024.2.1 and Netgear LB2120. |
Same with 2024.2.1 and LM1200. All was fine when using YAML version. |
Same issue here, the integration is broken on 2024.2.1 with MR2100 |
For everyone here, either wait for the mitigation to be in the next patch release or manually make the change IF you know what you are doing. Have a look at the the above pull request for what to do after a restart. |
I updated my HA Core 20 2024.2.2 and while the integration does load now, it will only work for a couple minutes before the entities fall to an unavailable state. I also noticed that now most of the entities are disabled by default and I needed to enable them, but no data would show up. |
It appears that after enabling the entities, a restart of Home Assistant is necessary. |
It’s working again after the upgrade and for more than one hour now… thank you 😊 |
All good for me, thanks |
Works here too. Appreciate the help! |
It works after upgrade to 2024.2.2. Restart is necessary. Thanks! |
Works perfectly; thank you @tkdrob! Funnily enough, even though this is supposed to mitigate the issue by reloading the integration, it is working 100% of the time for me upon (re)starting HA, whereas on the previous release it failed 100% of the time. |
It's broken again with HA Core 2024.3.3.
If these log files can help
|
I'm not seeing any issues with HA Core 2024.3.3. I restarted HA Core only and then the rpi running hassio and all good for me mate! |
Not sure, rebooted RPI and modem yesterday didn't work but after your
message rebooted RPI...bingo ...all good, thanks
…On Mon, 25 Mar 2024, 8:43 pm Chris McCallum, ***@***.***> wrote:
I'm not seeing any issues with HA Core 2024.3.3. I restarted HA Core only
and then the rpi running hassio and all good for me mate!
—
Reply to this email directly, view it on GitHub
<#108524 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKPZHXRBUD3HDKXWZUUOZDYZ7WSXAVCNFSM6AAAAABCDK6J36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGU4TGNBUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Glad it's work for you now! |
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. |
The problem
Netgear LTE Modem Add-On has stopped working. Attempted to remove the device and add it again, but same error occurs.
Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 12:38:48 AM (6 occurrences)
Last logged: 11:40:57 AM
Error setting up entry Netgear LM1200 for netgear_lte
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/netgear_lte/init.py", line 223, in async_setup_entry
await _login(hass, modem_data, password)
File "/usr/src/homeassistant/homeassistant/components/netgear_lte/init.py", line 269, in _login
await modem_data.modem.login(password=password)
File "/usr/local/lib/python3.11/site-packages/eternalegypt/eternalegypt.py", line 114, in login
await self._login(password)
File "/usr/local/lib/python3.11/site-packages/eternalegypt/eternalegypt.py", line 128, in _login
async with self.websession.get(url) as response:
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 1187, in aenter
self._resp = await self._coro
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 421, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
What version of Home Assistant Core has the issue?
core-2024.1.4
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
Netgear LTE
Link to integration documentation on our website
https://www.home-assistant.io/integrations/netgear_lte
Diagnostics information
home-assistant_netgear_lte_2024-01-20T17-48-43.511Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: