'Grabbing' a z-wave message when sent from the controller #139
-
|
I'm tinkering with indicator messages - I'm trying to create a 'base' message in a function. When I connect a debug node directly to the controller node and send an 'indicator multilevel 50' from the gui, I actually expected to see the message in the debug panel - but didn't. ps. the device updates it's indicator just fine - I would just like to know which command was sent to the device and which parameters was included. |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 28 replies
-
|
Hey, Are you referring to the Indicator CC or Multilevel Switch CC - if so The Indicator CC does not 'respond' like other CCs' Do you have a manual for the device? |
Beta Was this translation helpful? Give feedback.
-
|
All output is only for messages we receive (not what we send). HOWEVER! there is a way to see the command.
Indicator has gone through some revisions with Zwave Alliance - V1 was very simple, V2+ introduces more advanced control. |
Beta Was this translation helpful? Give feedback.
-
|
ignore the noWait stuff - that is specific to the UI |
Beta Was this translation helpful? Give feedback.
-
|
Example: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you - I'm held up right now, I'll get back as soon as possible - thank you, again! :) |
Beta Was this translation helpful? Give feedback.
-
|
Sure thing. its likely using V2+ on the Indicator - which is easy enough on the factory. or just go the route of constructing the message yourself - just remember to take out noWait if 'steeling' it from network log. |
Beta Was this translation helpful? Give feedback.
-
|
I should be able to test this today/night - I'm very appreciative of your help, just hung up like hell... I had great fun with indicators for a few hours yesterday - and will report back as soon as I have the time. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, the Indicator CC is a good one, My security pin pad uses it to indicate the current security arm modes (or to create a countdown i.e to exit the property for an example) - so I can easily sync it with my DIY alarm setup. Again, everything can be done within factory, just call out if you need help. No worries. - I am usually around. |
Beta Was this translation helpful? Give feedback.
-
|
It worked i'm no longer stranded. {mode: "ValueAPI", method: "setValue", node: 4,…} |
Beta Was this translation helpful? Give feedback.
-
|
before sure to remove noWait: true |
Beta Was this translation helpful? Give feedback.
-
|
This was the final working result - a multilevel+indicator sender in an easy understandable subflow :) I'll be tinkering with the blinking same time tomorrow (the device has blinking and blinking speed afaik)
|
Beta Was this translation helpful? Give feedback.
-
|
very nice, |
Beta Was this translation helpful? Give feedback.
-
|
Well, the cmd-factory node is way too complicated for me. The sheer amount of inputs in the cmd-factory makes the learning curve very steep. I have such flows for basic/binary set, scenes and now indicator/multichannel - they get the job done. And thank you, very much - I'm pretty proud of the progress i'm making 😃 |
Beta Was this translation helpful? Give feedback.
-
|
hmm |
Beta Was this translation helpful? Give feedback.
-
|
So with Indicator V2+ 0x01: The Multi Level Value Then the value which can be numeric for 0x01, 0x03 and 0x04 |
Beta Was this translation helpful? Give feedback.
-
|
So, to set 2 properties, let Multilevel = {
indicatorId: 1,
propertyId: 1,
value: 30 // Brightness I assume
}
let OnOffCycles = {
indicatorId: 1,
propertyId: 4,
value: 5 // How many times it flickers?
}
let Props = [Multilevel, OnOffCycles]
let Message = {
payload: {
mode: "CCAPI",
node: 2,
cc: "Indicator",
method: "set",
/* This needs to be an array, but setting using 2 indicator properties, in its self needs to be an array ;-) */
/* so param 0 is actually an array ;-) */
params: [Props]
}
}
return Messagehttps://zwave-js.github.io/node-zwave-js/#/api/CCs/Indicator?id=set |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to mark this as answered - but my morning-IQ is not sufficient. //Edit: I wanted to mark the Marcus' post about browser/network monitoring as the answer, but couldn't. I marked the post above it instead. |
Beta Was this translation helpful? Give feedback.
-
|
Someone once asked me, if it were possible to view the messages being sent from the UI - so you can capture the required message. Well....Someone once implemented the feature. @crxporter - Thoughts as well? NOTE: This is only for UI interaction - its not to monitor everything being sent out to the network, it only details what commands from the UI are taking place - but you can use the message being recorded in your setup later. Screen.Recording.2021-10-22.at.20.13.20.mov |
Beta Was this translation helpful? Give feedback.
-
|
This is just a "is it useful" type thing. |
Beta Was this translation helpful? Give feedback.
-
|
There are some places where that would be very awesome to see. I think "it is useful" and would keep it. |
Beta Was this translation helpful? Give feedback.
-
|
The ability to capture both value and cc API would be very helpful in my usecase. I actually thought I could use the GUI to build commands like that already (expand CC -option). The command viewer looks great - I would welcome it, greatly. |
Beta Was this translation helpful? Give feedback.
-
|
The UI is the only place I can capture the comms - but the UI uses the ValueID, so it will be limited to ValueAPI. Expand CCs simply auto expands the CC list when selecting a node - nothing special here sadley 😞 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, Having it log like - seems a really nice way?
|
Beta Was this translation helpful? Give feedback.
-
|
Its also placed in the right location.
|
Beta Was this translation helpful? Give feedback.
-
Could be "include/exclude" in one row with "UI monitor" in the same button row? We don't need the vertical growth again |
Beta Was this translation helpful? Give feedback.
-
|
I would probably have gone with a flag on the controller (using the debug panel) or something but I don't have the same context as you. The log-type display and button in the menu is great for me and other new people. I'm at a point where I probably don't even know, that I don't know JSON - it works and I can debug it, but I don't really understand it. |
Beta Was this translation helpful? Give feedback.
-
Fully agree here
This is my thought: A lot of users This is exactly what the new "UI Monitor" can do, the commands you see are directly usable in function nodes, where you can change any aspect of the command once copied - i.e the value to actually use for example. I have omitted inclusion/exclusion commands - as they are not simple commands, and require various steps to do a proper inclusion.
Before S2 was introduced, it was possible to do it with commands - Hey! We did once need to 😁 I did think about using the debug panel - but we cant see it if in the UI, the controller in your flow is not connected directly to the UI, which makes it more difficult to log the commands on the controller node its self. |
Beta Was this translation helpful? Give feedback.
-
|
Makes perfect sense :) |
Beta Was this translation helpful? Give feedback.
-
|
The finished UI Monitor. Screen.Recording.2021-10-23.at.08.11.01.mov |
Beta Was this translation helpful? Give feedback.
-
|
Everything is dandy - no fires what so ever! |
Beta Was this translation helpful? Give feedback.
-
|
We have some more on the way, to support a Security S2 feature. Scanning a QR code to include a device. Scan the devices QR code, and forget about it, these devices will advertise them self, and scanning its QR code, the module will 'Listen' for this advertisement, once the device is turned on / powered up - it will auto include. Its ready to use from the driver - but still has some kinks that are being ironed out. I will be implementing a web ui, allowing you to walk around the house scanning your devices to include with your phone. |
Beta Was this translation helpful? Give feedback.
-
|
This is getting ridiculous - you guys have better performance and compatibility than any of the old players in the game, already. X-D |
Beta Was this translation helpful? Give feedback.
-
|
@lurendrejer this is why I moved all my zwave over. Performance is amazing and I can now do so much more with automation and node-red and even inside of Homekit with what @marcus-j-davies has created. Welcome aboard and enjoy the ride! |
Beta Was this translation helpful? Give feedback.
-
|
............ That's better, sorry, my head needed shrinking back down 😉 Thanks guys, but I cant take all the credit, @AlCalzone, who develops/maintains the backend z-wave javascript driver that this module uses, is the reason its possible. There are a few of us who are under the zwave-js umbrella, we all maintain the different parts, but the main driver is AI's work. |
Beta Was this translation helpful? Give feedback.
Hey,
Are you referring to the Indicator CC or Multilevel Switch CC - if so The Indicator CC does not 'respond' like other CCs'
(therefore we don't see anything) its really only to... well.... indicate - i.e some devices use them to set an LED, some devices use them to trigger a sound, or in the case of outdoor sirens - to illuminate the logo on the box.
Do you have a manual for the device?