Alexa Guard no longer works after renaming the entity

Describe the bug I updated to the latest version and Alexa Guard showed up. I tested it and it worked fine. I used the HASS rename function to rename the device (wanted to remove the letters/numbers at the end) and now it doesn’t work/show up. I see the following error in HASS:

An error occured accessing AlexaAPI: An exception of type JSONDecodeError occurred. Arguments:
('Expecting value: line 1 column 1 (char 0)',)

And a separate error:

Error while setting up platform alexa_media
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/alarm_control_panel.py", line 34, in setup_platform
    hass)  \
  File "/home/homeassistant/.homeassistant/custom_components/alexa_media/alarm_control_panel.py", line 70, in __init__
    guard_dict = (data['locationDetails']
TypeError: 'NoneType' object is not subscriptable

To Reproduce Not sure if this is what caused it but try renaming Alexa Guard panel in HASS.

Expected behavior Alexa Guard alarm panel showing up/functioning

System details

• Home-assistant (version): 0.94.3
• Hassio (Yes/No): No (hassbian)
• alexa_media (version from const.py or HA startup): 1.3
• alexapy (version from pip show alexapy or HA startup): 0.7

[alandtse]

Ok thanks for the info. I’ll explore that angle although it shouldn’t since we don’t use the ha entity name for anything.

[alandtse]

I took a closer look at the code and I don’t see why the renaming would do anything. I also tested renaming on my end (both entity_id and name) and didn’t see the issues you reported. I am using a newer version that handles the log errors you reported so that may have resolved it. I’ll close this when I make that live. If you run into it again please let me know.