coldfire84 / node-red-contrib-alexa-home-skill-v3

A Node-RED node to control things via Amazon Alexa *and* Google Home
https://red.cb-net.co.uk/
Apache License 2.0
17 stars 8 forks source link

"Alexa turn on aircon" - "It is in cooling mode" #15

Closed logon84 closed 2 years ago

logon84 commented 2 years ago

Describe the bug I closed the issue in the wrong repo and writing it here. It's been 2/3 days since I am unable to start aircon telling alexa. Every time I say to her I want to start aircon, she replies it is in cooling mode. It's not that Alexa tells me my actual working mode, but it in fact switches my working mode from HEAT to COOLING.

To Reproduce "Alexa turn on aircon" - "It is in cooling mode" ||| "Alexa enciende el aire" - "Está en modo enfriamiento"

Expected behavior "Alexa turn on aircon" --> aircon starts operating.

Log Output

5 Jan 12:25:31 - [info] Starting flows
5 Jan 12:25:31 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] Node-RED contrib version: v0.4.66
5 Jan 12:25:31 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] Connecting to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: XXXXXX
5 Jan 12:25:32 - [info] [alexa-smart-home-v3-conf:97a70534.f2dd1] Node-RED contrib version: v0.4.66
5 Jan 12:25:32 - [info] [alexa-smart-home-v3-conf:97a70534.f2dd1] Connecting to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: XXXXXX
5 Jan 12:25:32 - [info] Started flows
5 Jan 12:25:32 - [info] [mqtt-broker:XXXXX mqtt server] Connected to broker: mqtt://192.168.1.1:1883
5 Jan 12:25:32 - [info] [alexa-smart-home-v3-conf:97a70534.f2dd1] Successfully connected to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: XXXXXX
5 Jan 12:25:32 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] Successfully connected to Alexa/ Google Home Skill MQTT server: mq-red.cb-net.co.uk, account username: XXXXXX
5 Jan 12:25:33 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] sensor ambiental : sending state update, topic:state/strummer84/6634 message:{"messageId":"af59bf18-3675-4166-915d-b819c397f16f","payload":{"state":{"temperature":18}}}
5 Jan 12:25:33 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] Aire : sending state update, topic:state/strummer84/6612 message:{"messageId":"03c52f91-af23-4b8e-976a-cfca386d6210","payload":{"state":{"power":"OFF","thermostatMode":"HEAT","thermostatSetPoint":24.5}}}
5 Jan 12:26:06 - [info] [alexa-smart-home-v3-state:sensor ambiental] sensor ambiental state node: discarded duplicate state payload
5 Jan 12:26:06 - [info] [alexa-smart-home-v3-state:Aire] Aire state node: discarded duplicate state payload
5 Jan 12:26:32 - [info] [alexa-smart-home-v3-state:sensor ambiental] sensor ambiental state node: discarded duplicate state payload
5 Jan 12:26:37 - [info] [alexa-smart-home-v3-state:sensor ambiental] sensor ambiental state node: discarded duplicate state payload

<<<<<<<<ALEXA turn ON aircon>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

5 Jan 12:27:09 - [info] [alexa-smart-home-v3-conf:5803a0a7.51fa3] Aire : sending state update, topic:state/strummer84/6612 message:{"messageId":"84371931-fef8-4e53-bc75-a5e1d7689ac4","payload":{"state":{"power":"OFF","thermostatMode":"COOL","thermostatSetPoint":24.5}}}

Environment (please complete the following information):

Node-RED node version: 14.17.6
Node-RED version: 1.0.3

Additional context PIC with my nodes: nodes Add any other context about the problem here. I can see thru a debug node (msg.command) connected to alexa--smart-home v3 node that when saying "turn on aircon", the debug node shows SetThermostatMode command only, so it doesn't turn on. I tried apeaking spanish and english to alexa and I confirm it is not a language issue... It is strange because the same setup has been working perfectly for two years now until 3 days ago.

logon84 commented 2 years ago

Any help?

coldfire84 commented 2 years ago

I've replicated the fault , just working through where the erroneous status is coming from (the Amazon Alexa API, or the service). Either way I'm hopeful I can fix it (just struggling for time of late , due to work!).

logon84 commented 2 years ago

Ok cool, at least I know I am not the only one :).

coldfire84 commented 2 years ago

Can you try and modify the device (via red.cb-net.co.uk) as below:

image

Then, importantly, unlink the skill an re-link via the Alexa App.

This fixed the issue on my test device, let me know if it does for you.

logon84 commented 2 years ago

Ok, now it's fixed! Following your steps, still Alexa behaves the same if I still call the device "Aire". I renamed it to "Aircon" and now it's working. Thank you so much!