Announcing home_assistant-ble to support bluetooth low energy device tracking for raspberry

Third party integrations
62

if “my_local_address”, is actually your public address, then that’s the problem.

Don’t use your public IP address, use your private internal IP address.

63

When i use my private internal IP address, i have a probleme with my SSL (from Letsencrypt):

Traceback (most recent call last):
        15: from /usr/local/bin/home_assistant-ble:23:in `<main>'
        14: from /usr/local/bin/home_assistant-ble:23:in `load'
        13: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/bin/home_assistant-ble:40:in `<top (required)>'
        12: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:69:in `run'
        11: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:69:in `loop'
        10: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:71:in `block in run'
         9: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:101:in `detect_new_devices'
         8: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:101:in `each'
         7: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:104:in `block in detect_new_devices'
         6: from /var/lib/gems/2.5.0/gems/home_assistant-ble-1.4.2/lib/home_assistant/ble.rb:139:in `update_home_assistant'
         5: from /usr/lib/ruby/2.5.0/net/http.rb:609:in `start'
         4: from /usr/lib/ruby/2.5.0/net/http.rb:909:in `start'
         3: from /usr/lib/ruby/2.5.0/net/http.rb:920:in `do_start'
         2: from /usr/lib/ruby/2.5.0/net/http.rb:985:in `connect'
         1: from /usr/lib/ruby/2.5.0/net/protocol.rb:44:in `ssl_socket_connect'
/usr/lib/ruby/2.5.0/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (unspecified certificate verification error) (OpenSSL::SSL::SSLError)
64

If you have LE certificate you must have HTTP enabled for renewal to work. You need to figure out your Let’s encrypt setup and connect via http, or resolve the SSL issue, which, most likely is that your SSL DNS name doesn’t actually match your local address. A workaround that might work is to add your public DNS name to /etc/hosts