-
Notifications
You must be signed in to change notification settings - Fork 32
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.
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
cannot read property 'homepage' of undefined #56
Comments
Since you're not specifying a sitemap, have you set up a site map named "homekit.sitemap"? |
yes in the same directory as the default.sitemap. I did try to add it by appending "--sitemap" "homekit" but that yielded the same results |
Can you open http://10.0.1.15:8080/rest/sitemaps/homekit in a web browser? |
Yes i can, I was also experimenting with Homebridge and there the sitemap works. No items are in groups or frames. Everything is added like the description on this repo's README.md |
I'm not sure I remember right, but I don't think I could use # for comments in the sitemap if you have copied from the example. |
I will test if it starts without the #'s, will post results |
Did the comments have any effect? Please post your sitemap if the problem still exists. |
Your problem is most likely having set up a username and password. Try to use "user:[email protected]:8080". Otherwise, sitemap download will fail, because of basic auth. |
I'm experiencing the same error:
I've set a default.sitemap as below:
Also I tried the method @niwakame suggested, didn't male any difference. And I cannot open/rest/sitemaps/default , it gave me this:
but just http://192.168.1.101:8080/ works fine and redirects to http://192.168.1.101:8080/openhab.app I have another bridge running just fine with the same config, not sure why this happened. |
It turned out to be caused by java. After manually killed the java and openhab process then restart openhab, the REST API became reachable, and the bridge worked fine! Took me an hour to figure out though... silly me 😂 |
I am trying to start the Node server from my Macbook but getting this error:
The text was updated successfully, but these errors were encountered: