Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Home Assistant gets null exception during initialization #1150

Closed
tjedmunds opened this issue Nov 6, 2019 · 7 comments · Fixed by #1266
Closed

Home Assistant gets null exception during initialization #1150

tjedmunds opened this issue Nov 6, 2019 · 7 comments · Fixed by #1266
Assignees
@bwssytems
Labels
bug question
Milestone
5..4.0

Comments

@tjedmunds
Copy link

I am using the most recent version of hassio (Home Assistant). After entering IP, port and a long lived access token (not a legacy password) for authentication ha-bridge fails to initialize the hass information. Further digging in the logs finds the following:

Nov 05 19:30:17 smarthouse.lan java[31933]: 2019-11-05 19:30:17,156 [main] ERROR com.bwssystems.HABridge.plugins.hass.HassHome - Cannot get hass (smarthouse) setup, Exiting with message: null
Nov 05 19:30:17 smarthouse.lan java[31933]: java.lang.NullPointerException: null
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.plugins.hass.HomeAssistant.isLegacyAuth(HomeAssistant.java:111)
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.plugins.hass.HomeAssistant.(HomeAssistant.java:31)
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.plugins.hass.HassHome.createHome(HassHome.java:53)
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.plugins.hass.HassHome.(HassHome.java:34)
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.HomeManager.buildHomes(HomeManager.java:82)
Nov 05 19:30:17 smarthouse.lan java[31933]: at com.bwssystems.HABridge.HABridge.main(HABridge.java:92)
@bwssytems
Copy link
Owner

Will need to take a look at that

@tjedmunds
Copy link
Author

A workaround for this issue is to click the Legacy Password checkbox even though it isn't a legacy connection. Click Save. You will get a 500 error. Uncheck the checkbox and click Save again. Then it connects. Go figure.

@ceefin
Copy link

ceefin commented Nov 30, 2019

Can verify, had to go through this process myself after a recent upgrade to 0.102. Was previously using 0.96.x and the upgrade forced me to ditch the legacy password.

sidenote: thank you BWS!!!!

@JesusArmy
Copy link

A workaround for this issue is to click the Legacy Password checkbox even though it isn't a legacy connection. Click Save. You will get a 500 error. Uncheck the checkbox and click Save again. Then it connects. Go figure.

I confirm that this workaround did also the trick for me. Thanks tjedmunds and thanks a lot bwssystems for this wonderful lightweight piece of software!

@bwssytems bwssytems self-assigned this Feb 25, 2020
@aristosv
Copy link

I can confirm that this issue still exists, and the workaround also works.

I am using Debian buster and I followed this installation method

https://github.com/bwssytems/ha-bridge#manual-installation-of-ha-bridge-and-setup-of-systemd-service

@sanderlv
Copy link

sanderlv commented Nov 19, 2020 •
edited
Loading

I have a major down again... It worked and then I had no devices in habridge anymore. So I restarted, redid, retried... nothing... even not the trick from above. Sorry: SUCKS.

I think a recent upgrade to 0.118 did break my habridge - homeassistant relation

@sanderlv sanderlv mentioned this issue Nov 19, 2020
Closed
@bwssytems
Copy link
Owner

bwssytems commented Dec 14, 2020 •
edited
Loading

This is an issue with the initialization of the legacy auth setting. This will be in 5.4.0

@bwssytems bwssytems added the bug label Dec 14, 2020
@bwssytems bwssytems added this to the 5.3.1 milestone Dec 14, 2020
@bwssytems bwssytems mentioned this issue Dec 14, 2020
Merged
bwssytems added a commit that referenced this issue Dec 14, 2020
@bwssytems
Merge pull request #1266 from bwssytems/dev_branch_5.3.x
b3f2c25 
Dev branch 5.3.x to create v5.4.0

#1044 Alexa app, error "Device doesn't support requested value" bug question
#1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question
#1126 Can't get XY ColorData into URL enhancement question
#1127 Can't get separate hue, saturation and brightness enhancement question
#1128 Wrong color calucation in HS mode bug question
#1131 Changing color temperatur is not working correctly bug question
#1132 Conversion from CIE to RGB incorrect bug question
#1139 Device ID creation fails bug question
#1150 Home Assistant gets null exception during initialization bug question
#1170 Alexa not sending the correct color codes duplicate
#1171 Please add option: If bright request present with on, only send dim enhancement
#1184 Alexa will not discover HABridge question
#1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug
#1210 [Enahnacement] Have link button timeout be configurable enhancement
#1215 Alexa unable to discover recently added devices to ha-bridge duplicate question
#1227 Feature request: ${intensity.previous} value passing control enhancement
#1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question
#1243 Alexa device discovery now broke question
#1253 HABridge hue ColorDecode 0 0 0 bug question
#1256 Homeassistant devices not appearing bug question
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwssytems bwssytems

Labels
bug question
Projects
None yet
Milestone
5..4.0
Development

Successfully merging a pull request may close this issue.

Dev branch 5.3.x bwssytems/ha-bridge
6 participants
@aristosv @bwssytems @sanderlv @ceefin @tjedmunds @JesusArmy