Anyone did a ibeacon (or similar installation)

anon35356645 · April 27, 2017, 8:05pm

I don’t get it. Too difficult for me

yelti_be · April 27, 2017, 8:12pm

Can you post your config?

May we can start from there.
HASS is powerfull, but not extremely easy to get everything right the first time.

anon35356645 · April 27, 2017, 8:14pm

in configuration (mine is a hassbian 1.1 with embedded mqtt)

mqtt:
  broker: 192.168.1.238
  port: 1883
  client_id: home-assistant-2
  username: username
  password: password

in sensor

  - platform: mqtt_room
    device_id: e81b30d17295
    name: 'fitbit'
    state_topic: 'room_presence'

device_id I took from HB server.

When I interrogsate topic room_presence with a mqtt client I receive no value

yelti_be · April 27, 2017, 8:40pm

try with this: as state topic:

state_topic: ‘happy-bubbles/presence/ha’
Is your beacin visible in added beacons?

anon35356645 · April 27, 2017, 8:44pm

I will but is HB server changing that topic?? Because in my PAHO client that topic also shows nothing.

Yes that device_id is in Added Beacon (now I changed its name in HB server to fitbit)

yelti_be · April 27, 2017, 9:14pm

I have the following topic I subscribed to: ‘happy-bubbles/presence/ha/#’ in my mqttfx client.

and I see regular updates.

Could be HB server is not working well with bluetooth devices.
I use the miband and transform(node-red) the data to ibeacon format, maybe the developper of HB can elaborate how it handles bluetooth devices.

anon35356645 · April 28, 2017, 9:10am

I do not understand much. Now in my front end sensor.fitbit is present. But subscribing to
happy-bubbles/presence/ha
or
happy-bubbles/presence/ha/#

brings nothing

Topic
happy-bubbles/presence
has many text coming

anilet · April 28, 2017, 2:08pm

Are you running presence server?. It collects all the changes from happy-bubbles/presence/changes
processes it and post the result to happy-bubbles/presence/ha.

anon35356645 · April 28, 2017, 2:22pm

after a while it works.

I nboticed changes are registered from 1 to 7 sefconds

yelti_be · April 28, 2017, 10:12pm

Perfect.

Now you can create automations and share your experiences
The delays are the reasons I intend to work with pir sensors as first trigger.

anon35356645 · April 28, 2017, 10:16pm

I think these are usefuel if you want to define the person (carrying different ibeacon), otherwise for same person, pir sensor are faster

farstreet · May 1, 2017, 6:16am

If anyone is still looking at a (for now) working set up with different beacons, together with the Happy Bubbles presence server and MQTT room, check out my config on GitHub.

Feel free to ask questions.

https://github.com/farstreet/my-home-assistant-configuration

zajnic · May 1, 2017, 11:07pm

Thank you for sharing. It would be useful when I get my order from Happy Bubbles soon! Still on its way from US to NZ!

anon35356645 · May 2, 2017, 11:37am

Hi, my happy-bubbles server crashes (now is second time).

How to

restart the service?
troubleshoot what happened?

dap35 · May 2, 2017, 11:44am

Assuming you are running on a current Linux type distribution (including Debian or RaspberryPi)

sudo systemctl restart presence.service

anon35356645 · May 2, 2017, 11:45am

I am on hassbian. I did the above but the webpage 192.168.1.238:5555 is not loading (ERR_CONNECTION_REFUSED)

Wonder what causes it to crashes

dap35 · May 2, 2017, 11:53am

So after you restart, it still doesn’t respond to a connection?

One thing I do is to open a second terminal session and run the following
sudo journalctl -fu presence.service

Then, in the first window, restart the service. The journalctl command is basically tracing the output of the service, so you can see what goes on during the start or operation.

I have not had any issues with my presence server, but I am running it on a seperate device, mainly as an excuse to get a PiZero.

chrio · May 2, 2017, 11:53am

Check the output from sudo journalctl -f in another terminal when you try to start the service, it might give you more info.

anon35356645 · May 2, 2017, 11:56am

