In the zwavejs Mqtt add-on go to settings then in the general area, you go to the “new value” link.
From there you can chose device (note: before it was each device now at this level its the family so single ports or 6 ports) then in the value you get a drop down list, and you can scroll through but again it’s grouped so for example you can poll power (W) for all port 1 of all your 6 port power boards. Slide the poll toggle on, and a new field for polling seconds comes up. Minimum is 10.
I did 20 seconds to see how it goes. So far it’s fine.
Then click add.
I’ve repeated that for port 2, 3, 4, 5, 6. For power
And all of my single ports.
Final step. Once you have added them at the bottom is a save button press that and it should say it’s competed or words like that.
I will add polling for the kWh value for each port tonight. Probably set that at 300 seconds (5minutes) so it’s refreshes the new energy charts.
I have a few more use case tests to run but so far I have 90% of what I need tested and works well. The last 10% isn’t a show stopper so I’ll clean up somethings this week and move forward.
Thanks for posting this! I have some devices that require polling, and that’s always sort of caused me to defer coverting everything over to zwavejs. If there was some conversion script, that’d be great, but I don’t know if that will be forthcoming? I’ve a few dozen Z-Wave devices (a few of which create a bunch of entities, like these power strips) and don’t look forward to all the renaming that’s required. I’ll have to see if I can hack up a script to use hass-cli to do the renaming based on the node ID values associated with the entities before and after.
No problems at all. I have to thank you for your support in the early days. So happy to be able to give back.
In terms of getting a script going I don’t want to discourage you but I found on the other side of 1.4 to js that the zwave entities have change in some places.
For example in the old zwave there was a previous energy and previous power entity which aren’t there in js
There are some new entities which I don’t use.
And the old zwave.devicename.status is gone it’s now a sensor node status.
I managed to get a hold of some more of these devices recently which was one of the drivers to change now, if zwavejs worked I had less to rewrite rather than setting them all up in 1.4 and then again in js.
If I get a chance this weekend I will get a dump of the zwave js default entities so you can see if you can plot a way through for any script you might want to attempt. Or do what I did and get some headphones lock yourself away for an hour or so and just start typing.
Still using the old (deprecated) zwave integration? As of this release Home Assistant helps you migrating your z-wave network to Z-Wave JS, using a migration wizard.
