I see that when I am setting the mode of my Nest thermostat, there is option for "eco", which is perfect. But, later when I am checking the current mode of the thermostat in my If condition, there is no "eco" mode in the list. Is this intended, or a bug?
Shown below is where i can correctly see "eco" mode during setting:
Shown below, is where during mode condition checking, "eco" is not available.
Hi, please talk to the developer of your rule engine. I don't have any control over what appears in the interface of the rule engine.
Regards
Hi,
I do not think this is a "rule" issue. The screenshot I displayed, are rule configuration input screens. The screenshot shows the available tstat mode values...not the actual rule logic. The values shown are what Hubitat is giving me from the tstat device. So my guess is that the device driver is exposing those in that way.
Hi, that's what I'm saying. The list of values in the rule engine interface should come from the supportedThermostatModes attribute in the driver which contains the eco mode.
But, the rule engine is using its own list of values which doesn't contain the eco mode. It's an issue to report to the rule engine's developer.
Regards
Ah, i see your point now. I thought by rule developer you were referring to me, who is creating the rule. I understand that this might be an issue which Hubitat staff might need to look at. Thanks.
Anybody knows, if we can tag hubitat rule engine staff team to this post for their review of the issue?
When you get a moment, please have a look at [Bug Report 2.2.8.156] Rule Machine is not picking up all Thermostat modes - #21 by bravenel
It turns out that there is a a bit of a fix needed from both Hubitat and the Next Manager app to better support "eco" mode. The good news is that for now, there seems to be a possible workaround (still need to test that) and in an upcoming Hubitat update, hopefully there will also be a fix for Thermostat. But, at the same time a fix is also suggested for this app by Hubitat in that thread. Please comment directly on that thread if you have any comments/thoughts.
Hi @saurabh9, RM will soon support the attributes "supportedThermostatModes" and "supportedThermostatFanModes" which is the right way to leverage the information exposed by the driver.
As you may know, some Nest thermostats support the cool mode, others not. Some Nest thermostats support some fan modes; others don't support any fan modes as there is no fan wired to the HVAC.
The only way to correctly expose the right thermostat modes and related fan modes is through the "supported*" attributes, which were designed for that purpose.
My understanding is that there is nothing more to "fix" on my side of things.
Regards.
Any idea how to correct an "Illegal character in query at index 84:" error on the issue token url?
Edit - what in chrome as %20 converted to "spaces" which was tripping the error
Thnx. Works indeed but either the toDo list or the app should compensate for the spaces and paste in %20's.
Hi, this is a new google chrome issue, but it's now corrected with the new minor release.
MyNextManager's version 3.7.1 automatically converts all spaces to %20 in the URL string.
If needed, you can download it using the same sellfy download link.
Regards.
So this only polls? Meaning if a nest protect is in an alarm or warning state, it won't trigger anything until the next polling is completed?
Yes, it can poll every minute if needed.
Regards
So I have this running on my Hubitat well. My question is for the Protects, will this integration polling work if the power or Internet goes out? Does the software poll directly to the Google Protects on WiFi? Also any future release coming for making the devices a child off a master device driver?
Hi, MyNext Manager uses a C2C connection to poll the devices.. It's not a local API, but a cloud one exposed by Nest.
Like any other C2C connection, if your internet is down, the devices won't be updated. If the outage lasts more than an hour (according to its own internal cycle, the interval may be less), you may have to re-authenticate as the code may not be able to automatically refresh the tokens.
And, there is no plan to create child devices out of a master parent device, I don't see any benefits of doing so. As the code is based on a C2C connection, all Nest devices are using the same parent smartapp (Service Manager) which optimizes the caching and polling of all child devices under it. You have access to some caching variables in MyNextManager from the first page.
Regards.
Is there a release notes section or list that I can't seem to locate? I see a reference to 3.7.1 but only 3.7 within the original post. Looks like I am running 3.7 too. Just curious what else was resolved in 3.7.1 and if I should upgrade or save my 4 minor update options for 3.8, or 3.7.2+.
Hi,
That's the only difference with the 3.7 version. If you have already authenticated your Nest device(s), then it's not worthwhile to update.
P.S. If there is any major update, it will be posted here in the forum under the first post of this thread, see latest release section above
Regards.
@yracine66 Not sure if this is the right place to put this, or send it to to your e-mail, in case the e-mail doesn't work I have put it here as well:
I placed an order for MyNextDevices from the following your hubitat store.
I have tried downloading and installing the App and Drivers in Hubitat, but none of them save, they all have errors, e.g. MyNextManager has the following error:
"unable to resolve class org.codehaus.groovy.grails.web.json.JSONObject @ line 3122, column 9."
I believe this is likely that I have been sent the SmartThings code rather than the Hubitat one.
I have tried to re downloading from the link in the e-mail but I get the same code.
Can you confirm and provide a link to the Hubitat code?
Regards
Barry Perfect
Hi @barryp, in fact, you haven't used the right link posted in this thread to go to the hubitat store, you went to the SmartThings store instead.
See the 1st post where the hubitat store is posted.
So, you'd need to contribute first to the right package, and then I will refund you for the SmartThings bundle. Please proceed to the following link this time:
www.ecomatiqhomes.com/hubitatstore
P.S. in order to get the minor updates after your contribution, you'd need to contribute to the right package, so I cannot just replace one package for another.
Regards.
@yracine66 have now sorted the Hubitat installation, thanks for the prompt refund of the SmartThings contribution.
One suggestion, it would help if the name of the SmartThings bundle had SmartThings in the name of the contribution/filename the same way as the Hubitat one does so you can more easily see you are picking the wrong one.
So far, the app/driver is working fine, thanks!
Regards
Barry
@yracine66 I have been using your code for many months now and have been happy with it. Recently my Nest thermostats have partially lost connection to Google Home and we have been unable to find the cause. The connection through your app to the Hubitat appears to be working fine, my Nest App is working fine, but Google home lists the devices as offline although notification of events is still appearing in the logs. I have been working with Google to understand the issue but they are stuck. Are you aware of any other users having this issue. It appears not just on my Google Home phone app, but also on my Google speakers. I don't know if your app is muddling things between Nest and Google Home at their server level or not. Any ideas?
Download the Hubitat app
