Skip to content
This repository has been archived by the owner on Jun 23, 2022. It is now read-only.

Thermostat #1

Closed
luxus opened this issue Mar 11, 2016 · 6 comments
Closed

Thermostat #1

luxus opened this issue Mar 11, 2016 · 6 comments

Comments

@luxus
Copy link

luxus commented Mar 11, 2016

thats the json of one my thermostats:
thermostat.badezimmer_mode_9
{
"max_temp": 35,
"fan": "off",
"battery_level": 45,
"node_id": 9,
"min_temp": 7,
"current_temperature": 25,
"target_temp_low": 21,
"temperature": 21,
"unit_of_measurement": "°C",
"current_operation": "Comfort",
"target_temp_high": 21,
"friendly_name": "Bad Thermostat"
}
i would love to have the characteristics in bold avail. in homebridge.
i had them before with homebridge-zway.. but now i use openzwave to get it working with home-assistant.
battery_level and current_operationsare optional for me, because i just use temperature to set the target temperature and current_temperature to know the current temperature in the room

@maddox
Copy link
Collaborator

maddox commented Mar 14, 2016

🆒

I can attempt to do a quick first pass in making this work, but not actually having a thermostat is definitely going to make doing this complicated.

@luxus
Copy link
Author

luxus commented Mar 14, 2016

i would try my best to help you..
as far i remember there is a demo thermostat ? https://github.com/balloob/home-assistant/blob/dev/homeassistant/components/thermostat/demo.py

@maddox
Copy link
Collaborator

maddox commented Mar 14, 2016

I can spin up a branch, but you're going to have to know how to use checked out versions of homebridge plugins to test it. I can't publish it until it actually works. And I certainly can't publish it over and over to see if it works.

Someone could always just send me an Ecobee too, heh.

@luxus
Copy link
Author

luxus commented Mar 14, 2016

npm install <githubname>/<githubrepo>[#<commit-ish>] sounds not too complicated.

@maddox
Copy link
Collaborator

maddox commented Mar 15, 2016

So, after taking a look at this, I've decided not to move forward with it. The primary reason is simple: I don't have a smart thermostat.

While I'd love for this plugin to support it, I just don't have time to devote to something that I can't actively test or get anything out of. Open source can be very self serving and that's definitely the case for this plugin. My apologies for things being like this, but I just don't have the time available to write something in the blind and that I'm not going to get anything out of.

That being said, I absolutely welcome any contributions for this feature, thats actually the real beauty of open source :)

So, I'm going to just close this for now.

@maddox maddox closed this as completed Mar 15, 2016
@luxus
Copy link
Author

luxus commented Nov 13, 2016

maybe now some more peoples are working on this.. we can reopen it @maddox ? perhaps someone else is willing to add climate to this plugin?

robbiet480 pushed a commit that referenced this issue Jul 19, 2017
* Update README.md

Add 'homebridge_gas_type" description.

* Update binary_sensor.js

Add compatibility for 'gas' type of 'device_class'

* Specify that 'co' is default for gas binary sensor

* Clean up formatting before merging

* Minor spelling correction

* Delete README.md

* Revert "Delete README.md"

This reverts commit 6bffc4e.

* Update README.md

* Add alarm_control_panel.js

* Update to allow alarm_control_panel

* Temporary workaround for "NIGHT_ARM"

Due to Home Assistant limitations, arming "Night" is not currently possible (temporarily redirected to "Home").

* Update README.md

* Clean up #1

* Clean up #2

* Clean up #3
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants