home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.88k stars 29.56k forks source link

[TP-Link LTE] No modem available on TP-Link MR100 #88000

Closed Aeris1One closed 2 weeks ago

Aeris1One commented 1 year ago

The problem

When configuring tplink_lte to send SMS through my TP-Link MR100 router, there's some weird error when trying to call notify.name_in_config to send a test notification.

What version of Home Assistant Core has the issue?

core-2023.2.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

tplink_lte

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink_lte

Diagnostics information

n/a

Example YAML snippet

configuration.yaml

tplink_lte:
  - host: 192.168.0.1
    password: 000000
    notify:
      - name: name_in_config
        recipient: "+33000000000"

Development tools -> Services

service: notify.name_in_config
data:
  message: Test

Anything in the logs that might be useful for us?

2023-02-13 12:59:01.782 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
2023-02-13 12:59:19.341 ERROR (MainThread) [homeassistant.components.tplink_lte.notify] No modem available

Additional information

No response

home-assistant[bot] commented 1 year ago

tplink_lte documentation tplink_lte source

browetd commented 1 year ago

Same behaviour ("notify" services created but when I try to send a SMS, I have this error message: "no modem available") for Tp-Link MR600...

cmer81 commented 1 year ago

Hello,

Same issue for me with a Tp-Link MR600 :(

[homeassistant.components.tplink_lte.notify] No modem available

1shoot commented 1 year ago

Hi,

Same issue for me with a Tp-Link MR600,

Can you fix it ?

issue-triage-workflows[bot] commented 1 year ago

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.

Aeris1One commented 1 year ago

Still occuring on latest version. Not stale.

issue-triage-workflows[bot] commented 9 months ago

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.

Aeris1One commented 9 months ago

Still occuring. Not stale.

issue-triage-workflows[bot] commented 6 months ago

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.

Aeris1One commented 6 months ago

not stale :)

issue-triage-workflows[bot] commented 3 months ago

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.

Aeris1One commented 3 months ago

still unsolved 🙂

issue-triage-workflows[bot] commented 3 weeks ago

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.

Aeris1One commented 2 weeks ago

still a thing