Error requesting sensor data
See original GitHub issueVersion of the custom_component
1.0
Configuration
Add your logs here.
Describe the bug
I’ve installed the custom component and I was able to add it in the integration page. However, I’m not getting the sensors in my HA. I might be missing something, but I don’t know what.
Debug log
Logger: custom_components.google_home
Source: helpers/update_coordinator.py:160
Integration: Google Home (documentation, issues)
First occurred: 10:53:42 (3 occurrences)
Last logged: 10:55:19
Error requesting sensor data: Cannot connect to host 192.168.xx.xx:8443 ssl:default [None]
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (1 by maintainers)
Top Results From Across the Web
Hue unable to reach bridge · Issue #23796 · home-assistant ...
Weird the enough, my hue motion sensor works flawless every time. ... Unable to reach bridge 192.168.0.9 (Error requesting data from ...
Read more >ERROR: Unable to request rawdata at this time. The sensor ...
I am running a recent install of Security Onion with one Master and two sensors. Everything seems to be working great except for...
Read more >Anyone else having problems with 0.92 and Hue?
2019-05-30 16:47:24 ERROR (MainThread) ... X (Error requesting data from 10.0.0. ... Hue motion sensors + remotes: custom component.
Read more >EDR: What are the common sensor communication error ...
Answer ; 0x80190198, 408, HTTP, Request Timeout ; 0x8019019D, 413, HTTP, Payload Too Large - The request is larger than the server is...
Read more >Error while pushing sensor data with raspberry pi to xively ...
i try to read data with a raspberry pi from my ds18b20 temperature sensor and push them to xively. ... How can i...
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
So I powered off the Shield and by a restart it added the sensors. Restart HA with the shield made the sensors unavailable as expected. Copied the dev branche into the custom component and they went available again. Fun fact the shield is now also apperearing 😄
Just so i 100% sure i understand. There are no sensors for the rest of you Google devices, even though they are supported?
As there is many different devices out there, we don’t use a whitelist approach. If it generates a token in the right format it is expected to support it (This obliviously does not).