You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone, I'm sorry it's my first post ever and I may not do as expected...
I have a problem on Node-RED on my Home Assistant OS : none of the BLE nodes that I try work (while they were working until yesterday !)
Before opening this issue, I tried many hours today, thinking that ChatGPT would offer me some help, but it was pointless. I have a lot of BLE sensors and every hour spent without this running is a lot of data wasted...
Add-on version: 18.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.12.5
Home Assistant Supervisor: 2024.12.3
Used node package : node-red-contrib-ble-sense
I think I updated my home assistant to the latest version this morning but I had probably done so only 2 months ago.
Expected behavior
BLE scanning, simply. I handle the rest with no problem. Have been doing so for years.
Actual behavior
Nothing scans, I just get errors like : Error scanning for devices: Error: Could not start scanning, state is unknown (not poweredOn)
I see my bluetooth devices in Home Assistant integrations
I can scan for BLE devices on Home Assistant Terminal (command bluetoothctl) and it works flawlessly.
When I tried playing in Node-RED (Exec nodes) with this kind of commands, bluetoothctl scan on or whatnot, it would tell me errors regarding dbus. I never tried before this problem so it might have never worked...
Steps to reproduce
"Luckily" I was trying to share my flow to a friend today, installing the nodes when I noticed it didn't work on HIS instance, and then went to mine to unfortunately see that it also happened to me, so I think anyone can reproduce it.
So, the steps to reproduce :
install Node-REDHome Assistant module
install node-red-contrib-ble-sense from the palette (I needed to add system packages python3, make, gcc, g++ in order to install)
import the example from the package.
try
Some of the things I tried so far
Rebooting
Reinstalling Node-RED (and removing its whole addon-config directory for a fresh start)
activating/deactivating/removing/... my bluetooth devices in Home Assistant
Crying/praying
Updating/restoring Home Assistant...
Thanks in advance for your help on this topic
The text was updated successfully, but these errors were encountered:
Any custom node may or may not work. Some need additional system packages; but that is up to you to handle. We can't provide support for all nodes out there.
Hi @frenck, I get it, but in my opinion it's not linked to custom node since all custom nodes with Bluetooth seem to act this way now (when they used to work, no change, no update on the custom nodes).
Any idea why Node-RED would stop accessing the bluetooth devices or why its authorizations/privileges may have changed ?
Any tip on how to give more privileges to Node-RED ?
Problem/Motivation
Hi everyone, I'm sorry it's my first post ever and I may not do as expected...
I have a problem on Node-RED on my Home Assistant OS : none of the BLE nodes that I try work (while they were working until yesterday !)
Before opening this issue, I tried many hours today, thinking that ChatGPT would offer me some help, but it was pointless. I have a lot of BLE sensors and every hour spent without this running is a lot of data wasted...
Add-on version: 18.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.12.5
Home Assistant Supervisor: 2024.12.3
Used node package : node-red-contrib-ble-sense
I think I updated my home assistant to the latest version this morning but I had probably done so only 2 months ago.
Expected behavior
BLE scanning, simply. I handle the rest with no problem. Have been doing so for years.
Actual behavior
Nothing scans, I just get errors like : Error scanning for devices: Error: Could not start scanning, state is unknown (not poweredOn)
I see my bluetooth devices in Home Assistant integrations
I can scan for BLE devices on Home Assistant Terminal (command bluetoothctl) and it works flawlessly.
When I tried playing in Node-RED (Exec nodes) with this kind of commands, bluetoothctl scan on or whatnot, it would tell me errors regarding dbus. I never tried before this problem so it might have never worked...
Steps to reproduce
"Luckily" I was trying to share my flow to a friend today, installing the nodes when I noticed it didn't work on HIS instance, and then went to mine to unfortunately see that it also happened to me, so I think anyone can reproduce it.
So, the steps to reproduce :
Some of the things I tried so far
Rebooting
Reinstalling Node-RED (and removing its whole addon-config directory for a fresh start)
activating/deactivating/removing/... my bluetooth devices in Home Assistant
Crying/praying
Updating/restoring Home Assistant...
Thanks in advance for your help on this topic
The text was updated successfully, but these errors were encountered: