HA entity is not created...complete silence over mqtt
See original GitHub issueDescribe the bug Room-assistant is not sending out mqtt updates. Apparently, it does register my iBeacon but it then doesn’t create an entity and never updates status over mqtt 😦 What am I doing wrong? To reproduce Steps required to reproduce the issue.
Relevant configuration Paste the relevant parts of your configuration below.
instanceName: the-office
integrations:
- bluetoothLowEnergy
- homeAssistant
homeAssistant:
mqttUrl: mqtt://192.168.1.195:1883
mqttOptions:
username: xxxxxxx
password: xxxxxxx
bluetoothLowEnergy:
whitelist:
- a50693a4e24fb1afcfc6eb07647825-5-6
- 5548a6779994
- e2c56db5dffb48d2b060d0f5a71096e0-0-0
channel: 'room_presence'
onlyIBeacon: true
Expected behavior expected to update entity.
Environment
- room-assistant version: 2.0.0
- installation type: [e.g. NodeJS, Docker, Hass.io]
- hardware: Raspberry Pi Zero W
- OS: [e.g. Linux, Windows, macOS]
Additional context
root@raspberrypi:/home/pi/room-assistant# /opt/nodejs/bin/room-assistant --verbose
[Nest] 574 - 2020-02-27 11:25:20 [ClusterService] Cannot find module '../build/Release/dns_sd_bindings'
Error: Cannot find module '../build/Release/dns_sd_bindings'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
at Function.Module._load (internal/modules/cjs/loader.js:497:25)
at Module.require (internal/modules/cjs/loader.js:626:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object.<anonymous> (/opt/nodejs/lib/node_modules/room-assistant/node_modules/mdns/lib/dns_sd.js:32:22)
at Module._compile (internal/modules/cjs/loader.js:678:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)
at Module.load (internal/modules/cjs/loader.js:589:32)
at tryModuleLoad (internal/modules/cjs/loader.js:528:12)
at Function.Module._load (internal/modules/cjs/loader.js:520:3)
[Nest] 574 - 2020-02-27 11:25:24 [NestFactory] Starting Nest application... +3878ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] AppModule dependencies initialized +3244ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] ConfigModule dependencies initialized +15ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] NestEmitterModule dependencies initialized +13ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] IntegrationsModule dependencies initialized +13ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] DiscoveryModule dependencies initialized +92ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] HomeAssistantModule dependencies initialized +16ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] ClusterModule dependencies initialized +13ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] ScheduleModule dependencies initialized +15ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] BluetoothLowEnergyModule dependencies initialized +22ms
[Nest] 574 - 2020-02-27 11:25:28 [InstanceLoader] EntitiesModule dependencies initialized +12ms
[Nest] 574 - 2020-02-27 11:25:28 [RoutesResolver] EntitiesController {/entities}: +148ms
[Nest] 574 - 2020-02-27 11:25:28 [RouterExplorer] Mapped {/, GET} route +84ms
[Nest] 574 - 2020-02-27 11:25:29 [HomeAssistantService] Successfully connected to MQTT broker at mqtt://192.168.1.195:1883
[Nest] 574 - 2020-02-27 11:25:30 [ClusterService] Dependency "mdns" was not found, automatic discovery has been disabled. You will have to provide the addresses of other room-assistant nodes manually in the config.
[Nest] 574 - 2020-02-27 11:25:30 [NestApplication] Nest application successfully started +22ms
[Nest] 574 - 2020-02-27 11:25:30 [ClusterService] the-office has been elected as leader
[Nest] 574 - 2020-02-27 11:25:30 [EntitiesService] Refreshing entity states
[Nest] 574 - 2020-02-27 11:25:33 [BluetoothLowEnergyService] Discovered new BLE peripheral fda50693a4e24fb1afcfc6eb07647825-5-6 with ID fda50693a4e24fb1afcfc6eb07647825-5-6 and RSSI -47
[Nest] 574 - 2020-02-27 12:20:13 [BluetoothLowEnergyService] Discovered new BLE peripheral 50765cb7d9ea4e2199a4fa879613a492-59716-24897 with ID 50765cb7d9ea4e2199a4fa879613a492-59716-24897 and RSSI -90
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Unable to create the entities (MQTT) - Configuration
I would like to read out my “xiaomi flower sensor” via Bluetooth with the help of a Zero-W. These values should then be...
Read more >HA ignores first mqtt state publish from zigbee2mqtt after restart
So before restart it was "Open". During start it switches to "Unavailable" for 2 minutes, then to "Closed" for ~5 minutes and then...
Read more >Rhasspy is Joining Nabu Casa - Announcements
I use Home Assistant with Rhasspy (base + 3 satellites), MQTT and node-RED; so I personally welcome closer integration with HA - but...
Read more >Fix list for IBM MQ Version 9.0.0 LTS
The following is a complete listing of available and scheduled fixes for Version 9.0 with the most recent fix at the top.
Read more >Home Assistant - Tasmota
You can use MQTT Discovery in HA to add sensors and other entities that are not discovered through Tasmota integration and associate them...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dedepene From the logs I can’t see any of the devices you have in your whitelist being discovered by room-assistant. Are the IDs correct as noted in the config? Does executing “sudo hcitool lescan” (while room-assistant is not running) list your iBeacons?
@Gio76 I think your bug is unrelated, as it it’s about Bluetooth Classic and not BLE. Did you try rebooting your host machine? Could anything else be using the Bluetooth adapter? What do the logs say?
The above logs have always been the same…both when the entities worked and didn’t work.