2.0 protects do not seem to have co_previous_peak anymore
wired_or_battery, born_on_date, ntp_green_led_brightness, and color may already exist on the version 1 Nest, but since I don't have a 1 anymore I can't test. I made it check to make sure these exist just in case. If they do exist on the Nest 1 the check for isset can be removed.
speaker,buzzer tests were added tests for the nest 2 - currently it will put out 'null' just in case someone is using this and using lazy checking I didn't want to trigger a false positive by "0 == false" being true.
home_alarm_link,wired_led_enable I think are new features, but to stick with current conventions using empty and putting 0.
2.0 protects do not seem to have co_previous_peak anymore
wired_or_battery, born_on_date, ntp_green_led_brightness, and color may already exist on the version 1 Nest, but since I don't have a 1 anymore I can't test. I made it check to make sure these exist just in case. If they do exist on the Nest 1 the check for isset can be removed.
speaker,buzzer tests were added tests for the nest 2 - currently it will put out 'null' just in case someone is using this and using lazy checking I didn't want to trigger a false positive by "0 == false" being true.
home_alarm_link,wired_led_enable I think are new features, but to stick with current conventions using empty and putting 0.