Nest Protect integration for Home Assistant. This will allow you to integrate your smoke, heat, co and occupancy status real-time in HA.

Overview

Detail page of a Nest Protect device

hacs_badge GitHub release HA integration usage

Nest Protect integration for Home Assistant

Custom component for Home Assistant to interact with Nest Protect devices via an undocumented and unofficial Nest API. Unfortunately, Google SDM doesn't support Nest Protect devices and thus the core Nest integration won't work for Nest Protect.

This integration will add the most important sensors of your Nest Protect device (CO, heat and smoke) and the occupancy if your device is wired (to main power). In addition, it will expose several diagnostic and configuration entities. All sensor values will be updated real-time.

Known limitations

  • Only Google Accounts are supported, there is no plan to support legacy Nest accounts
  • When Nest Protect (wired) occupancy is triggered, it will stay 'on' for 10 minutes. (API limitation)

Installation

You can install this integration via HACS or manually.

HACS

Search for the Nest Protect integration and choose install. Reboot Home Assistant and configure the Nest Protect integration via the integrations page or press the blue button below.

Open your Home Assistant instance and start setting up a new integration.

Manual

Copy the custom_components/nest_protect to your custom_components folder. Reboot Home Assistant and configure the Nest Protect integration via the integrations page or press the blue button below.

Open your Home Assistant instance and start setting up a new integration.

Advanced

Feel free to create an issue on GitHub if you find an issue or if you have a suggestion. It is always helpful to download the diagnostics information and to include debug logging.

Enable debug logging

The logger integration lets you define the level of logging activities in Home Assistant. Turning on debug mode will show more information about unsupported devices in your logbook.

logger:
  default: critical
  logs:
    custom_components.nest_protect: debug

Credits

Based on the research and implementation of homebridge-nest.

