I don't think my Ecobee node has been working since the 11 upgrade

Third party integrations Node-RED
1

This code works just fine in dev tools

service: ecobee.delete_vacation
data:
  entity_id: climate.thermostat
  vacation_name: NotHome

But the same basic code does not work in Node-Red. Here’s a screenshot, including the debug error.

image
image884×812 28.8 KB

And if needed, here’s the actual (scrubbed) JSON. What’s going on here?

[{"id":"a3d5f4248db9b1ac","type":"inject","z":"4aafea6f.327f44","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":1360,"y":300,"wires":[["d31319305db9e384"]]},{"id":"d31319305db9e384","type":"api-call-service","z":"4aafea6f.327f44","name":"","server":"","version":4,"debugenabled":false,"domain":"ecobee","service":"delete_vacation","target":{"areaId":[],"deviceId":[],"entityId":["climate.thermostat"]},"data":"{\"vacation_name\":\"NotHome\"}","dataType":"jsonata","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1270,"y":200,"wires":[["ed168afe6d93d4d5"]]},{"id":"ed168afe6d93d4d5","type":"debug","z":"4aafea6f.327f44","name":"Ecobee","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":1500,"y":200,"wires":[]}]

2

You have a capital letter in entity name and climate. is missing.

3

The new version of node red truncates the entity names to their friendly name for some auto fill entities.

image

image

@flyize is delete_vacation the right service?

1 Like
4

It’s what I’m trying to do, yes. And it works from Services.

5

There has been quite a few entity_id problems on several other service calls as well, seems something is up with the newest version.

You can try deleting the node, deploy, pulling out a new call service and then set it up the same way again. Otherwise if this is causing a lot of problems, try restoring the previous version.

I say try because this could also be a change in HA and the nodered version may not make a difference.

1 Like
6

Yeah, I tried deleting and recreating the node. It did not help. I’m almost positive this issue started with the v11 upgrade of NR.

7

Is this something I make a github report for?

8

I just loaded your flow again and I have a newer version of the home assistant nodes, have you installed the most recent? Go to palette manager, installed nodes, search home assistant, click little box in lower right corner to upgrade.

You may need to press it more than once. depending on how many versions you are behind. Then restart nodered, upgrade nodes and deploy.

1 Like
9

I had updated it the other day, but I’ll be damned - the newest one fixed it. Thanks for the suggestion!