Are you using HTTPS for both internal_url & external_url?
The Home Remote uses both URLs. I think in most cases, systems use standard HTTP for internal/local access. If you are trying to link Home Assistant on your local network, Home Remote should be using your internal_url. It almost sounds like you’ve got HTTPS enabled on your internal_url.
So I made a trial with a new ddns server on my Synology NAS. I was able to generate a trusted certificate from Let’s Encrypt and set the right files in Home Assistant. Now when I try to access Home Assistant from the https call I don’t get anymore the nasty messages from the browser, which makes me think that I have now a trusted certificate. When I now try to add Home Assistant from the Android tablet I continue to get the error net::ERR_EMPTY_RESPONSE
Same error from the browsers, when I try to access HA from http://x.x.x.x:8123.
I believe that I have set up HA to use https from external and http from internal with the following instruction in customize.yaml:
internal_url: http://x.x.x.x:8123
external_url: https://.synology.me
but calling http://x.x.x.x:8123 will fail with no response, https://x.x.x.x:8123 gives me a nasty message saying that the certificate is linked to .synology.me and not x.x.x.x:8123, which makes sense. So for some reason HA does not respond to the internal call.
Any idea?
I don’t think you can have both HTTP & HTTPS on the same port. I’m not sure how that would work. So I kind of expect you’ll see “no response”. I also expect you’ll see errors when trying to connect using https://x.x.x.x:8123 because the Let’s Encrypt cert requires a domain name. I think you need to somehow set up 2 unique ports for both HTTP & HTTPS but I’m not sure how to do that.
Take a look through this discussion. I believe this user is experiencing the same issue you are.
Bill,
I finally managed to get both internal and external calls to be working (it even seems to have improved the overall performance of Home Assistant). I used the NGINX app but only following the instruction would not work. Following the instructions from this site https://companion.home-assistant.io/docs/troubleshooting/networking allowed a proper functioning (I am giving this in case others have troubles). I am now playing a little with it and it is just amazing the power of getting both applications to work together!
Now I ran into a little issue you may be helpful. I have all my radiators equipped with Z-Wave thermostats. I can pretty well communicate with each of them. The issue is that when I increment the ThermostatHeatingSetpoint to a value that is not an integer (ie 20.5) I get the following error: "expected float for dictionary value @ data[‘temperature’] and the value is not set in the thermostat. Any integer value works fine. If I do the same from Home Assistant it works fine. So I tried from the straight SettingsReset example you sent using the built in thermostat template and the same happens. I guess this must be linked to some interface with Home Assistant.
Thanks,
Daniel
I just fixed this on my dev machine. It’ll be part of the 4.1.4 release which should be out in a few days.
Refresh my memory. What are you referring to?
The thermostat setpoint fixes should have been in the 4.1.4 release. That is live in all of the app stores.
I did quote you but it’s a bit strange how this forum handles quotes.
I meant about your reply here:
Yeah, nested groups aren’t currently going to work. This can probably be added to a future release though.
Yes. That is something I still have to work on yet.
Cool ty.
Not trying to rush you or anything but do you have an ETA? Just trying to decide whether to bite the bullet and build the whole thing manually one by one or keep waiting for nested groups to work which in turn would mean the whole app would be dynamic and any device I may add in the future would automagically appear in the right place based on groups
I don’t think I’ll have time to include it in the next release. If I had to guess, I’d say sometime May.
OK thanks for letting me know.
Think I’ll may have to go the manual route then, was really trying to avoid it 