This is what i see in the log file:
2022-01-02T09:44:54.309872+01:00 bli server: B&O Halo remote (26070): 33286849: aliveMonitor: keepalive: send a PING
2022-01-02T09:44:56.294240+01:00 bli server: B&O Halo remote (26070): 33286849: aliveMonitor: timedout, notifying
2022-01-02T09:44:56.303549+01:00 bli server: B&O Halo remote (26070): 33286849: aliveMonitor: keepalive: timeout: table: 0x517c47c0 OPEN
2022-01-02T09:44:56.313167+01:00 bli server: B&O Halo remote (26070): 33286849: Closing connection, no activity in last 62 seconds.
2022-01-02T09:44:56.322727+01:00 bli server: B&O Halo remote (26070): 33286849: _scheduleConnectionRetry: starting wakeup timer 10s for msg:aliveMonitor: Connection is dead, retrying in 10 seconds
It keeps dying on me and as soon as I see the proximity sensor it keeps popping up with the logo. I have no macro running
On the error history:
2022-01-01T02:23:22.265469+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
2022-01-01T02:25:53.663522+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
2022-01-01T02:32:54.229901+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
2022-01-01T02:43:04.753775+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
2022-01-01T02:46:31.520333+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
2022-01-01T02:50:01.453135+01:00 bli server: B&O Halo remote (26070): 33286849: socket error: Unreachable host
On macro's:
No events or loops.
Login to view image Northing....
Halo on accespoint active.....However only for 4 hours and 53 minutes
It is a very expensive paperweight, I cannot use this. I will contact my dealer for a wired version I supose.
Chucky