My migration from Vera, or what I did on my holidays
-
OK this is a significant issue.
Guess who installed 32bit Debian......
Any thoughts on a Z-way server binary?
C
-
Hmm so this looks like a no win scenario. Torch and start again
C
-
So plan to get me back. It shouldn't be too hard but I'll probably leave it for today because of the Alexa / HA bridge stuff will stop.
Install 64bit Debian
Install Lua
Install jq (for Alexa TTS)
Install default-jdk and jre
Install HA-bridgeRestore the copies of the service definitions I created
Enable them in systemctlRestore the Open-luup backup
Restore the HAbridge backup.Hope?
@akbooer @rafale77 @therealdb does this sound like a good test?
Regards
Chris
-
Yeah sorry I never thought about 32bit installation... have not done anything on 32bit OS except for the vera for ages.
-
The openLuup transfer should be straightforward. I’d save the whole of the cmh-ludl directory tree with all your device files, etc. There’s nothing that’s 32/64 bit dependant.
-
I pretty much have
Just overwrite the lot on the new install, yes?
Thanks!
C
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
Just overwrite the lot on the new install, yes?
Yes.
-
Well that was fun
Debian re-install. Restore of Openluup instant.
Restore of HA Bridge not so much. Or in fact at all. But there we are . Not too much more to do
C
-
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
-
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.
58/105
