Username and password auth is no longer working.
Neothermic has a fork with this corrected that can be found here:
It looks like the tokens this use expire after 1 month, though, so you’ll have to get a new one after that point.
Username and password auth is no longer working.
Neothermic has a fork with this corrected that can be found here:
It looks like the tokens this use expire after 1 month, though, so you’ll have to get a new one after that point.
Can someone post a sample of how exactly the yaml file should be setup? I get an error to check my config each time I restart HA. This is my first time setting up badnest. Thanks
im not getting any errors but nothing is showing up. im using google auth anyone see that,not sure what to do
Any chance you could share an example?
Still pulling my hair over why the badnest doesn’t want to work on my system. I recapitulate: badnest is properly installed with HACS (everything is where it should be under /custom_components. I have switched to google log-in and have extracted issue_token and cookie as per instructions (using incognito on google chrome). It clearly tries to setup the badnest but fails and hangs forever and says in the log that badnest is taking more than 10 secs to setup. The home assistant homepage doesn’t even show up.
I have tried to isolate the problem by , for example, removing the cookie line altogether. Of course it won’t set up the badnest component but at least it will allow the HA to start and just identify an error in badnest. Last night I use the " logger:" option in my configuration.yaml file to have more verbose logging details. With that I can see an error that says " Failed to update, trying to log in again". Now I looked in the api.py python file and the only place this line occurs is just after a bunch of camera setup
sensor_data["rq_battery_vbridge_volt"]
self.device_data[camera]['location'] = \
sensor_data["location"]
self.device_data[camera]['data_tier'] = \
sensor_data["properties"]["streaming.data-usage-tier"]
except requests.exceptions.RequestException as e:
_LOGGER.error(e)
_LOGGER.error('Failed to update, trying again')
self.update()
except KeyError:
_LOGGER.debug('Failed to update, trying to log in again')
self.login()
self.update()
Now I don’t even have a nest camera (although I do have a foscam that’s working properly). SO I tried removing anything to do with a camera. No change.
Any brilliant suggestions for me to try??
Many thanks again, Yves
Sure…
sensor:
- platform: badnest
- platform: template
sensors:
hallway_thermometer:
friendly_name: "Hallway Temperature"
unit_of_measurement: 'C'
value_template: "{{ state_attr('climate.**yourdevicehere**', 'current_temperature') | round(0) }}"
device_class: "temperature"
I have had issues also with the badnest original version (Camera didnt show and some others issues) till I used the forked version from https://github.com/vinodmishra/badnest Now I would like to know how I can make the camera images more “live” like the camera is in the NEST app.
Were all the issues related to the cameras or did you have thermostat issues?
Yea, the thermostat and remote sensors were detected and worked right away. The camera never showed till I used the forked version.
Did you have to redo the cookies etc? Or just using the forked and restarting worked?
Nope, just uninstalled the original badnest and used the forked version. The added lines to the .yaml file were still there and worked with the forked version.
Nice. I will give this a shot. Love the name.
Still trying to figure this one out after two weeks of failure! TO further investigate, I have installed a new instance of HA on a Mac (the other is running on a raspberrypi) and found that it does not load badnest properly either (presumably the token/cookie issue even though I follow the instructions to the letter). One other possibility is that I have an old 2nd generation Nest. Has anyone have it functioning on a 2ng gen Nest??
Thanks again, Yves
2nd gen here, no issues at all. Been using Badnest since it was named shitty nest, I started out with a nest.com account worked great till Google changed the login process, I then switched to a Google account with 2fa and have not had any issues since.
Has anyone got this working with multiple Nest thermostats?
Home Assistant Newbie here,
Glad I accidentally bumped into this page. Thought I’d never be able to integrate Nest with Home Assistant.
Directions were straight forward. I was able to do this via “Not using google Auth” earlier today. I currently have 2 Nest Devices (Both 3rd Generation Nest Learning). Looks like the token will eventually expire in 5 months? Guess I will have to do the process in a few month—not sure.
Why do you keep asking? Somebody has already answered you he has three thermostats up an running no issues. I have two 3rd gens and they are working as well. (I have to admit last few weeks i have seen some timeout errors in loggs )
Yesterday’s update broke camera. Unavailable error in Lovelace.
@yvesprairie - I am having the same issue. I wonder if deleting our Nest account and starting over might fix this?
Good question, I don’t know. It may be worth a try. In a way, that’s why I created a second HA instance from scratch on a different computer to make sure it was not an issue about the HA. Since I got exactly the same result, it does point for the problem to be elsewhere, unless of course we are doing something wrong in the configuration.yaml file (I have read and re-read the instructions about 10 times!). I’m busy for the next couple of evenings but if you try it, please share the outcome. Thanks, Yves