kar1024 Posted February 23, 2018 Posted February 23, 2018 Two homes with EcoBee thermostats. All thermostats are under the same account, but in separate groups. NodeLink-EcoBee integration allows only one instance of Nodelink to be running at the same time. Any work around for this limitation? Obvious solution is ask guys from Automation Shack to register multiple applications with EcoBee (Nodelink, Nodelink2, etc) a add a parameter to config. Am I the only one with this kind of problem? P.S. @io_guy Thanks for great product! Cannot live without it.
io_guy Posted February 23, 2018 Posted February 23, 2018 Just add a second ecobee device to NodeLink.
kar1024 Posted February 23, 2018 Author Posted February 23, 2018 I have 7 devices total. 6 at one home and 1 at the other. Only one instance of NodeLink is able to stay connected to EcoBee at the same time. Even tried manually copying keys - still only one connection is allowed.
io_guy Posted February 23, 2018 Posted February 23, 2018 I mean keep adding more ecobee devices (one for each stat) in the same instance of NodeLink. This design is intentional because the ecobee API is very limiting in polling allowance per account. With 7 stats installed on the same NodeLink they share a single poll to the API.
kar1024 Posted February 23, 2018 Author Posted February 23, 2018 1 minute ago, io_guy said: I mean keep adding more ecobee devices (one for each stat) in the same instance of NodeLink. This design is intention because the ecobee API is very limiting in polling allowance per account. Sorry, was not clear. I have 2 homes with ISY in each one. Have to run two instances of NodeLink. One per ISY.
io_guy Posted February 23, 2018 Posted February 23, 2018 Ahh gotcha. Yea I think you're the first with that config. Definitely no clean solution. Would involve creating a NodeLink2 as you said in the devel portal and then rewriting the code to allow selection of the secondary API key. Might be cleaner to connect two versions of NodeLink and one pump the ecobee data to the second.
kar1024 Posted February 23, 2018 Author Posted February 23, 2018 I don't mind tinkering with two instances of NodeLink. How do I go about configuring one to be "slave" of the other?
kar1024 Posted February 23, 2018 Author Posted February 23, 2018 @io_guy I have a developer account with EcoBee and have a few apps under my name. What if you add parameter for custom developer API key to the config?
io_guy Posted February 23, 2018 Posted February 23, 2018 Yea that's a lot easier than the code changes I'd need to make for data sharing between two instances.
io_guy Posted February 28, 2018 Posted February 28, 2018 0.9.10 should have what you want. You'll need to edit config.xml and add a "customkey" variable under the ecobee section. I didn't add it to the GUI cause it would just confuse everyone else.
kar1024 Posted March 6, 2018 Author Posted March 6, 2018 @io_guy Thank you very much for adding this feature. Works flawlessly. Your update allowed me to connect all EcoBee sensors to both ISYs. With location data in both ISYs already I finally got Leave/Arrive programs to trigger correctly in both houses! Perfect for preheating weekend country retreat just in time for arrival. The dream of never pressing any buttons to control home automation is one step closer to becoming reality.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.