Domoticz

thebartzman wrote: ↑Saturday 23 May 2020 22:24 Hi i've been searching for a while, but can anybody explain what the nest features are in Domoticz? I have several Nest Protects in use and I'm curious what the Domoticz features are when Nest project is integrated.
Thanks

rolandbreedveld wrote: ↑Sunday 24 May 2020 11:20 hi
the usual stuff, temp, humidity, control of setpoint, see if its heating, set or view away and eco modes.
I use Domoticz also as an automatic alarm system, if no one is at home, alarm switches on, and also a trigger to set the Nest in eco mode, this will spare energy.
regards Roland

Slyguy wrote: ↑Friday 29 May 2020 22:41 Hi,

Thanks for bringing back Nest to Domoticz! I already gave up ever seeing back my nest protects in Domoticz.

But could someone help out this noob? I can manage the Domoticz webinterface, but when it comes to coding and dzVents, I'm lost. So now I'm stuck. I've read this topic, but I'm not able to figure it out.

I own a couple of Nest protects and not the thermostat.
I've managed to install the nest-api on my pi.
I also retrieved my google nest credentials and added them to nest.auth.php.
When I run php get_nest.php status of one of my protects is displayed.
But I don't know how to link this information to a domoticz item.

- I've created a Hardware dummy, but do I need to create a virtual sensor? And if so, what kind of sensor should this be. For now I'm mainly interested in the smoke and CO2 status.
- The IDX from the virtual sensor should be placed in the nest_devices.cfg, correct? And should the name of this virtual sensor correspond to the one in the nest_devices.cfg?
- And then somehow I should create a dzVent Device based on dzVents_script_nest_setpoint.txt? Or is this only meant for the active control of sensors and therefor not needed for my protects, since they're only generate output.

Thanks in advance!

rolandbreedveld wrote: ↑Sunday 31 May 2020 10:46 it's all described on https://github.com/rolandbreedveld/nest-api
follow it carefully.
suc6, Roland

Slyguy wrote: ↑Monday 01 June 2020 12:25

rolandbreedveld wrote: ↑Sunday 31 May 2020 10:46 it's all described on https://github.com/rolandbreedveld/nest-api
follow it carefully.
suc6, Roland

Hi Roland, thanks for the reply.

I've read your description on github. What I don't understand is how the gathered variables by nest_class.php of the nest protect, like "co_status", are linked to my virtual sensors in Domoticz.

For example: I created a virtual switch sensor named CO en added this to nest_devices.cfg with the corresponding IDX. But how is the co_status passed to this virtual sensor? Integrating my rooted Eneco Toon in Domoticz required me to add several "User variables" in Domoticz. Or am I now comparing appels met peren?

Sadly, as you may have noticed, my Domoticz skills and knowledge are quite basic.

meel4chris wrote: ↑Monday 15 June 2020 13:53 update: also with the latest beta (build 12164), the Nest thermostat isnt being update when I change the setpoint via my LUA script.
I'm very curious if somebody has the same experience.

meel4chris wrote: ↑Tuesday 16 June 2020 12:24 Hi,

I have now made a workaround and added the following to my LUA scripts to change the Nest:
os.execute('/usr/bin/php /home/pi/nest-api/nest_setpoint.php 16')

but still strange that the Nest is not updated together with the setpoint in domocticz if I use the following in my LUA script:
commandArray[#commandArray + 1]={["UpdateDevice"]='897|0|16'}

tjabas wrote: ↑Monday 29 June 2020 18:01 im about to order a nest hello door bell, would this be possible to se this device in domoticz with this account migration?