pi@hassbian:~ $ sudo journalctl -fu presence.service
– Logs begin at Tue 2017-05-02 13:20:09 CEST. –
May 02 13:46:07 hassbian presence[20099]: panic(0x36dc00, 0x10764688)
May 02 13:46:07 hassbian presence[20099]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:46:07 hassbian presence[20099]: main.main()
May 02 13:46:07 hassbian presence[20099]: /code/happy-bubbles/presence-gh/main.go:639 +0xc00
May 02 13:46:07 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:46:07 hassbian systemd[1]: Stopping presence…
May 02 13:46:07 hassbian systemd[1]: Starting presence…
May 02 13:46:07 hassbian systemd[1]: presence.service start request repeated too quickly, refusing to start.
May 02 13:46:07 hassbian systemd[1]: Failed to start presence.
May 02 13:46:07 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:36 hassbian systemd[1]: Starting presence…
May 02 13:55:36 hassbian systemd[1]: Started presence.
May 02 13:55:36 hassbian presence[20516]: _ _ _ ____ ______ __ ____ _ _ ____ ____ _ _____ ____
May 02 13:55:36 hassbian presence[20516]: | | | | / \ | _ | _ \ \ / / | __ )| | | | __ )| __ )| | | / |
May 02 13:55:36 hassbian presence[20516]: | || | / _ \ | |) | |) \ V / | _ | | | | _ | _ | | | | _
May 02 13:55:36 hassbian presence[20516]: | _ |/ ___ | __/| __/ | | | |) | || | |) | |) | || |_ ) |
May 02 13:55:36 hassbian presence[20516]: || |// __| || || |/ ___/|/|/|||/
May 02 13:55:36 hassbian presence[20516]: CONNECTED TO MQTT
May 02 13:55:36 hassbian presence[20516]: Visit http://0.0.0.0:5555 on your browser to see the web interface
May 02 13:55:36 hassbian presence[20516]: EOF
May 02 13:55:36 hassbian presence[20516]: panic: the Client has not yet connected to the Server
May 02 13:55:36 hassbian presence[20516]: goroutine 1 [running]:
May 02 13:55:36 hassbian systemd[1]: presence.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 02 13:55:36 hassbian presence[20516]: panic(0x36dc00, 0x10764688)
May 02 13:55:36 hassbian presence[20516]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:55:36 hassbian presence[20516]: main.main()
May 02 13:55:36 hassbian presence[20516]: /code/happy-bubbles/presence-gh/main.go:639 +0xc00
May 02 13:55:36 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:37 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:55:37 hassbian systemd[1]: Stopping presence…
May 02 13:55:37 hassbian systemd[1]: Starting presence…
May 02 13:55:37 hassbian systemd[1]: Started presence.
May 02 13:55:37 hassbian presence[20529]: _ _ _ ____ ______ __ ____ _ _ ____ ____ _ _____ ____
May 02 13:55:37 hassbian presence[20529]: | | | | / \ | _ | _ \ \ / / | __ )| | | | __ )| __ )| | | / |
May 02 13:55:37 hassbian presence[20529]: | || | / _ \ | |) | |) \ V / | _ | | | | _ | _ | | | | _
May 02 13:55:37 hassbian presence[20529]: | _ |/ ___ | __/| __/ | | | |) | || | |) | |) | || |_ ) |
May 02 13:55:37 hassbian presence[20529]: || |// __| || || |/ ___/|/|/|||/
May 02 13:55:37 hassbian presence[20529]: CONNECTED TO MQTT
May 02 13:55:37 hassbian presence[20529]: Visit http://0.0.0.0:5555 on your browser to see the web interface
May 02 13:55:37 hassbian presence[20529]: EOF
May 02 13:55:38 hassbian presence[20529]: panic: the Client has not yet connected to the Server
May 02 13:55:38 hassbian presence[20529]: goroutine 24 [running]:
May 02 13:55:38 hassbian presence[20529]: panic(0x36dc00, 0x1076a410)
May 02 13:55:38 hassbian presence[20529]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:55:38 hassbian presence[20529]: main.getLikelyLocations(0x2d, 0x0, 0x8, 0x0, 0x10771ba0, 0x0, 0x0, 0x0, 0x0, 0x0, …)
May 02 13:55:38 hassbian presence[20529]: /code/happy-bubbles/presence-gh/main.go:386 +0x948
May 02 13:55:38 hassbian presence[20529]: main.IncomingMQTTProcessor.func3(0x10778960, 0x10771ba0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1077a480, 0x10776740)
May 02 13:55:38 hassbian presence[20529]: /code/happy-bubbles/presence-gh/main.go:477 +0x110
May 02 13:55:38 hassbian presence[20529]: created by main.IncomingMQTTProcessor
May 02 13:55:38 hassbian presence[20529]: /code/happy-bubbles/presence-gh/main.go:558 +0x2bc
May 02 13:55:38 hassbian systemd[1]: presence.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 02 13:55:38 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:38 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:55:38 hassbian systemd[1]: Stopping presence…
May 02 13:55:38 hassbian systemd[1]: Starting presence…
May 02 13:55:38 hassbian systemd[1]: Started presence.
May 02 13:55:38 hassbian presence[20539]: _ _ _ ____ ______ __ ____ _ _ ____ ____ _ _____ ____
May 02 13:55:38 hassbian presence[20539]: | | | | / \ | _ | _ \ \ / / | __ )| | | | __ )| __ )| | | / |
May 02 13:55:38 hassbian presence[20539]: | || | / _ \ | |) | |) \ V / | _ | | | | _ | _ | | | | _
May 02 13:55:38 hassbian presence[20539]: | _ |/ ___ | __/| __/ | | | |) | || | |) | |) | || |_ ) |
May 02 13:55:38 hassbian presence[20539]: || |// __| || || |/ ___/|/|/|||/
May 02 13:55:38 hassbian presence[20539]: CONNECTED TO MQTT
May 02 13:55:38 hassbian presence[20539]: Visit http://0.0.0.0:5555 on your browser to see the web interface
May 02 13:55:38 hassbian presence[20539]: EOF
May 02 13:55:38 hassbian presence[20539]: panic: the Client has not yet connected to the Server
May 02 13:55:38 hassbian presence[20539]: goroutine 1 [running]:
May 02 13:55:38 hassbian presence[20539]: panic(0x36dc00, 0x10764688)
May 02 13:55:38 hassbian presence[20539]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:55:38 hassbian presence[20539]: main.main()
May 02 13:55:38 hassbian presence[20539]: /code/happy-bubbles/presence-gh/main.go:639 +0xc00
May 02 13:55:38 hassbian systemd[1]: presence.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 02 13:55:38 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:38 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:55:38 hassbian systemd[1]: Stopping presence…
May 02 13:55:38 hassbian systemd[1]: Starting presence…
May 02 13:55:38 hassbian systemd[1]: Started presence.
May 02 13:55:38 hassbian presence[20549]: _ _ _ ____ ______ __ ____ _ _ ____ ____ _ _____ ____
May 02 13:55:38 hassbian presence[20549]: | | | | / \ | _ | _ \ \ / / | __ )| | | | __ )| __ )| | | / |
May 02 13:55:38 hassbian presence[20549]: | || | / _ \ | |) | |) \ V / | _ | | | | _ | _ | | | | _
May 02 13:55:38 hassbian presence[20549]: | _ |/ ___ | __/| __/ | | | |) | || | |) | |) | || |_ ) |
May 02 13:55:38 hassbian presence[20549]: || |// __| || || |/ ___/|/|/|||/
May 02 13:55:38 hassbian presence[20549]: CONNECTED TO MQTT
May 02 13:55:38 hassbian presence[20549]: Visit http://0.0.0.0:5555 on your browser to see the web interface
May 02 13:55:38 hassbian presence[20549]: EOF
May 02 13:55:38 hassbian presence[20549]: panic: the Client has not yet connected to the Server
May 02 13:55:38 hassbian presence[20549]: goroutine 1 [running]:
May 02 13:55:38 hassbian systemd[1]: presence.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 02 13:55:38 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:38 hassbian presence[20549]: panic(0x36dc00, 0x10764688)
May 02 13:55:38 hassbian presence[20549]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:55:38 hassbian presence[20549]: main.main()
May 02 13:55:38 hassbian presence[20549]: /code/happy-bubbles/presence-gh/main.go:639 +0xc00
May 02 13:55:38 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:55:38 hassbian systemd[1]: Stopping presence…
May 02 13:55:38 hassbian systemd[1]: Starting presence…
May 02 13:55:38 hassbian systemd[1]: Started presence.
May 02 13:55:38 hassbian presence[20560]: _ _ _ ____ ______ __ ____ _ _ ____ ____ _ _____ ____
May 02 13:55:38 hassbian presence[20560]: | | | | / \ | _ | _ \ \ / / | __ )| | | | __ )| __ )| | | / |
May 02 13:55:38 hassbian presence[20560]: | || | / _ \ | |) | |) \ V / | _ | | | | _ | _ | | | | _
May 02 13:55:38 hassbian presence[20560]: | _ |/ ___ | __/| __/ | | | |) | || | |) | |) | || |_ ) |
May 02 13:55:38 hassbian presence[20560]: || |// __| || || |/ ___/|/|/|||/
May 02 13:55:38 hassbian presence[20560]: CONNECTED TO MQTT
May 02 13:55:38 hassbian presence[20560]: Visit http://0.0.0.0:5555 on your browser to see the web interface
May 02 13:55:38 hassbian presence[20560]: EOF
May 02 13:55:38 hassbian presence[20560]: panic: the Client has not yet connected to the Server
May 02 13:55:38 hassbian presence[20560]: goroutine 1 [running]:
May 02 13:55:38 hassbian presence[20560]: panic(0x36dc00, 0x1071c6c0)
May 02 13:55:38 hassbian presence[20560]: /code/go/go/src/runtime/panic.go:481 +0x330
May 02 13:55:38 hassbian presence[20560]: main.main()
May 02 13:55:38 hassbian presence[20560]: /code/happy-bubbles/presence-gh/main.go:639 +0xc00
May 02 13:55:38 hassbian systemd[1]: presence.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 02 13:55:38 hassbian systemd[1]: Unit presence.service entered failed state.
May 02 13:55:39 hassbian systemd[1]: presence.service holdoff time over, scheduling restart.
May 02 13:55:39 hassbian systemd[1]: Stopping presence…
May 02 13:55:39 hassbian systemd[1]: Starting presence…
May 02 13:55:39 hassbian systemd[1]: presence.service start request repeated too quickly, refusing to start.
May 02 13:55:39 hassbian systemd[1]: Failed to start presence.
May 02 13:55:39 hassbian systemd[1]: Unit presence.service entered failed state.

anon35356645 · May 2, 2017, 12:43pm

@chrio

any idea on what to do?