Same for me i have it included but doesnt work, my blinds in my kitchen closed Till 3 weeks now and i dont have connected a Hardware switch.
I had an issue with HA where it wouldn’t update the entities / devices when switching from non beta the new beta, so I deleted the integration and re-added it for everything to come in properly.
Warning ! You’ll have to re-name them all again !
GoControl is just the branding, Nortek is the manufacturer, mine shows up as it and it works fine.
My blinds also work fine (Bali / Somfy) (see below)
My issue is still my old Schlage BE469, they work fine, except that they don’t report lock/unlock status from where, i.e. locked manually, locked by keypad. ZWaveJS does, so it’s something with the integration.
There was a bug in beta0 and beta1 for transferring entities. If you can roll back to a backup that works then upgrade to beta2 (released today) it should work.
Check out the issues listed in b1 and b2 for details.
If you are using the zwavejs2mqtt add-on passing in the toneID value you want to use to zwave/(node-id)/121/0/toneId/set works, but this doesn’t let you dynamically set the volume. Technically something like setting zwave/_CLIENTS/ZWAVE_GATEWAY-(mqtt server)/api/sendCommand/set to
{ "args": [
{
"nodeId": (nodeId),
"commandClass": 121,
"endpoint": 0
},
"tonePlaySet",
[
{"toneId": (toneID),"volume": (volume)}
]
]
}
but I haven’t gotten that soundSwitch command to work yet…
1 Like
This should no longer be an issue. This is only an issue if you updated to beta1, beta2 is good to go.
My battery devices are 6 Fibaro Door/Window sensors and two Fibaro Flood Sensors.
I already wandered around my house to wake them up. I used the TMP button to wake them up, as well as removing and putting back the battery, but I only managed to fully “interview” a single one. I’m not sure if it just a coincidence, but it happens to be the one closer to my RPI that has the USB zwave stick connected.
Based on what @mrMagoo mentioned, I’m not sure if I am supposed to remove them from the zwave mesh and add them again to make them work. If that is the case, I’ll face another problem, because some of these devices are not accessed directly, but by at least one hop through powered devices. If I remember correctly, devices cannot be added to a zwave network indirectly, they must be near the zwave stick and for adding devices securely I cannot use the zwave stick in standalone mode.
And by the way, there is another drawback regarding the battery device that I was able to interview: it does not update when the door is opened or closed, which is a major bummer. It is not a matter of lack of communication, because the device is reporting temperature periodically, but the “Entrance Door Sensor: Access Control - Window/door is open” sensor is always “closed”.
You don’t need to need to reinclude. Just need to wake them up. They can be more than 1 hop for inclusion as well. I include everything (including the model numbers you listed) from my desk which is 1 hop from my controller. For that specific device, when I switched to zwave_js, I pulled it off the wall. Pressed the botton on the bottom, and glued it back in place.
1 Like
I just upgraded from the old Zwave integration and after going from beta0 to beta3 everything is working fine apart from a small problem with my thermostats.
I have one Z-TRM3 and one Z-TRM2FX from Heatit. Both of them come up and I get all the sensors and can change the setpoint. But they have 2(3) different temperature sensors (Air, Floor, External), and I’m using the floor-sensor for both of them.
But the climate devices show the air temperature, not the floor temperature for both thermostats. See image, the top one shows the external temp, and the bottom one shows the air temp.
While this is mostly a cosmetic problem at the moment, I would really like the climate device to report the correct temperature.
Based on what @mrMagoo mentioned, I’m not sure if I am supposed to remove them from the zwave mesh and add them again to make them work.
Ah, but that’s NOT what I said. 
You do not need to exclude them !
However, some devices (like my BRK / First Alert Smoke Alarms and Philio 4-in-1 sensors) will never properly wake up and accept an interview unless you force them into inclusion mode.
So step one is to try and wake them up “normally”, tap the button, pull/re-insert batteries or whatever method there might be, and if that fails, I’d try to re-include them and ONLY from the device standpoint, do NOT click include in ZWaveJS, in ZWaveJS(MQTT) you should use “Re-Interview Node”.
2 Likes
On my first attempt at setting up zwavejs on my production stick (26 nodes) I’m kind of not impressed so far.
Right now every node but one (that I haven’t had a chance to wake up yet) has been successfully interviewed and is showing up in the zwavejs2mqtt control panel.
But so far after I add the integration I only have two nodes showing up in HA - the controller (node 1) and the first node after it in sequence (node 3).
I did a json dump and it seems as all of the nodes are there (there’s over 300,000 characters so I’m not scrolling thru all of that) but I definitely saw node 4 & node 5 in the list of nodes even tho they don’t show up in my list of devices.
And I have zero entities now too. I would expect that there should be at least one “switch” entity from my dry-contact relay device.
Is there some “special sauce” that I need to get the rest of the devices/entities to show up?
I’ve restarted HA several times.
The test zwavejs2mqtt container had been working well using MQTT but I switched it to using only WS and now it is no longer exposing any entities to HA either even tho it had already had a working switch via MQTT.
I’m not really sure where to go from here.
EDIT:
Nevermind…
It seems updating to the latest docker image seems to have solved it.
As I am not sure who is answering whom: Has anybody fully working Fibaro Roller Shutter 3 modules (incl. full up / down, go to certain position, tilt slats, report back correct position after being moved by wall switch)?
Some background: This device never fully worked in OZW 1.4 - Fibaro made it constantly report the position during movement to make it look pretty in the Fibaro Home Center UI which OZW 1.4 can’t interpret correctly (and also hammers the network…) - so you have to manually refresh the cover entity after movement. Also tilt slats never worked.
roller shutter dowsnt work my blindsa are closed till 3 weeks, i hope with the update on wednesday it will work
My Thermostat control functions stopped working when I updated recently to Z-Wave JS 0.1.10, .07 worked fine. Not sure what happened, the other entities(temp, battery, battery level) were reporting in normally just the actual control entity stopped working. I’ll likely hold out before updating to .10. , hope this issue is fixed in future updates.
Anyone have any insight into if some kind of event or status will ever be implemented that lets us know ZWave status? Network ready, offline, other? I can monitor container status for offline, but would be good to get a network ready notification if nothing else like we used to have.
1 Like
I agree.
It’s not quite as big of a deal as it was with the old zwave integration since HA and zwave are now decoupled but it would still be good to have some kind of indication if there was an issue with the zwavejs server.
It seems like the information is (mostly) there. There is no way that I’m aware of to access it in sensor though.
I wonder if that generates an event in HA?
Tho I’m not sure if that’s possible since HA disconnects from the js server if it goes down until you restart HA…at least that’s what I’ve experienced.
I’ll have to check.
EDIT:
it doesn’t appear that it does.
but I found this:
https://zwave-js.github.io/zwavejs2mqtt/#/guide/healthcheck
it isn’t a passive check tho so you’ll have to actively run it from inside HA so that’s not a good solution.
But I just checked it from the host CLI and it works there.
Ya never did see any events come through other than scenes and things like that. Good to know there are options at least. Hopefully we’ll get a built in check eventually. Good find btw.
1 Like
I have the Fibaro Roller Shutter 3 working in Z-Wave JS, but I don’t use tilt. The reporting of the position works fine (other than in OZW 1.4 as you mentioned, where I also used a workaround).
Sorry if this is a stupid question, but is there any place where I can see the version history and release notes of the Zwavejs2mqtt project? I use a docker image on a seperate server and I can’t see anywhere what the latest version is and what the changes are. This is really annoying. As much as I love fast development, it should not come at the cost of poor documentation.
Forget my post. I found the version history here: