Thanks! Do you see a service to set slat position for the device?
No. In the entity window there are only the buttons for up, down and stop as well as a slider for the position. No seperate slider for the slat position.
The cover entity generally allows for tilt position:
If it’s not too much trouble (and if you even have blinds) it would be great if you could check using the developer tools if you can turn the blinds to a certain position:
- service: cover.set_cover_tilt_position
target:
entity_id: cover.demo
data:
tilt_position: 50
I do not have a spare one here - will probably have to buy one to thoroughly test before I do the transition… 
I switched to Z-Wave JS a few days ago and must say I have had almost no issues.
I do have some troubles getting my Fibaro FGRGBW-442 to work.
As far as I can see the Z-Wave JS to MQTT (version 0.5.0) sees the device correctly.
However I think HA integration Z-Wave JS is missing entities.
I am able to get the light on and off and change colors by manually playing with the settings in Z-Wave JS to MQTT, but in HA there is not much to play with.
In the old situation I had 6 switches that I could use to control the led strip. One of them had the ColorWheel…
Any idea how to get HA integration to see the same items as the z-wave JS to MQTT add-on ?
Problem is that I don’t have blinds attached to the roller shutter but just ordinary shutters. So no way to test if they can tilt. 
Af the Moment i have installed the zwavejs addon but now i want to use the zwavejstomqqt too, anybody knows How to connect the zwavejstomqqt to zwavejs without reinstall zwavejs?
You can’t use both at the same time.
Once zwavejs is stopped and zwavejs2mqtt is running just add another zwavejs integration pointing to th new server.
I’m using ZwaveJS2MQTT and upgraded to 0.5.0 the other day. I’ve noticed a couple of instances of Z-wave lights/switches getting “out of sync” which I haven’t seen before. In the first case, a light wired to a GE/Jasco dimmer was on, but showing off in the UI. I couldn’t shut it off from the interface. In the other case, a bunch of lights wired to an Inovelli Red Series on/off switch was off, but showing on in the UI.
In both cases, everything was resolved once I went to the physical dimmer/switch and cycled it.
Everything else is going fine, and I’m excited to see changes in beta for Inovelli LED notifications.
This solution works for me
Thank you
In zwavejstomqqt i See now all my nodes and they with battery i have to Wake up, but IT doesnt work for All Devices, is There any solution?
Yes, this is a known issue. Since my switch over to z-wave JS, this is the only device I cannot control. I think we just have to be patient, but the wife is getting a little pissy about it.
Which devices aren’t working?
And what do you mean by “not working”?
the wake up doesnt work.
The wake up on the device is working, is saw it with a led on the device, but zwavejstomqqt dont ad the information to the node. i only see in zwavejs a blank node with unknown status.
the wake up dont work for all my battery devices (5 motion sensor from fibaro, 4 door window sensor from fibaro 2 door window sensor from aeotec and 1 wallmote quad from aeotec)
my wife too^^
did you try selecting the node in the zwavejs2mqtt control panel and initiating a “re-interview node” on that node when you try to wake it up?
I can’t remember which way had more success for me - waking it up then doing the interview or initiating the interview then waking it up. try it one way and if it doesn’t work then reverse the order.
if the wake up is successful you will see the status of the node change immediately to “awake” in the control panel of zwjs2m. If it goes back to sleep then keep trying to wake it up until you see “complete” for that node.
1 Like
Alright, thanks anyway for the feedback! Take care!
Hello !
I use ZwaveJS2MQTT with MQTT communication (using webockets I had disconnexions).
I have a weird behaviour with one Fibaro Roller Shutter 3 (FGR-223). I have 17 of them, all with the same firmware. Everything works fine except for this one. For this specific FGR-223 I don’t ever receive any position feedback, either if the shutter is open/closed manually or from Home Assistant.
What is stranger is : using ZwaveJS2MQTT, when i force a “Refresh Values” on this device, the correct position is immediately displayed in Home Assistant. Does it mean that ZwaveJS2MQTT has the actuel value and does not transmit it ? Or that the module does not transmit the actual position to ZwaveJS2MQTT ?
I did not check logs or debug yet. I juste confirmed suing MQTT Explorer that MQTT broker did not received the updated position, so the problem is before (either device or ZwaveJS2MQTT).
Behaviour is exactly the same than with old OpenZWave 1.4 integration, known issue with theses FGR-223.
Note : I have tried to exclude it and then include it back. No change.
Did you update to the latest ZwaveJS2MQTT? If yes, you have to use the HA beta because the latest ZwaveJS2MQTT is only compatible with the beta. Or you can wait until wednesday for the release.
1 Like
Is that for the add-on or standalone container or both?
I pretty sure I’m on the latest standalone container (updated two days ago) and not on the beta and mine seems to work with the little bit of testing I’ve done so far
add-on and stand alone container
To clarify, some devices won’t work. Specific dimmer types. I can’t remember which.