core
core copied to clipboard
Connection to TP-Link LTE router fails with MR-6400 v5
The problem
Hello,
Login to TP-Link LTE router with the tplink_lte
core integration fails at login time, preventing the associated SMS service to be instantiated.
Declared issue here with HA core 2022.6.6
but actually never worked even with pre-2022.
My TP-Link LTE router is MR6400, running firmware v5.
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/tplink_lte/__init__.py", line 122, in _setup_lte
await _login(hass, modem_data, password)
File "/usr/src/homeassistant/homeassistant/components/tplink_lte/__init__.py", line 137, in _login
await modem_data.modem.login(password=password)
File "/usr/local/lib/python3.9/site-packages/tp_connected/tp_connected.py", line 130, in login
await self.encryptCredentials(password, username)
File "/usr/local/lib/python3.9/site-packages/tp_connected/tp_connected.py", line 114, in encryptCredentials
_LOGGER.debug("ee: {0} nn: {1}".format(ee, nn))
UnboundLocalError: local variable 'nn' referenced before assignment
What version of Home Assistant Core has the issue?
core-2022-6-6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
TP-Link LTE
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink_lte/
Diagnostics information
No response
Example YAML snippet
tplink_lte:
- host: local.ip.address.here
password: !secret tplink_lte_password
notify:
- name: SMSGatewaySurname
recipient: "+xxx"
Anything in the logs that might be useful for us?
No response
Additional information
No response
tplink_lte documentation tplink_lte source (message by IssueLinks)
Hi I have the MR6400 V5 and am having the same problem.
Logger: homeassistant Source: components/tplink_lte/init.py:137 First occurred: 7:45:04 PM (1 occurrences) Last logged: 7:45:04 PM
Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/tplink_lte/init.py", line 122, in _setup_lte await _login(hass, modem_data, password) File "/usr/src/homeassistant/homeassistant/components/tplink_lte/init.py", line 137, in _login await modem_data.modem.login(password=password) File "/usr/local/lib/python3.10/site-packages/tp_connected/tp_connected.py", line 130, in login await self.encryptCredentials(password, username) File "/usr/local/lib/python3.10/site-packages/tp_connected/tp_connected.py", line 114, in encryptCredentials _LOGGER.debug("ee: {0} nn: {1}".format(ee, nn)) UnboundLocalError: local variable 'nn' referenced before assignment
What version of Home Assistant Core has the issue? Home Assistant 2022.7.2 Supervisor 2022.07.0 Operating System 9.0.dev20220601 Frontend 20220707.0 - latest
Integration causing the issue TP-Link LTE
I suspect this warning in router log is related V2 igmp router occured! Not matching ours V3.
Please anyone know how to fix this addon. Its the only way i can get sms notifications if my smoke alarms go off?
Hello,
Same issue here with Home Assistant 2022.8.7 container and TP-Link Archer MR600 V1 router.
Info on the TP-link:
Firmware version: 1.3.0 0.9.1 v0001.0 Build 210608 RC.66100n Hardware Version: Archer MR600 v1 00000001
The logs:
2022-09-01 05:39:32.430 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/tplink_lte/__init__.py", line 122, in _setup_lte
await _login(hass, modem_data, password)
File "/usr/src/homeassistant/homeassistant/components/tplink_lte/__init__.py", line 137, in _login
await modem_data.modem.login(password=password)
File "/usr/local/lib/python3.10/site-packages/tp_connected/tp_connected.py", line 130, in login
await self.encryptCredentials(password, username)
File "/usr/local/lib/python3.10/site-packages/tp_connected/tp_connected.py", line 114, in encryptCredentials
_LOGGER.debug("ee: {0} nn: {1}".format(ee, nn))
UnboundLocalError: local variable 'nn' referenced before assignment
Is it possible to correct this please?
Hello @Michsior14
Could you look for errors please?
@Rathorian Unfortunately I am not a maintainer of tp_connected
and don't have equipment to test it. Anyway I can see nn
being not always initialized before the debug is done (https://github.com/andtos90/tp-connected/blob/master/tp_connected/tp_connected.py#L115). Adjusting this will probably not fix the core issue of not getting response, but at least will make sure the logs are a bit more helpful.
I will try to open the PR in the library during the weekend if no one will do it before.
@Michsior14
Sorry, I mistakenly thought you were keeping the embed.
I admit I don't know Python, if you already have the possibility of doing a PR to solve this problem, that would be super nice. Thanks to you
I will try to find the maintainer and see with him for the rest.
Hello @andtos90
Would you be able to look at the problem above please? I would love to be able to use it....
Thanks
I'm also looking forward on a solution since I got a brand new TP-Link LTE router. I have the same problem.
I have the same issue with tp-link TL-MR6400
Running on RPi4: Home Assistant 2022.11.4 Supervisor 2022.10.2 Operating System 9.3 Frontend 20221108.0 - latest
Log:
Logger: tp_connected.tp_connected
Source: components/tplink_lte/__init__.py:137
First occurred: 20:06:35 (1 occurrences)
Last logged: 20:06:35
Invalid encryption key request
Who is the author of this integration, have we not got a resolution to this issue as I have order to link LTE router MR6500 and hoping this to work
@ausfas - I support this question/request. In the integration github page there is no owner (the field in manifest.json) is empty. The oldest history of this integration shows that @balloob has "Embed all platforms into components..." on February 2, 2019. It also shows that @bdraco has added loggers to manifest.json on January 28, 2022. Do not know what can I do more to get this resolved....
What can be done if there is no response to the issues registered ? Should we make a request to remove this integration fro the list since it does not work? On the Integration page of HA it says that it is used by 24 active installations - which probably means that it is installed in such number of installations but if it working ?
same issue here with MR500.
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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.