As of HomeAssistant v0.100.0, API passwords have been disabled; The new method is to use "Long-Lived Access Tokens". Since API requests to homeassistant are now broken, the $printstat command fails. It is unable to query homeassistant for the light status by the 3d printer and does not fail gracefully (granted that is it's own issue that needs to be dealt with separately)
What the user see when issuing command $printstat:
Error on chatbot console:
Auth error in homeassistant log:
As of HomeAssistant v0.100.0, API passwords have been disabled; The new method is to use "Long-Lived Access Tokens". Since API requests to homeassistant are now broken, the $printstat command fails. It is unable to query homeassistant for the light status by the 3d printer and does not fail gracefully (granted that is it's own issue that needs to be dealt with separately)
**What the user see when issuing command $printstat:**

**Error on chatbot console:**

**Auth error in homeassistant log:**

Now that #3 is closed, it's apparent that first two screenshots no were not part of this specific issue. Those have been eliminated by gracefully handling the API error.
Now that #3 is closed, it's apparent that first two screenshots no were not part of this specific issue. Those have been eliminated by gracefully handling the API error.
created branch [`2-homeassistant-api-connection-is-broken`](/Bots/r0b3BOT/compare/master...2-homeassistant-api-connection-is-broken) to address this issue
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As of HomeAssistant v0.100.0, API passwords have been disabled; The new method is to use "Long-Lived Access Tokens". Since API requests to homeassistant are now broken, the $printstat command fails. It is unable to query homeassistant for the light status by the 3d printer and does not fail gracefully (granted that is it's own issue that needs to be dealt with separately)
What the user see when issuing command $printstat:
Error on chatbot console:
Auth error in homeassistant log:
Now that #3 is closed, it's apparent that first two screenshots no were not part of this specific issue. Those have been eliminated by gracefully handling the API error.
Issue is no longer breaking, we are now able to gracefully handle issue. Downgrading to "Bug".
Will need to use RESTful api, documented here: (https://developers.home-assistant.io/docs/en/external_api_rest.html)
created branch
2-homeassistant-api-connection-is-brokento address this issuementioned in merge request !6
mentioned in merge request !7
mentioned in merge request !8
mentioned in merge request !9
mentioned in merge request !10
mentioned in merge request !11
mentioned in merge request !12
closed via merge request !12
mentioned in commit
3a3846df85mentioned in merge request !13
mentioned in merge request !14
mentioned in merge request !15
mentioned in commit
1eedc900f2mentioned in merge request !16
mentioned in merge request !17
mentioned in merge request !18
mentioned in merge request !19
mentioned in merge request !20
mentioned in merge request !21
mentioned in merge request !22
mentioned in merge request !23
mentioned in merge request !24
mentioned in merge request !25
mentioned in merge request !26
mentioned in commit
fbc1b79b7cmentioned in merge request !27
mentioned in commit
349c0b9631mentioned in merge request !28
mentioned in commit
90d2808480mentioned in merge request !29
mentioned in commit
7cd570979dmentioned in merge request !30
mentioned in commit
e3f373333fmentioned in merge request !31
mentioned in commit
ce6ae512camentioned in merge request !32
mentioned in commit
37766daadamentioned in merge request !33
mentioned in commit
9180aef86ementioned in merge request !34
mentioned in commit
7a18bdcc43mentioned in merge request !35
mentioned in commit
18551d30aamentioned in merge request !36
mentioned in commit
16c68d3189mentioned in merge request !37
mentioned in commit
5083659dbf