I’m struggling to get the Duewi (or Popp) remote to work. I neither can’t program the szene buttons or assign lights to normal buttons from within vera. I can associate the controller as secondary but nothing more.
Unforntunately this is an European product and Z-Wave is over here a little bit exotic. I know that some Danes are trying to make the remote work but since I don’t understand Danish I don’t know much more.
Any help appreciated - overall Vera looks fine and I’m looking forward to getting know it better!
It’s nice that something might happen … but this is not “just” the Popp/Düwi controller. It’s all portable controllers that I have come across. And then I think it’s a bit funny that the focus is on LUA - because we all need to script our vera… remotes are just for fun
Luckily I have an iPhone - but I’m not gonna buy that for my whole family so they can control the house.
Regarding Lua vs. Duwi… The Lua module gives you Infrared control on a/v devices, plus Insteon (big in the US) and the ability to add KNX/EIB in Europe and Zigbee smart meters. So there’s a lot more people after us to finish the Lua module than the Duwi remote. I got the Duwi remote partially working, and sent an email to one of Duwi’s engineers to figure out the remaining issue and am waiting for his resposne.
According to Duwi’s engineers, their remotes do not support the Z-Wave scene controller or scene transfer commands. So they’re not technically Z-Wave handheld remotes, because those commands are mandatory for a remote since that’s the only way to transfer scenes into them. The Duwi uses their own proprietary closed system, I was told, where you have to build the scenes within the remote. So, you can include the remote into Vera’s Z-Wave network, so the Duwi can see and talk to all the Z-Wave devices, but you can’t create scenes in Vera and transfer them to the Duwi, or use the Duwi to trigger scenes in Vera, because it doesn’t support Z-Wave scenes.
this is my first post and I did get my vera yesterday. This Düwi-Remote is the first problem I ran into after a few minutes.
If your statement is the last on this, I think I have to live with it. Unfortunately this remote is the only remote that is available at the moment in Germany. (I think) and it’s very sad, that it cannot be used properly.
What troubles me, are the following points:
How should I connect that remote to vera to get the most of it.
The remote has a transfer mode to synchronize, I find it odd, that this isn’t supposed to work.
When I switch a node with the remote, vera doesn’t show the proper state of the lamp module. I have to poll the node manually to get it updated.
If a manufacurer of Z-Wave is “allowed” to do what he wants, e.g. leave mandatory functions unimplemented, how is that mix of different manufacturers ever going to work reliably? Sad…
I have to say, the first erperience with vera is not at all as straight forward, as I expected…
That’s what I have now.
But my understanding of a proper z-wave net is that when you use any controller to switch something on, other cotrollers should be aware of it. What I see here, is that vera never realizes the switching I do with the düwi remote. I have to poll the network to see the changes.
So in my understanding there seems to be something wrong, doesn’t it?
AFAIK, you are wrong - that’s exactly how Z-Wave network works. That’s why Vera has the concept of polling - it has to poll to get the idea what state each device is in.
Different manufacturers implement different concepts of preserving/sharing states between a device and its controller. For example, Leviton uses half-proprietary HAIL mechanism. But the thing is that a device would send back a HAIL message with it’s new state only to one controller - either to the one associated or the one changing its state.
So, if you have an in-wall controller which is associated with a light switch and shows its on/off state, toggling the switch or controlling it from this in-wall controller will update the controller’s state immediately. While Vera will not be notified of the state change and need to poll the device. Now, when switching the light switch from Vera will send the state update notification back to Vera and the in-wall controller will not be updated.
AFAIU, Z-Wave has this limitation to avoid the network flood of notifications in large networks, every time you hit the light switch. On the other hand, INSTEON allows you to associate one device with multiple controllers and it will send the state change notification to all the associated controllers every time the state changes, regardless by which means it is changed (i.e. locally of by one of the controllers).
I can understand that with battery operated devices like sensors, so the would only report when they are “asked”. But with wall switches and switching devices I find it hard to believe that a controller would be forced to poll every device. And in what way would a controller then be different from a simple wall switch?
That makes sense. On the other hand it seems to me, that letting a device be controlled by different controllers is common. I could associate my devices with the vera and the düwi controller at the same time. The düwi controller instantly reflects the state of a switch, even when vera has changed it’s state. It seems odd to me, that it doesn’t work the other way arround. Why would I have to connect the düwi to the vera as secondary controller, if they were working independently?
So all in all, I am not convinced. that a controller normally has to poll every node be be aware of its state. I have to do some digging on this.