Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning HASS code 500 creating sensor #41

Open
nortuzar opened this issue Mar 17, 2020 · 3 comments
Open

Warning HASS code 500 creating sensor #41

nortuzar opened this issue Mar 17, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@nortuzar
Copy link

nortuzar commented Mar 17, 2020

Hi, I change mi rasp zero W for a rasp 3 with external dongle, to compare the bluetooth range.
I set everything and in the debug log I can see that the appdaemon create the sensor in the web but it show an error when registering on HA. Error code 500, any idea?
Nothing of the info of the table is registered on HA
image

2020-03-17 11:25:46.448187 INFO home_presence_app: Creating sensor 'sensor.monitor_t_band_rasp-monitor_conf' for Confidence 2020-03-17 11:25:46.451220 DEBUG home_presence_app: set state: sensor.monitor_t_band_rasp-monitor_conf, {'state': 62, 'attributes': {'friendly_name': 'T Band Rasp-Monitor Confidence', 'unit_of_measurement': '%'}} 2020-03-17 11:25:46.453539 WARNING home_presence_app: home_presence_app: Entity sensor.monitor_t_band_rasp-monitor_conf not found in namespace default 2020-03-17 11:25:46.457314 INFO AppDaemon: home_presence_app: Entity sensor.monitor_t_band_rasp-monitor_conf created in namespace: default 2020-03-17 11:25:46.588716 WARNING HASS: Error setting Home Assistant state default.sensor.monitor_t_band_rasp-monitor_conf, {'state': 62, 'attributes': {'friendly_name': 'T Band Rasp-Monitor Confidence', 'unit_of_measurement': '%'}} 2020-03-17 11:25:46.590961 WARNING HASS: Code: 500, error: 500 Internal Server Error Server got itself in trouble

Also another question to avoid making more mistakes.

In the app daemon I have already set;
user_device_domain: device_tracker
known_beacons:

I want to use 2 nodes, one rasp W and one rasp 3 with dongle. Here I need to set up inside each one the following options or because they are already defined on the appdaemon there is no need?
KNOWN BEACON DEVICES
PREF_DEVICE_TRACKER_REPORT=TRUE

Thanks for the great app

@Odianosen25
Copy link
Owner

Hello @nortuzar,

I am sorry took so long to respond, I actually don’t remember getting the notification for it. Anyway in your first question I think it has to do with the device tracker, I will need to check that.

On the second you don’t need to specify known_devices in both nodes and the app will do it for you. But as for the other, you need to manually do it am afraid.

Regards

@Odianosen25 Odianosen25 added the bug Something isn't working label Apr 8, 2020
@eklee
Copy link

eklee commented Jun 14, 2020

Hi, any updates on this bug? I am also seeing the same errors when the script is try to create the confidence sensors. They are not created in HA nor in AD.

@Odianosen25
Copy link
Owner

@eklee,

I haven't been able to fix this yet am afraid, as I don't use the device tracker. I will need to seek out time to look at this, as been very busy of late.

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants