anyone already tried this?
-
Alexa Node-Red Skill
-
I’m trying it at the moment
The first steps are working with pimatic-node-red (with direct integration of pimatic commands) like simple switch on and off.I was wondering whether it is possible to customize the response of the echo dot?
-
I have implemented some switches but i am struggling with the shutters. What’s the command to move up or down an shutter in Alexa?
-
@kenci I think an direct implemention of shutters don’t exist at the moment.
The only chance maybe is to take the workaround over on and off and percentage value of a dimmer with msg.command:- SetPercentageRequest
- IncrementPercentageRequest
- DecrementPercentageRequest
-
@techbarney i used on off switch for now and it works good. I am saying “computer, Wohnzimmer Jalousie Links ab” / “computer, living room shutter down” and that’s it.
-
short info:
getTemperatureRequest for heating devices and temperature sensors works too.
-
@Felix-Haverkamp You know there is now also a pimatic plugin for node-red directly? So no need to use the node-red plugin of pimatic anymore.
-
yes thats true, but with this node-red skill you can use more commands and you can better customize commands and responses.
For Example:
TurnOnRequest
TurnOffRequest
SetPercentageRequest
IncrementPercentageRequest
DecrementPercentageRequest
SetTargetTemperatureRequest
IncrementTargetTemperatureRequest
DecrementTargetTemperatureRequest
GetTemperatureReadingRequest
GetTargetTemperatureRequests
SetLockState
GetLockState
SetColorRequest
SetColorTemperatureRequest -
@Felix-Haverkamp I dont have a Alexa (jet) and i use the combination of nodered with About everything ranging from mqtt, pimatic, mysensors etc.
In your first post you mention to install the node red plug-in in pimatic? I dont think that is required anymore and makes the nodered install itself more flexible and more up to date! -
yeah, thought the intergrated node-red is nice to use. But in the end, and with node-red updates coming with pimatic, i know think its a bad idee. With every update i have to add all node-red plugins again.
-
@felix-haverkamp said in Alexa Node-Red Skill:
SetPercentageRequest
Hi,
I try to dim my device with Alexa - Nodered - Pimatic. I don’t understand which deveice parameter I need to use in the Pimatic NodeRed component.
If I use the API this works:
http://IPADDRESS/api/device/leeslamp-dimmer/changeDimlevelTo?dimlevel=8In the NodeRed Node I use the action: changeDimlevelTo, param name is dimlevel. Via Alexa the msg.payload should contain the percentage. In order to test I prefill this with 50. The only thing what happens is that I get an error message: false == true.
How should I configure this node?
-
@ptrvh said in Alexa Node-Red Skill:
ry to dim my device with Alexa - Nodered - Pimatic. I don’t understand which deveice parameter I need to use in the Pimatic NodeRed component.
If I use the API this works:
http://IPADDRESS/api/device/leeslamp-dimmer/changeDimlevelTo?dimlevel=8
In the NodeRed Node I use the action: changeDimlevelTo, param name is dimlevel. Via Alexa the msg.payload should contain the percentage. In order to test I prefill this with 50. The only thing what happens is that I get an error message: false == true.
How should I configure this node?Can you please post an example flow you are using. This will be helpful to reproduce the issue.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Flow looks as follow:
Switch Node
Turn on and Turn off work
Dimmer does not. I added a mail flow to see which data is send. There is not send any data on the dimmer flow (setpercentagerequest).
I say to Alexa: “Alexa, Dim reading to 100 percent”, she confirms but nothing happens.
If I say: "Alexa, turn off Reading, she confirms and the light is switched off.Am I using the wrong command?
-
I added a debug node and this is the message which is send from Alexa to the Switch Node:
msg : Objectobject
topic: “”
name: “reading”
_messageId: “bd9c6e88-071a-40b9-aa62-de7123d53060”
_applianceId: “18779”
_confId: “ca5e89e5.f60c88”
command: “SetPercentageRequest”
extraInfo: object
payload: 50
_msgid: “d27c2920.2d83d8”
-
It’s working, changed the order of the switch (by removing the SetPercentage and adding the SetPercentageRequest and then moved the order.
After I moved the order again it still works… I think the deletion and creation in the Switch node did it.