# \[ANNOUNCE\] node-red-contrib-zwave-js V8 Baby!

**URL:** <https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151>\
**Category:** Share Your Nodes\
**Created:** [23 September 2022 17:03 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151 "2022-09-23T17:03:02Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [23 September 2022 17:03 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/1 "2022-09-23T17:03:02Z")

</div>

Here it is...... **V8** of **node-red-contrib-zwave-js**

After

- 3+ Months
- 120 Commits
- 14 changed files
- Various UI design discussions

i present the below change log

**Breaking**

- Dropped support for Node 12 (min required is now 14.13.0)
- If you use the set method of the Configuration CC in CCAPI mode, the arguments must now have one object (see Github CL)
- ValueAPI is now default on the CMD Factory node. If you have problems with this node after the update, please open it up, and select your API, then save.

**New Features**

- Default scales can now be applied inside the controller config
- Added ability to export/import node name & location maps
- Implemented a Firmware Update Service, that allows to install Firmware on devices that have known updates - Please double click controller!
- 2 new event types have been added : ALIVE, DEAD - these allow you to monitor if a device has been marked dead or alive accordingly.
- Added a color chooser for color input types in the UI
- Added a new Driver function getLastEvents
- Device last seen timestamp is now shown in the UI
- Node list now contains the date when the device was last seen.

**Bug Fixes**

- Modal alerts are now rendering HTML content once again
- Missing normalizedObject.label for Thermostat devices
- Fix some data type odities in the UI editor
- msg properties are now carried through the CMD Factory node

**Changes**

- Current Value(s) who's type is an object have been changed to prompt for a double click in the UI
- Association Management has been updated, and changes are now applied in batch.
- For battery operated devices, certain UI actions now ask you to wake up said device before anything is comit
- Various performance boosts in the UI
- Bump ZWave JS to V10
- Bump Winston
- Bump ESlint

Sorry for the delay in updates - but never the less enjoy!

> **[node-red-contrib-zwave-js](https://flows.nodered.org/node/node-red-contrib-zwave-js)**
>
> The most powerful, high performing and highly polished Z-Wave node for Node-RED based on Z-Wave JS. If you want a fully featured Z-Wave framework in your Node-RED instance, you have found it.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [28 September 2022 14:15 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/2 "2022-09-28T14:15:33Z")

</div>

Thanks a lot for all the support and maintenance.

I am running into some issues, maybe you are familiar with this use case, but I am running node-red in a LXC container (using proxmox) and am passing through my zwave usb device to the container, when the controller tries to initialize, i get the following error:

```auto
ZWaveError: Failed to open the serial port: Error: Inappropriate ioctl for device setting custom baud rate of 115200 (ZW0100)

```

Is this something i can set/configure or should it actually be 115200 ?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [28 September 2022 14:29 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/3 "2022-09-28T14:29:31Z")

</div>

Hi @bakman2  
I can't say I have ever seen this.

**115200** is pretty standard for a z-wave serial module.

The driver (zwave-js) will set the following when connecting :

- baudrate: 115200
- data bits: 8
- parity: none
- stop bits: 1

Maybe check if the LXC container is setting stuff (when it should be left to zwave-js)  
Sadly I know nothing about container based setups.

I did find this that also refers to LXC (but for Zigbee)

> <https://github.com/Koenkk/zigbee2mqtt/issues/6732>
>
> \<!--
> Before submitting an issue make sure you've searched for a similar issue a…nd read the documentation: https://www.zigbee2mqtt.io/.
> 
> Rules (don't ignore these, your issue will be closed without further notice):
> \- English only
> \- Make sure you are on the latest Zigbee2MQTT version
> \- Provide a clear description of the problem
> \- DON'T copy logs directly here, post a link to https://hastebin.com/ or https://pastebin.com/.
> \- Make sure you are running the latest firmware https://github.com/koenkk/z-stack-firmware.
> 
> Did you read the FAQ?
> \- https://www.zigbee2mqtt.io/information/FAQ.html
> 
> Zigbee2MQTT fails to start?
> \- https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start
> 
> Having issues when using a CC2531?
> \- Make sure the CC2531 is connected through a USB extension cable
> \- Try the source routing firmware: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack\_Home\_1.2/bin/source\_routing
> \- With larger networks (30/40+) devices, your CC2531 might not be powerful enough. This will cause weird issues, in this case it's advised to use a more powerful adapter: https://www.zigbee2mqtt.io/information/supported\_adapters.html#texas-instruments-cc26x2r1
> 
> Unsupported device?
> \- https://www.zigbee2mqtt.io/how\_tos/how\_to\_support\_new\_devices.html
> 
> Device does not pair or interview fails?
> \- https://www.zigbee2mqtt.io/information/FAQ.html#why-does-my-device-not-or-fail-to-pair
> 
> Bug report?
> \- If applicable, provide steps how to reproduce the problem.
> \- Provide the herdsman debug logging: https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging
> 
> \--\>
> 
> 
> 
> \## My Zigbee2MQTT stopped working
> I tried to update from version 1.16 to the latest version 1.18.1. Running on an Debian 10 LXC container. Nothing changed to my adapter settings or my devices.
> 
> \## What did you expect to happen
> \- Update went without any problems
> \- My USB port is visible and i have write access
> \- Would expect that I could start Zigbee2MQTT without any problems
> 
> \## Debug info
> Platform: Debian 10 LXC container running in Proxmox
> Zigbee2MQTT version: 1.18.1
> Adapter hardware: CC2652
> 
> \## Logging
> \`\`\` 
> Mar 16 11:01:33 zigbee2mqtt-lxc systemd\[1\]: Started zigbee2mqtt.
> Mar 16 11:01:33 zigbee2mqtt-lxc npm\[558\]: \> zigbee2mqtt@1.18.1 start /opt/zigbee2mqtt
> Mar 16 11:01:33 zigbee2mqtt-lxc npm\[558\]: \> node index.js
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:info 2021-03-16 11:01:34: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2021-03-16.11-01-33' filename: log.txt
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:info 2021-03-16 11:01:34: Starting Zigbee2MQTT version 1.18.1 (commit #a43d1f3)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:info 2021-03-16 11:01:34: Starting zigbee-herdsman (0.13.71)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:error 2021-03-16 11:01:34: Error while starting zigbee-herdsman
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:error 2021-03-16 11:01:34: Failed to start zigbee
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:error 2021-03-16 11:01:34: Exiting...
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: Zigbee2MQTT:error 2021-03-16 11:01:34: Error: Error while opening serialport 'Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200'
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at Znp.\<anonymous\> (/opt/zigbee2mqtt/node\_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at Generator.next (\<anonymous\>)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at /opt/zigbee2mqtt/node\_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at new Promise (\<anonymous\>)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at \_\_awaiter (/opt/zigbee2mqtt/node\_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at SerialPort.\<anonymous\> (/opt/zigbee2mqtt/node\_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at SerialPort.\_error (/opt/zigbee2mqtt/node\_modules/zigbee-herdsman/node\_modules/@serialport/stream/lib/index.js:198:14)
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: at /opt/zigbee2mqtt/node\_modules/zigbee-herdsman/node\_modules/@serialport/stream/lib/index.js:242:12
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! code ELIFECYCLE
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! errno 1
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! zigbee2mqtt@1.18.1 start: \`node index.js\`
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! Exit status 1
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR!
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! Failed at the zigbee2mqtt@1.18.1 start script.
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! A complete log of this run can be found in:
> Mar 16 11:01:34 zigbee2mqtt-lxc npm\[558\]: npm ERR! /root/.npm/\_logs/2021-03-16T11\_01\_34\_620Z-debug.log
> Mar 16 11:01:34 zigbee2mqtt-lxc systemd\[1\]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
> Mar 16 11:01:34 zigbee2mqtt-lxc systemd\[1\]: zigbee2mqtt.service: Failed with result 'exit-code'.
> Mar 16 11:01:34 zigbee2mqtt-lxc systemd\[1\]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
> Mar 16 11:01:34 zigbee2mqtt-lxc systemd\[1\]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 4.
> Mar 16 11:01:34 zigbee2mqtt-lxc systemd\[1\]: Stopped zigbee2mqtt.
> \`\`\`

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [28 September 2022 14:45 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/4 "2022-09-28T14:45:31Z")

</div>

Ignore me, i used wrong device file/permissions, controller started now. Thanks for the quick response!

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [15 October 2022 12:19 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/5 "2022-10-15T12:19:10Z")

</div>

Hi Marcus,

any known problems when updating from V7 to V8?

regards  
Hannes

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [15 October 2022 12:33 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/6 "2022-10-15T12:33:36Z")

</div>

No problems I know of 😉 - but some potential breaking changes, extremely minor however.

See the breaking changes section.

> **[Release Release v8.0.0 · zwave-js/node-red-contrib-zwave-js](https://github.com/zwave-js/node-red-contrib-zwave-js/releases/tag/v8.0.0)**
>
> Breaking Changes
> 
> Dropped support for Node 12 (min required is now 14.13.0)
> If you use the set method of the Configuration CC in CCAPI mode, the arguments must now have one object (see Github CL)
> 
> ...

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [29 October 2022 13:15 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/7 "2022-10-29T13:15:34Z")

</div>

Hi Marcus,  
version 8 runs perfectly 👍

One other question. I have upgraded my Z-Pi 7 controller to 7.18.1.  
It works ok but instead of 2 green leds i now have one green and one red. I send a message to aeotec support and received this:  
One of the LEDs typically indicates the z-wave frequency of the Z-Pi 7, if you are having issues with controlling your devices, then try changing the Z-Pi 7 Z-Wave Frequency which can be done in Z-WaveJS UI  
I checked your UI and I have power level 9.5 and Measured 0dbm 0.  
What would you do in this case? Run with the red led?  
Appreciate your input on this matter,  
Johannes

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [29 October 2022 13:28 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/8 "2022-10-29T13:28:53Z")

</div>

Hi @juntiedt - Glad V8 is up and running for you.

I wouldn't change the power levels unless there is a very specific reason for doing so.  
sometimes you get worst performance and increased noise on the network.

The LED's might indicate the region frequency (which can also be set) - but it needs to be supported by the radio its self.

My advice would be - if you see no issues, I would leave as is - if you find you do need to increase it - Aeotec are more equipped to offer the optimum levels guidance (i'm still using Gen 5 Sticks 😅 )

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [29 October 2022 14:59 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/9 "2022-10-29T14:59:01Z")

</div>

ok, thanks.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [10 November 2022 22:29 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/10 "2022-11-10T22:29:14Z")

</div>

@marcus-j-davies What is the use case for the `normalizedObject` ? I mean i can see a use case (ie, dumping it into a db), but in that case it missed the nodeId and nodeName, could those be added (if that is the purpose) ?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [11 November 2022 12:39 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/11 "2022-11-11T12:39:06Z")

</div>

Hi @bakman2

`normalizedObject` is an attempt to simplify the payloads, so it’s easier to understand what just happened.

The module does not interfere with what is being received, I.e the `object` is not being modified since leaving the driver.

As this contains quite a lot of data - the object you are referring to is a slimmed down / to the point alternative that’s aims to be uniform.

V9 is in the works, that could change a lot of this (it’s a typescript refactor), but that won’t drop until next year.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 November 2022 07:05 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/12 "2022-11-21T07:05:15Z")

</div>

@marcus-j-davies

Another question, I am struggling with the "ValueAPI" "CCAPI" concepts, I want to set some undocumented value by manufacturer, I see in the home assistant forums that folks managed to do it, but i have no idea how to translate this in NR.

```auto
  command_class: "49"
  method_name: sendReport
  parameters:
    - 1
    - 0
    - 20.00
  endpoint: "0"
....

3105014207d1
31 -> Command Class 49 (hex 31)
  05 -> Command SENSOR_MULTILEVEL_REPORT
    01 -> Sensor Type == 1 == Air Temperature
      42 -> 0b1000010 -> Precision = 2, Scale = 0, Size = 2 bytes
        07d1 -> Temp value 20 (hex 14) 2001, which is 20.01 with precision 2

```

[Source info](https://community.home-assistant.io/t/eurotronic-spirit-z-wave-external-temperature-sensor/88430/61)

Which node(s) do i need to use for this ? the cmd factory ? or just the device node and what should the message look like ?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 November 2022 07:22 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/13 "2022-11-21T07:22:28Z")

</div>

Hi @bakman2 try this.

```auto
let Message = {
    payload: {
        mode: "CCAPI",
        node: 2,
        cc: 49,
        method: "sendReport",
        params: [1,0,20.00]
    }
}
return Message

```

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 November 2022 07:27 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/14 "2022-11-21T07:27:13Z")

</div>

Thanks, i received an error, might be related to the device itself

```auto
ZWaveError: Invalid CC Multilevel Sensor! (ZW0300)

```

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 November 2022 07:32 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/15 "2022-11-21T07:32:44Z")

</div>

Here:  
`params: [1,0,20.00]`

is the following.

- sensorType = 1 (Temp)
- scale = 0 (Celsius (°C))
- value = 20.00

Send it to the controller and ensure `node` is correct (and the device is awake 😅)  
The `CCAPI` is an untethered API i.e your on your own, where as the `ValueAPI` has all sorts of magic to ensure local data caches are in sync

See here.

> **[Z-Wave JS - Z-Wave driver written entirely in JavaScript/TypeScript](https://zwave-js.github.io/node-zwave-js/#/api/CCs/MultilevelSensor?id=sendreport)**
>
> Z-Wave driver written entirely in JavaScript/TypeScript

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 November 2022 13:09 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/16 "2022-11-21T13:09:45Z")

</div>

Ok thanks and to which node do i send this, controller, command, device?

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 November 2022 14:05 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/17 "2022-11-21T14:05:42Z")

</div>

Send this to the `controller node` or a `device node`. If using `device node` and your `device node` is enabled for multiple devices, ensure you include `node` else it will target the node that is addressed in the config on the `device node`

This message can be created using CMD Factory also.  
The CMD Factory node just creates ready to use messages.

```auto
/* 0x01 - Temperature */ 
/* 0x00 - Celsius */
let Message = {
    payload: {
        mode: "CCAPI",
        node: 2, /* The node ID it should target */
        cc: 0x31, /* Multi Level Sensor */
        method: "sendReport", /* Function on this CC */
        params: [0x01,0x00,20.00] /* Function params -> Sensor Type, Scale, Value*/
    }
}
return Message

```

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 November 2022 16:43 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/18 "2022-11-21T16:43:22Z")

</div>

I receive the same error, I will search a bit further how this thing can be set.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [21 November 2022 17:20 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/19 "2022-11-21T17:20:51Z")

</div>

I think I got it working by using:

```auto
const temperature = RED.util.cloneMessage(global.get("state.netatmo_temperature"))
const temperature_formatted = Number(temperature.toFixed(1) + "1");
node.warn(temperature_formatted)

const nodes = [2,3]

nodes.forEach(n=>{
    let payload = {
        mode: "CCAPI",
        node: n,
        cc: "Multilevel Sensor",
        method: "sendReport",
        params: [1, 0, temperature_formatted]
    }
    node.send({payload})

})

```

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [21 November 2022 17:23 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151/20 "2022-11-21T17:23:59Z")

</div>

If you did not receive any error - it likely would have.  
if you enable Driver logging (at least `debug` level) and paste the output, I can confirm.

[Next page](https://discourse.nodered.org/t/announce-node-red-contrib-zwave-js-v8-baby/68151.md?page=2)