tonesto7/nest-manager

Power type shows as Null for Nest protect

Open

#483 opened on Aug 26, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Groovy (392 stars) (2,134 forks)batch import
good first issue

Description

Verify the following before opening an issue:

  • That OAuth is Enabled for the SmartApp under the IDE.
  • The SmartApp and Device are using the latest version.
  • You have reviewed the Readme for potential fixes.
  • That the Device Types have been Published for You.

About Your Setup:

  • How many Thermostats?:
  • How many Protects?
  • Are you Using the Nest Presence Device?
  • iOS or Android?:
  • Mobile App Version:

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Please include a copy of your log under the IDE if possible>>>

Contributor guide

Tech stack
groovy
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Knowledge of Nest APISmartThings Groovy development environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the Nest Protect device handler (likely 'nest protect.groovy') to understand how power type is parsed from the Nest API response. Check if the API returns a null or missing field for certain devices. Review any existing comments or closed issues for solutions. Since the issue is old and no progress, consider testing with current API to see if the bug persists.