My migration from Vera, or what I did on my holidays
-
It looks like tomorrow is the day....
C
-
Hmmm
So how long should a restore take? Mine seems to be stuck at 91% and none of my actual devices are visible in the dashboard. Z-wave network is not starting.
Maybe I'm being too impatient
C
-
Hmm total nightmare. Never gets past restoring to 91%. Won't start Z-wave. Wont' show my devices. dev/ttyACM0 keeps being replaced by tty/ACM1
Might just burn it and start from scratch
C
-
OK that's looking better after a second restore. Lots of devices. All with dumb arse names, waiting for wakeup in many cases. Good
C
-
OK I think that's the important stuff working apart from a Fibaro dimmer in the kitchen. I can't get it beyond any kind of 85% on the interview.
Similarly my SRT321 in the hall claims it's a switch with is a little irritating
Any thoughts?
C
-
Have you other Fibaros which have interviewed OK?
-
Yes, although no other Fibaro dimmers. Only modules
C
-
In other news none of my devices turned up int the right rooms. I'm having some trouble getting some of them to show up in AltUI
Is there a way to force a refresh, other than the obvious reload Luup and hard refresh?
Cheers
C
-
OK beginning to get some kind of grip here.
The main thermostat has been created with D_ComboDevice1.xml which ain't gonna work
Does anyone have copies or know where I can get the right xml and json files at all? There doesn't appear to be anything obviously suitable in my files folder, but if anyone knows what they should be, that would be lovely.
C
-
don't worry about the interview percentage. That doesn't matter at all. I have devices at 50% and they all work fine. This is due to device makers using very weird implementations declaring command classes on their list which the device does not support so the device won't answer. Fibaro and aeotec are notorious for doing that which is why I avoid them as much as possible. What matters is not the percentage but what command classes are being interviewed.
It seems you are doing a lot of things at the same time. Let's take it step by step. Is your restore on the vera hanging at 85%?Before starting on the bridge, I would recommend to get familiar with the z-way interface and get all your devices setup with names and rooms there. They will be imported by the bridge.
-
Sorry, chap
Way ahead of that. I have about 90% of my devices working.
Nearly all are in AltUI A-OK
Ones I have problems with, in order of importance:
SRT321 thermostat in the hall:
This has AltUI attributes of D_ComboDevice1.xml and json. Can be seen in elements of Z-way but cannot be controlledFibaro dimmer 2 in the kitchen:
This has AltUI attributes of D_PowerMeter1.xml and json. Not visible in the elements of Z-wayThanks!
C
-
The combodevice is normal. It is what the z-way bridge uses for... combo devices. The SRT from what I can see seems to be declared as a switch with a temperature sensor, so you should see child devices spawn from that combo device. For us to be helpful, we would need to know what command classes are showing in z-way which are not ported by the bridge but the first problem is to get them interviewed and show in the z-way home automation UI.
The dimmer 2, if it has more than one functionality, likely also shows up as a combo device with child devices. Apparently it already has ported the power meter but not the dimmer command class? This is not like the vera... you don't need to go modify the xml and json and neither will it work. Each of these corresponds to an actual zwave command class and doesn't go through some vera guess work, often failing and spawning some random stuff which is why it doesn't have the vera's device specific support problems.
-
Ahhhh OK. That gives me some interesting avenues to explore. I shall report back (undoubtedly with more questions!)
C
-
OK looking at the lights Fibaro dimmer it hasn't appeared to create any devices in Z-way that are visible other than in the advanced view.
Nothing in elements. The advanced view gives me access to all the parameters but nothing I can control it with, if that makes sense?
Cheers
C
-
SRT321 now accepts setpoint so that's great. Just curious how I would control it via AltUI?
Cheers
C
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
OK looking at the lights Fibaro dimmer it hasn't appeared to create any devices in Z-way that are visible other than in the advanced view.
Nothing in elements. The advanced view gives me access to all the parameters but nothing I can control it with, if that makes sense?
yep, that's where the problem lies and is why we have been talking about switching the API the bridge is talking to. The automation UI is really more of a demonstrator for what the lower API and library can do. It has some gaps unlike the lower level zwave API and even the JS API. I also have devices like these which we had to workaround by sending commands directly to the lower level API. Please provide the details: what command class that device has on the expert UI and which ones are missing. It is possible that a forced interview or a simple version edit can fix it too.
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
SRT321 now accepts setpoint so that's great. Just curious how I would control it via AltUI?
Cheers
C
This is a bridge problem then, because none of us had this device before. A screenshot of the cgi screen showing the details of this device (go to the zway bridge and click on configure child) could reveal what this device is publishing and we can make the bridge support it.
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
OK looking at the lights Fibaro dimmer it hasn't appeared to create any devices in Z-way that are visible other than in the advanced view.
I haven't tried a simple Fibaro dimmer on ZWay, but I certainly have have tested one of their RGBW LED controllers, which presents as no less than SIX dimming devices (one each for RGBW, one group, and one master.) These all work as expected, so I have high hopes for the basic Fibaro dimmer.
I think the interview problem is the one to fix first??
I do have Fibaro dimmers on my Vera system, and I think I have a spare device somewhere, so I'll try and find it and add it to ZWay.
-
I have a number of older Fibaro devices on my ZWay and most of them work as they should. As noted by Rafale77 above Fibaro are a bit of a pain, and I will try avoiding buying more.
I do not have any Dimmer 2 devices but a three older Dimmer 1 devices and they work as they should. I also have a single and a double switch (also the older models) that also work. I tried to include another double switch but I did not get it to report status properly. When checking the FW was older on that one that the one that works. I re-included it to my Vera Plus for the time being.
Unfortunately Fibaro does only allow FW update on their own controller, so I will need to replace it with something else.I also have two RGBW devices and an old Fibaro door sensor of the old type that all work the way they should. The last one is a Universal Sensor that works despite not having finished the interview.
In all they work better that on the Vera (baring one) and inclusion of e.g. the door sensor that was a proper pain on Vera was much easier on Zway.
There are some threads on the zwave-me forum on Fibaro devices, perhaps there could some clues on the Dimmer2 there.//ArcherS
-
CatmanV2replied to rafale77 on Jun 30, 2020, 5:31 PM last edited by CatmanV2 Jun 30, 2020, 1:33 PM
@rafale77 said in My migration from Vera, or what I did on my holidays:
. Please provide the details: what command class that device has on the expert UI and which ones are missing. It is possible that a forced interview or a simple version edit can fix it too.Like this?
Association group and security are the ones that are failing interview.
This is a bridge problem then, because none of us had this device before. A screenshot of the cgi screen showing the details of this device (go to the zway bridge and click on configure child) could reveal what this device is publishing and we can make the bridge support it.
Hmmm I get a 404 on the zway_cgi.lua...
file not found: cgi/zway_cgi.lua
C
-
ok we are getting somewhere. failing security is bad. You probably skept the whole security part? (extracting security key from the vera and insert it in zwave). Then yeah because your device was added to the vera with security, no other controller without the key will be able to control it... It is by design.
As for the cgi, you just need to install the file in the cgi folder.PS: @akbooer is right. I was in no way suggesting that the fibaro won't work with zway. Just that it is normal if interview may not complete.
68/105
