My migration from Vera, or what I did on my holidays
-
Spoke too soon, but HA Bridge is finally back where it was. No idea why I was having so many issues, but I suspect there were overall Vera issues which shouldn't be a problem but....
Anway.
To get Z-wave running on Debian I followed the Z-wave manual and then @rafale77 's excellent tutorial on Debian install. It's up running and hooked into Openluup but tomorrow and the weekend are busy so I doubt I'll get much progress.
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.
-
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