search

andrei-tatar / node-red-contrib-smartnora

Node Red Google Home integration
https://smart-nora.eu/
109 stars 24 forks source link

Thermostat "on" mode not working. #298

Closed 420pootang69 closed 6 months ago

420pootang69 commented 7 months ago

Hi,

I've a google home thermostat node.

I've enabled the "on" and "off" modes in the settings.

If I send an object into the node with either on or off, then the Nora node responds correctly and turns it on/off. However it's not 'telling' Google that the "on" mode is available.

As a result, Google can only turn off the heating, it can't turn it on.

If I access the thermostat in google and select modes, it only shows the "off" mode, which to me shows this isn't being sent to Google correctly?

How do I fix that?

420pootang69 commented 7 months ago

Screenshots to show the issue.

image

image

andrei-tatar commented 7 months ago

Hi,

As far as I remember, in Google Home, on is a shorthand for the last used mode. It's only supported when using voice commands. It doesn't appear in the user interface. So I suspect you want to also enable heat as a supported mode.

https://developers.home.google.com/cloud-to-cloud/traits/temperaturesetting

image

420pootang69 commented 7 months ago

Hmmm,

I'll have a play with this later, but what's extra confusing is that telling Google to "turn on the heating" get a positive response, as if it's trying to do something, but the node doesn't react at all. A debug on the output shows Nora doing nothing.

On Fri, Feb 9, 2024, 8:03 AM Andrei Tatar @.***> wrote:

Hi,

As far as I remember, in Google Home, on is a shorthand for the last used mode. It's only supported when using voice commands. It doesn't appear in the user interface. So I suspect you want to also enable heat as a supported mode.

https://developers.home.google.com/cloud-to-cloud/traits/temperaturesetting

image.png (view on web) https://github.com/andrei-tatar/node-red-contrib-smartnora/assets/6473183/4a59d0c7-9948-44c0-a2be-24233a57bad2

— Reply to this email directly, view it on GitHub https://github.com/andrei-tatar/node-red-contrib-smartnora/issues/298#issuecomment-1935485700, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2QNZNKAHS5HSONDFJDWD3YSXJ4XAVCNFSM6AAAAABDAIV446VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGQ4DKNZQGA . You are receiving this because you authored the thread.Message ID: @.***>

420pootang69 commented 7 months ago

Screenshot_20240209-082115

Image didn't attach from email reply.

github-actions[bot] commented 7 months ago

This issue is stale because it has been open for 14 days with no activity.

420pootang69 commented 6 months ago

OK, Yeah, I've this "fixed".

I don't actually know what's causing Google to choose between "heat" and "on", but I did have to enable "heat" in the Nora options to make this work 100% of the time. It seems to flip between either sending a "heat" request, or an "on" request. My solution to this was was a function that converts either "heat" or "on" to a bool true in node red. I'll close this now, I just wanted to update and say I have it working now.

420pootang69 commented 6 months ago

Reopened just to add solution and clarify node behavior for other users.