-
|
Hello, how can I migrate my Z-Wave from Home Assistant to Node Red? I'm using Z-Wave JS to MQTT and Z-Wave Js. Is it only to move the USB plug and my network will be recreated? |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 41 replies
-
|
Hi @widert, Please do bear in mind, this module is not designed to work with the internals of HA - its strictly Node RED only. On that bases. Then after you install the module in Node RED, add a controller node into your flow - select your serial port so on and so forth. or load in the example that comes with the module. |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, I'll give it a try then! Tom |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, it seems like it is not able to recreate the network... |
Beta Was this translation helpful? Give feedback.
-
|
And this is probably the one I should address: { |
Beta Was this translation helpful? Give feedback.
-
|
no worries.
If you go to the import menu - there is a full example on how all the nodes work. |
Beta Was this translation helpful? Give feedback.
-
|
Brilliant, this gave me the following: { |
Beta Was this translation helpful? Give feedback.
-
|
Nice! The UI will actually control your network so the commands it uses can be used in your function nodes. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, so next issue is running a roller shutter in/out: (Testing with CMD Factory) So to run it down using the method you described earlier, I go into the node, select the Multilevel switch and set Up to true (!)
The UI monitor gives me the following: To replicate I use the following nodes: The factory node configuration: The Binary switch device: The event-filter node: However, when injecting "True", there is a small movement in the roller shutter, but then it stops...?? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @widert, I think I see the problem.
Given you can see here, the parameters required for So, how do we fix this? 1) Change the method to
2) change the params text box to the following object (Click the 3 dots ... next to it), and set the endpoint to why? if you look at the required params for
[
{
"ignoreStartLevel": true,
"direction": payload
}
]3) finally, you can now send using an inject node the below (be sure to set {
payload: "Up" | "Down", /* Direction */
topic: 1 /* Endpoint */
}You can see from the above, the Find below the setup. If you are addressing this to a device node, depending on its mode, you can omit My suggestion however - set CMD Factory to
is CCAPI useful? - yes if course, but more often than not, its only used if you are executing things that the Hopefully the above make sense? 😬 |
Beta Was this translation helpful? Give feedback.
-
|
Using CMD Factory is trivial when using you can pass in
You can also provide a partial {
"commandClassName": "Mulitlevel Switch",
"commandClass": 38,
"endpoint": 1,
"property": direction,
"propertyName": direction
}So many possibilities. |
Beta Was this translation helpful? Give feedback.
-
|
Puuh, struggelig to get this right. I tested the CCAPI example, but was not able to make it work. Using your suggestion this is how my Command factory node is configured: Debug: |
Beta Was this translation helpful? Give feedback.
-
|
So if I instead would like to go the ValueAPI route then I need to send the following:
How do I send this? Through a function node only? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @widert You're connecting the CMD Factory to the device-node or controller right? 😄 The the property is called
The ValueAPI is likely adding this property behind the scene, hence why it works under the UI (The UI uses the ValueIAPI) see here, for the ValueAPI Method using CMD Factory. if you wanted to do it in a function node; let ValueID = {
"commandClassName": "Mulitlevel Switch",
"commandClass": 38,
"endpoint": 1,
"property": "Up",
"propertyName": "Up"
}
let Message = {
payload: {
"mode": "ValueAPI",
"method": "setValue",
"node": 10,
"params": [ValueID, true]
}
}
return Message |
Beta Was this translation helpful? Give feedback.
-
|
Ok, finally got it running now using the following flow; My function node contains: |
Beta Was this translation helpful? Give feedback.
-
|
Cool! In essence, the CMD Factory node in ValueAPI mode will do exactly what the function node is doing. ValueAPI is the better API 👍 |
Beta Was this translation helpful? Give feedback.
-
|
You can now see, how your function node, has the shape of the message displayed in UI Monitor.
We are just wrapping the valueID in a variable, instead of writing it in line. let ValueID = {
"commandClassName": "Mulitlevel Switch",
"commandClass": 38,
"endpoint": 1,
"property": "Up",
"propertyName": "Up"
}
let Message = {
payload: {
"mode": "ValueAPI",
"method": "setValue",
"node": 10,
"params": [ValueID, true]
}
}
return Message |
Beta Was this translation helpful? Give feedback.
-
|
How can I now read status of the blinds, i.e if they are up or down? The "Current Value" doesn't change, maybe I need to run calibration first?
|
Beta Was this translation helpful? Give feedback.
-
|
Morning @widert You can obtain the current Value with the below. let ValueID = {
"commandClassName": "Mulitlevel Switch",
"commandClass": 38,
"endpoint": 1,
"property": "currentValue",
"propertyName": "currentValue"
}
let Message = {
"payload": {
"mode": "ValueAPI",
"node": 10,
"method": "getValue",
"params": [ValueID]
}
}
return Messagebut also, when ever the device sends an update you will get a |
Beta Was this translation helpful? Give feedback.
-
|
So, a lot of questions, I'm sorry... |
Beta Was this translation helpful? Give feedback.
-
|
I had a notification, but cant find anything you wrote? |
Beta Was this translation helpful? Give feedback.
-
|
Tried again... :) |
Beta Was this translation helpful? Give feedback.
-
|
No worries. it's the same for obtaining the roller status, but for a different ValueID. 👍 let ValueID = {
"commandClassName": "Notification",
"commandClass": 113,
"endpoint": 0,
"property": "Home Security",
"propertyKey": "Motion sensor status",
"propertyName": "Home Security",
"propertyKeyName": "Motion sensor status"
}
let Message = {
"payload": {
"mode": "ValueAPI",
"node": <NodeID>,
"method": "getValue",
"params": [ValueID]
}
}
return Message |
Beta Was this translation helpful? Give feedback.
-
|
And don't be Sorry. |
Beta Was this translation helpful? Give feedback.
-
|
And remember, you will also get them, when they update. as a |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, not getting it right. My setup: The function The z-wave device mode:
The event-filter node:
The filter: The response I'm getting: |
Beta Was this translation helpful? Give feedback.
-
|
Its here.
|
Beta Was this translation helpful? Give feedback.
-
|
You don't have to use event filter - its just a helper tool, if you want to split the values out to different paths/wires |
Beta Was this translation helpful? Give feedback.
-
|
Like this.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Too late in the evening...😁 |
Beta Was this translation helpful? Give feedback.
Hmm, not getting it right. My setup:
The function
The z-wave device mode:
The event-filter node:
The filter: