Hi, your notification requirement is outside of the scope of my smartapps.
You can only get audio notifications within the WindowDoorOpen smartapp as notifications are not supported natively by the Hubitat platform (contrary to the SmartThings platform).
And, for push notifications to your phone, you can use the native notifications app and send them according to your event selection and other notification requirements.
This is not something that can be implemented within my smartapps.
Regards
So I installed the tstat app and drivers, and can see that my Nest thermostat appears successfully as a device, and is showing the correct numbers. But, I am not able to figure out how to use it in my automations. Like, if my rule needs to enable "eco", I am not getting the tsat to appear in my list of switches, or buttons etc... what do I need to select in the rule to be able to push the tsat device buttons?
As you have chosen to code your own custom automation rules, and not use the ScheduleTstatZones smartapp, please check RM(Rule Machine), WebCore or Sharptools.
All those rule engines can call any methods on the driver (ex. eco(), away(), home(), setHeatingSetpoint(), setCoolingSetpoint, heat(), cool(), etc.) according to your own requirements and automation rules.
There are several threads in this forum about rule engines. I don't use those rule engines myself.
P.S. The list of capabilities and commands supported are listed here:
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:
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.
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?
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.
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
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.
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.
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+.