Comments
  • Support FieldTest Environment

    Support FieldTest Environment

    Description

    Nest uses a Field Test environment that is served by different endpoints.

    It would be fantastic if this integration would allow to select the field test environment in addition to the (default) prod environment.

    homebridge-nest is doing a great job managing the endpoints and authentication.

    Happy to help testing or provide more information if useful!

    Device (optional)

    No response

    Additional information

    No response

    enhancement p1 
    opened by SeraphimSerapis 16
  • Support Nest Thermostat temperature sensors

    Support Nest Thermostat temperature sensors

    Description

    The eventual goal is to see if this integration can expose the features that are currently missing from the Nest SDM API. One of these features is the temperature access:

    How can you help?

    1. Download https://github.com/iMicknl/ha-nest-protect/archive/refs/heads/enhancement/kryptonite_temperature_sensors.zip Extract this file and place custom_components/nest_protect in your custom_components folder.
    2. Restart Home Assistant
    3. (assuming you already have setup the integration, otherwise you need to do it now)
    4. Go to your integrations page (config/integrations) and click the 3 dots next to Nest Protect. Select 'download diagnostics'.
    5. Post your diagnostics here in a comment.
    6. You can check if there are temperature sensors added as well and or if you have errors in your log.

    Device (optional)

    No response

    Additional information

    No response

    enhancement 
    opened by iMicknl 16
  • Improve exception handling and reliability of real-time updates

    Improve exception handling and reliability of real-time updates

    The problem

    Since this integration is still work in progress, I didn't add good error handling / retry logic yet. This will need to be added to make sure the integration is reliable and will always receive state updates.

    What version of this integration (ha-nest-protect) has the issue?

    0.3.0

    What version of Home Assistant Core has the issue?

    2022.2.0

    Device / Model

    No response

    Diagnostics information

    No response

    Home Assistant log

    Logs
    2022-03-10 04:13:14 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
    Traceback (most recent call last):
    File "/config/custom_components/nest_protect/__init__.py", line 123, in _async_subscribe_for_data
    result = await entry_data.client.subscribe_for_data(
    File "/config/custom_components/nest_protect/pynest/client.py", line 222, in subscribe_for_data
    raise NotAuthenticatedException(await response.text())
    custom_components.nest_protect.pynest.exceptions.NotAuthenticatedException
    During handling of the above exception, another exception occurred:
    Traceback (most recent call last):
    File "/config/custom_components/nest_protect/__init__.py", line 170, in _async_subscribe_for_data
    await entry_data.client.authenticate(entry_data.client.auth.access_token)
    File "/config/custom_components/nest_protect/pynest/client.py", line 160, in authenticate
    nest_response = await response.json()
    File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1103, in json
    raise ContentTypeError(
    aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: ', url=URL('https://home.nest.com/session')
    

    Additional information

    No response

    bug 
    opened by iMicknl 12
  • Options is available as a standard property of SelectEntityDescription

    Options is available as a standard property of SelectEntityDescription

    The problem

    As of Home Assistant Core 2022.11, options is available as a standard property of SelectEntityDescription. This may cause issues in custom components if a custom options property was previously implemented.

    Please adjust the custom component by either dropping or renaming the custom options property.

    See https://github.com/home-assistant/core/pull/78882

    bug 
    opened by epenet 9
  • Occupancy ‘stuck’

    Occupancy ‘stuck’

    The problem

    I’m noticed the occupancy sensor got stuck at ‘on’ today until I rebooted. First time I noticed, and fixed on rebooting home assistant, but thought worth reporting…

    What version of this integration (ha-nest-protect) has the issue?

    0.2.0

    What version of Home Assistant Core has the issue?

    2022.3.3

    Device / Model

    Nest wired topaz 2.33 firmware 3.4.5

    Diagnostics information

    No response

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by Ibycus314 9
  • 2fa_state_changed error after enter refresh token

    2fa_state_changed error after enter refresh token

    Just after enter refresh token i got follow error in logs... On UI i just got "Unexpected error"

    Logger: custom_components.nest_protect
    Source: custom_components/nest_protect/pynest/client.py:139
    Integration: nest_protect (documentation)
    First occurred: 21:01:33 (1 occurrences)
    Last logged: 21:01:33
    
    
    '2fa_state_changed'
    Traceback (most recent call last):
      File "/config/custom_components/nest_protect/config_flow.py", line 40, in async_step_user
        refresh_token = await self.async_validate_input(user_input)
      File "/config/custom_components/nest_protect/config_flow.py", line 28, in async_validate_input
        await client.authenticate(
      File "/config/custom_components/nest_protect/pynest/client.py", line 139, in authenticate
        nest_response["_2fa_state_changed"] = nest_response.pop("2fa_state_changed")
    KeyError: '2fa_state_changed'
    
    bug 
    opened by marcswiss 8
  • Make replace by sensor a valid timestamp.

    Make replace by sensor a valid timestamp.

    Description

    The replace by sensors don't include a time which means HA doesn't see it as a valid timestamp.

    image

    This means we can't use the timestamp formatting options in the HA front end for entities. In a case like this a relative time display is more intuitive than just displaying the date.

    - entity: sensor.nest_protect_upstairs_replace_by
      format: relative
    

    image

    Device (optional)

    All

    Additional information

    I've solved the issue in the meantime with a template sensor, but it would be nice if it came right out of the box with a valid timestamp.

        - name: 'Nest Replace'
          unique_id: nest_replace
          icon: mdi:calendar-account-outline
          device_class: timestamp
          state: "{{ states('sensor.nest_protect_upstairs_replace_by')|as_datetime|as_local }}"
    

    image

    enhancement wontfix 
    opened by jazzyisj 7
  • CO Status shows off

    CO Status shows off

    The problem

    Hi there! Congratulations for this great job! Just testing out this integration which worked fine out of the box (copying nest_protect to custom_components folder and restarting ha). I found that CO status shows off in my device, is this correct? Since I cannot see this in nest application I am not sure if this is an expected behaviour, but I think the feedback will be welcomed, screenshot here:

    image

    If there is any test or contribution needed just ask, I will very pleased to help with this integration development.

    Regards

    What version of this integration (ha-nest-protect) has the issue?

    0.1.1

    What version of Home Assistant Core has the issue?

    core-2021.12.9

    Device / Model

    Topaz-2.7

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by bcantera 7
  • Change entities name

    Change entities name

    Description

    As in have my homeassistant in dutch i have the following problem. On my lovelace when i look on for example nestprotect smoke it states 'niet beschikbaar. Not availible. Is rather confucianisme. Is there a wat to adjust? Woud be a gratis improvement. Thans on advance Ton

    Device (optional)

    No response

    Additional information

    No response

    enhancement 
    opened by Vabis1010 6
  • not detected

    not detected

    The problem

    don't know if it schould be like this but my occupancy and smoke detection sensors gif state not detected. When i see the example pic in the github it schould give other states or am i wrong? Happy with the program because now i can integreate my nestprotects in the automations.

    Ton

    What version of this integration (ha-nest-protect) has the issue?

    0.1.1

    What version of Home Assistant Core has the issue?

    supervissor

    Device / Model

    nest protect battery

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by Vabis1010 6
  • Platform errors after HA 2022.11

    Platform errors after HA 2022.11

    The problem

    Logger: homeassistant.setup Source: setup.py:320 First occurred: 9:47:25 PM (1 occurrences) Last logged: 9:47:25 PM

    Unable to prepare setup for platform nest_protect.select: Platform not found (Exception importing custom_components.nest_protect.select).

    This error originated from a custom integration.

    Logger: homeassistant.loader Source: custom_components/nest_protect/select.py:23 Integration: Nest Protect (documentation, issues) First occurred: 9:47:25 PM (1 occurrences) Last logged: 9:47:25 PM

    Unexpected exception importing platform custom_components.nest_protect.select Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/loader.py", line 728, in get_platform cache[full_name] = self._import_platform(platform_name) File "/usr/src/homeassistant/homeassistant/loader.py", line 745, in _import_platform return importlib.import_module(f"{self.pkg_path}.{platform_name}") File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 1006, in _find_and_load_unlocked File "", line 688, in _load_unlocked File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/config/custom_components/nest_protect/select.py", line 23, in class NestProtectSelectDescription( File "/usr/local/lib/python3.10/dataclasses.py", line 1185, in dataclass return wrap(cls) File "/usr/local/lib/python3.10/dataclasses.py", line 1176, in wrap return _process_class(cls, init, repr, eq, order, unsafe_hash, File "/usr/local/lib/python3.10/dataclasses.py", line 1025, in _process_class _init_fn(all_init_fields, File "/usr/local/lib/python3.10/dataclasses.py", line 546, in _init_fn raise TypeError(f'non-default argument {f.name!r} ' TypeError: non-default argument 'key' follows default argument

    What version of this integration (ha-nest-protect) has the issue?

    0.3.8

    What version of Home Assistant Core has the issue?

    core-2022.11

    Device / Model

    No response

    Diagnostics information

    Screenshot_20221102-215610

    Screenshot_20221102-215616

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by tobycth3 5
  • Occupancy not updated / triggered

    Occupancy not updated / triggered

    The problem

    Occupancy is not updated / triggered. On the nest I see the white light coming on, so all is working fine. The occupancy value seems to be read correctly from the (powered) Nests when HA is started, but does not seem to change after that anymore. Sometimes the values are updated assuming this happens when other sensor values get updated, I hoped to use the occupancy as a direct trigger but seems not to be working. Nothing shows up in the logs, not even with debugging enabled (also not after a restart of HA).

    What version of this integration (ha-nest-protect) has the issue?

    0.3.10 (in Hacs) 0.3.8 (in logs)

    What version of Home Assistant Core has the issue?

    2022.12.7

    Device / Model

    Nest Protect (3 on power, 1 on battery)

    Diagnostics information

    No response

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by GentleGiantSoftware 0
  • Unknown Exception popping up every 5 seconds

    Unknown Exception popping up every 5 seconds

    The problem

    I have got an error popping up on the log every 5 seconds. The Nest Protect Devices and entities seem working fine though.

    What version of this integration (ha-nest-protect) has the issue?

    0.3.10

    What version of Home Assistant Core has the issue?

    core-2022.11.5

    Device / Model

    Nest Protect (Topaz-2.9)

    Diagnostics information

    config_entry-nest_protect-d9d72164fb1de9ad1884f574ae28ec3c.json.txt

    Home Assistant log

    Logs ```2022-12-01 05:28:37.479 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:33:37.682 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:38:37.819 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:43:37.958 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' ```

    Additional information

    No response

    bug 
    opened by janusn 8
  • Failed to connect error while using cookies

    Failed to connect error while using cookies

    The problem

    Can you guys help me with this error? I logged in on home.nest.com and followed the guide after I got the other issue on logging in.

    Logger: custom_components.nest_protect
    Source: custom_components/nest_protect/pynest/client.py:219
    Integration: Nest Protect ([documentation](https://github.com/imicknl/ha-nest-protect), [issues](https://github.com/imicknl/ha-nest-protect/issues))
    First occurred: 8:14:31 PM (3 occurrences)
    Last logged: 8:16:50 PM
    
    400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"27334ad0-f0f8-4467-9c56-0e4bd11aa022"}. Please create an issue on GitHub.
    400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"fc7af587-a67b-4d19-ba4c-7b9c2e71975b"}. Please create an issue on GitHub.
    400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"fadec021-38cf-432e-ad5d-da81ce319b7c"}. Please create an issue on GitHub.
    Traceback (most recent call last):
      File "/config/custom_components/nest_protect/pynest/client.py", line 215, in authenticate
        self.nest_session = NestResponse(**nest_response)
    TypeError: NestResponse.__init__() got an unexpected keyword argument 'error_description'
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/config/custom_components/nest_protect/config_flow.py", line 104, in async_step_account_link
        [issue_token, cookies] = await self.async_validate_input(user_input)
      File "/config/custom_components/nest_protect/config_flow.py", line 62, in async_validate_input
        await client.authenticate(
      File "/config/custom_components/nest_protect/pynest/client.py", line 219, in authenticate
        raise PynestException(
    custom_components.nest_protect.pynest.exceptions.PynestException: 400 error while authenticating - {"error":"invalid_request","error_description":"missing user credentials","instance_id":"27334ad0-f0f8-4467-9c56-0e4bd11aa022"}. Please create an issue on GitHub.`
    

    What version of this integration (ha-nest-protect) has the issue?

    0.3.10

    What version of Home Assistant Core has the issue?

    2022.11.3

    Device / Model

    Raspberry Pi

    Diagnostics information

    No response

    Home Assistant log

    Logs ``` Copy/paste any log here, between the starting and ending backticks (`) ```

    Additional information

    No response

    bug 
    opened by danieldevos90 7
  • Error 400: invalid_request when authenticating with Google

    Error 400: invalid_request when authenticating with Google

    The problem

    I installed the ha-nest-protect integration through HACS and restarted. I'm trying to add the integration now and when I click on the "authorize your account" link I get this error:

    Screen Shot 2022-10-07 at 12 20 03 PM

    Clicking into the error details shows the following:

    Error 400: invalid_request The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow Migration Guide linked in the developer docs below to migrate your app to an alternative method. Request details: access_type=offline response_type=code redirect_uri=urn:ietf:wg:oauth:2.0:oob client_id= scope=openid https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/nest-account

    I've tried it on two separate browsers to the same result.

    Edited to add: I found this page: https://developers.google.com/identity/protocols/oauth2/resources/oob-migration

    I was successfully able to get a token by appending a ack_oob_shutdown=2022-10-03 parameter to the query string on the auth url.

    What version of this integration (ha-nest-protect) has the issue?

    0.3.8

    What version of Home Assistant Core has the issue?

    2022.10.0

    Device / Model

    Nest Protect (Battery)

    Diagnostics information

    No response

    Home Assistant log

    No response

    Additional information

    No response

    bug 
    opened by WKHarmon 58
  • The smoke alarm comes on but there is no trace in the home assistant

    The smoke alarm comes on but there is no trace in the home assistant

    The problem

    I received the alarm notification of a Nest Protect that has detected smoke (push notification from Nest app) but there is no trace of the alarm in the logs in the home assistant. Screenshot from Nest app: https://prnt.sc/SDcufmNljrNh Screenshot from Home Assistant: https://prnt.sc/uDqxosQIIoPr

    What version of this integration (ha-nest-protect) has the issue?

    0.3.8

    What version of Home Assistant Core has the issue?

    2022.9.7

    Device / Model

    Nest protect Topaz-2.33 (with cable power supply)

    Diagnostics information

    No response

    Home Assistant log

    Questo errore ha avuto origine da un'integrazione personalizzata.

    Logger: homeassistant Source: custom_components/nest_protect/init.py:202 Integration: Nest Protect (documentation, issues) First occurred: 28 settembre 2022 11:29:47 (1 occurrences) Last logged: 28 settembre 2022 11:29:47

    Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1154, in _create_direct_connection hosts = await asyncio.shield(host_resolved) File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 880, in _resolve_host addrs = await self._resolver.resolve(host, port, family=self._family) File "/usr/local/lib/python3.10/site-packages/aiohttp/resolver.py", line 33, in resolve infos = await self._loop.getaddrinfo( File "/usr/local/lib/python3.10/asyncio/base_events.py", line 860, in getaddrinfo return await self.run_in_executor( File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.10/socket.py", line 955, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Try again

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last): File "/config/custom_components/nest_protect/init.py", line 202, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 535, in _request conn = await self._connector.connect( File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 542, in connect proto = await self._create_connection(req, traces, timeout) File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 907, in _create_connection _, proto = await self._create_direct_connection(req, traces, timeout) File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1166, in _create_direct_connection raise ClientConnectorError(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host home.nest.com:443 ssl:default [Try again]

    Additional information

    No response

    bug 
    opened by galamarco 2
Releases(v0.3.10)
  • v0.3.10(Nov 3, 2022)

    What's changed

    This update will fix issues with Home Assistant 2022.11 version, due to a breaking change in core.

    Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this.

    🐛 Bug Fixes

    • Need for minor version number (add .0) (#113) @markvader

    Contributors to this release

    @markvader

    Source code(tar.gz)
    Source code(zip)
  • v0.3.9(Oct 31, 2022)

    What's changed

    This update will fix issues with the (soon to be released) Home Assistant 2022.11 version, due to a breaking change in core.

    Please note that since Nest has changed authentication, multiple issues have been reported which you can read more about here. This update does not fix this.

    Features

    • Add German Translation (#97) @JbbDE

    🐛 Bug Fixes

    • Remove options as property of SelectEntityDescription (#109) @iMicknl

    Contributors to this release

    @JbbDE and @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.8(Jun 15, 2022)

    What's changed

    ✨ Enhancement

    • Bump HA version to 2022.6 (#92) @iMicknl
    • Improve error logging during login (#88) @iMicknl

    📘 Documentation

    • Update HACS URL (#89) @wrt54g

    Contributors to this release

    @iMicknl and @wrt54g

    Source code(tar.gz)
    Source code(zip)
  • v0.3.7(May 6, 2022)

    What's changed

    ✨ Enhancement

    • Catch more Nest back-end errors during authentication (#82) @iMicknl
    • Handle Nest 502 Bad Gateway errors and add retry logic (#81) @iMicknl

    🐛 Bug Fixes

    • Enable real-time updates for temperature sensors (#79) @elmigbot

    Contributors to this release

    @elmigbot and @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.6(May 3, 2022)

  • v0.3.5(Apr 29, 2022)

    What's changed

    ✨ Enhancement

    • Improve reliability by retrying after 5 minutes on unknown exceptions (#75) @iMicknl

    🐛 Bug Fixes

    • Retry on ClientConnectorError (#74) @iMicknl
    • Don't fail when Nest temperature sensor doesn't have serial and model information (#68) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.4(Mar 22, 2022)

    What's changed

    This release won't add any improvements for Nest Protect devices, but will include support for external Nest Temperature Sensors that are often used with the Nest Thermostat. Unfortunately, this is not exposed via the official SDM API, hence it is added to this integration.

    ✨ Enhancement

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.3(Mar 14, 2022)

    What's changed

    ⚠️ Breaking changes

    • Disable heat test binary sensor (#51) @iMicknl

    ✨ Enhancement

    • Add more diagnostics redactions (#52) @iMicknl

    🐛 Bug Fixes

    • Don't add occupancy sensor for battery devices (#55) @iMicknl
    • Handle gateway timeout exception (#54) @iMicknl
    • Disable heat test binary sensor (#51) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.2(Mar 13, 2022)

    What's changed

    ✨ Enhancement

    • Add line power diagnostic sensor (#42) @iMicknl

    🐛 Bug Fixes

    • Make device naming more consistent when label is used (#47) @iMicknl
    • Move to EntityCategory enums (#46) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.1(Mar 12, 2022)

    What's changed

    ✨ Enhancement

    • Catch gateway time-out (#41) @iMicknl
    • Add 'reauth' to Config Flow (#37) @iMicknl
    • Improve error handling in Config Flow (#36) @iMicknl
    • Add all available test statuses as diagnostic sensors (#35) @iMicknl

    🐛 Bug Fixes

    • Redact address line in diagnostics (#40) @iMicknl
    • Improve authentication refresh logic (#39) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.3.0(Mar 7, 2022)

    What's changed

    This release makes the configuration entities more usable, since you can now change them via Home Assistant! The sensor/binary sensor entities are removed in favor of new select and switch entities. You will need to manually remove the old entities or remove your config entry and reconfigure the integration.

    Until we reach 1.0.0, more breaking changes can happen, since this integration is still in early development.

    ⚠️ Breaking changes

    • Make it possible to change configurable settings via switch entities (#31) @iMicknl
    • Add configurable option to select brightness (#28) @iMicknl

    ✨ Enhancement

    • Make it possible to change configurable settings via switch entities (#31) @iMicknl
    • Add diagnostics (#29) @iMicknl
    • Add configurable option to select brightness (#28) @iMicknl
    • Add Dutch translations (#30) @iMicknl
    • Add Brazilian Portuguese Translation (#26) @LeandroIssa

    Contributors to this release

    @LeandroIssa and @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.2.0(Mar 4, 2022)

    What's changed

    A long-awaited change, live updates of your device states. Please note that this hasn't been tested thoroughly, so please report an issue if it is not working as expected.

    ✨ Enhancement

    • Update devcontainer (#24) @iMicknl
    • Add real-time updates (#10) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.1.2(Feb 19, 2022)

    What's changed

    ✨ Enhancement

    • Update manifest (#21) @iMicknl
    • Update CO device class (#20) @iMicknl
    • Add icon to brightness sensor (#19) @iMicknl
    • Fix brightness sensor and improve typing (#15) @iMicknl
    • Add workflow for running tests on PR (#13) @allenporter
    • Remove DataUpdateCoordinator (in preparation for long polling task) (#14) @iMicknl

    Tests

    • Add test coverage for pynest client library (#17) @allenporter
    • Add test timeout of 10 seconds (#18) @allenporter
    • Add a basic integration test skeleton. (#12) @allenporter

    Contributors to this release

    @allenporter and @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.1.1(Jan 15, 2022)

    What's changed

    ✨ Enhancement

    • Pull bucket data from coordinator (#2) @iMicknl

    🐛 Bug Fixes

    • Handle result when 2factor is not enabled (#3) @iMicknl

    Contributors to this release

    @iMicknl

    Source code(tar.gz)
    Source code(zip)
  • v0.1.0(Jan 15, 2022)

Owner
Mick Vleeshouwer
Cloud Solution Architect @microsoft | Software Engineer
Mick Vleeshouwer
Source code for our EMNLP'21 paper 《Raise a Child in Large Language Model: Towards Effective and Generalizable Fine-tuning》

Child-Tuning Source code for EMNLP 2021 Long paper: Raise a Child in Large Language Model: Towards Effective and Generalizable Fine-tuning. 1. Environ

46 Dec 12, 2022
A PyTorch Implementation of "SINE: Scalable Incomplete Network Embedding" (ICDM 2018).

Scalable Incomplete Network Embedding ⠀⠀ A PyTorch implementation of Scalable Incomplete Network Embedding (ICDM 2018). Abstract Attributed network em

Benedek Rozemberczki 69 Sep 22, 2022
A new framework, collaborative cascade prediction based on graph neural networks (CCasGNN) to jointly utilize the structural characteristics, sequence features, and user profiles.

CCasGNN A new framework, collaborative cascade prediction based on graph neural networks (CCasGNN) to jointly utilize the structural characteristics,

5 Apr 29, 2022
We have made you a wrapper you can't refuse

We have made you a wrapper you can't refuse We have a vibrant community of developers helping each other in our Telegram group. Join us! Stay tuned fo

20.6k Jan 09, 2023
Official code for Next Check-ins Prediction via History and Friendship on Location-Based Social Networks (MDM 2018)

MUC Next Check-ins Prediction via History and Friendship on Location-Based Social Networks (MDM 2018) Performance Details for Accuracy: | Dataset

Yijun Su 3 Oct 09, 2022
Privacy-Preserving Machine Learning (PPML) Tutorial Presented at PyConDE 2022

PPML: Machine Learning on Data you cannot see Repository for the tutorial on Privacy-Preserving Machine Learning (PPML) presented at PyConDE 2022 Abst

Valerio Maggio 10 Aug 16, 2022
Diffusion Probabilistic Models for 3D Point Cloud Generation (CVPR 2021)

Diffusion Probabilistic Models for 3D Point Cloud Generation [Paper] [Code] The official code repository for our CVPR 2021 paper "Diffusion Probabilis

Shitong Luo 323 Jan 05, 2023
Codecov coverage standard for Python

Python-Standard Last Updated: 01/07/22 00:09:25 What is this? This is a Python application, with basic unit tests, for which coverage is uploaded to C

Codecov 10 Nov 04, 2022
Gated-Shape CNN for Semantic Segmentation (ICCV 2019)

GSCNN This is the official code for: Gated-SCNN: Gated Shape CNNs for Semantic Segmentation Towaki Takikawa, David Acuna, Varun Jampani, Sanja Fidler

859 Dec 26, 2022
Step by Step on how to create an vision recognition model using LOBE.ai, export the model and run the model in an Azure Function

Step by Step on how to create an vision recognition model using LOBE.ai, export the model and run the model in an Azure Function

El Bruno 3 Mar 30, 2022
Whisper is a file-based time-series database format for Graphite.

Whisper Overview Whisper is one of three components within the Graphite project: Graphite-Web, a Django-based web application that renders graphs and

Graphite Project 1.2k Dec 25, 2022
Optimal space decomposition based-product quantization for approximate nearest neighbor search

Optimal space decomposition based-product quantization for approximate nearest neighbor search Abstract Product quantization(PQ) is an effective neare

Mylove 1 Nov 19, 2021
(AAAI2022) Style Mixing and Patchwise Prototypical Matching for One-Shot Unsupervised Domain Adaptive Semantic Segmentation

SM-PPM This is a Pytorch implementation of our paper "Style Mixing and Patchwise Prototypical Matching for One-Shot Unsupervised Domain Adaptive Seman

W-zx-Y 10 Dec 07, 2022
Official Codes for Graph Modularity:Towards Understanding the Cross-Layer Transition of Feature Representations in Deep Neural Networks.

Dynamic-Graphs-Construction Official Codes for Graph Modularity:Towards Understanding the Cross-Layer Transition of Feature Representations in Deep Ne

11 Dec 14, 2022
This repo is about to create the Streamlit application for given ML model.

HR-Attritiion-using-Streamlit This repo is about to create the Streamlit application for given ML model. Problem Statement: Managing peoples at workpl

Pavan Giri 0 Dec 10, 2021
Monitora la qualità della ricezione dei segnali radio nelle province siciliane.

FMap-server Monitora la qualità della ricezione dei segnali radio nelle province siciliane. Conversion data Frequency - StationName maps are stored in

Triglie 5 May 24, 2021
The deployment framework aims to provide a simple, lightweight, fast integrated, pipelined deployment framework that ensures reliability, high concurrency and scalability of services.

savior是一个能够进行快速集成算法模块并支持高性能部署的轻量开发框架。能够帮助将团队进行快速想法验证(PoC),避免重复的去github上找模型然后复现模型;能够帮助团队将功能进行流程拆解,很方便的提高分布式执行效率;能够有效减少代码冗余,减少不必要负担。

Tao Luo 125 Dec 22, 2022
Autonomous Ground Vehicle Navigation and Control Simulation Examples in Python

Autonomous Ground Vehicle Navigation and Control Simulation Examples in Python THIS PROJECT IS CURRENTLY A WORK IN PROGRESS AND THUS THIS REPOSITORY I

Joshua Marshall 14 Dec 31, 2022
[CVPR 2021] Few-shot 3D Point Cloud Semantic Segmentation

Few-shot 3D Point Cloud Semantic Segmentation Created by Na Zhao from National University of Singapore Introduction This repository contains the PyTor

117 Dec 27, 2022
Personalized Transfer of User Preferences for Cross-domain Recommendation (PTUPCDR)

This is the official implementation of our paper Personalized Transfer of User Preferences for Cross-domain Recommendation (PTUPCDR), which has been accepted by WSDM2022.

Yongchun Zhu 81 Dec 29, 2022