My migration from Vera, or what I did on my holidays
-
CatmanV2replied to therealdb on Jun 23, 2020, 6:17 AM last edited by CatmanV2 Jun 23, 2020, 2:40 AM
@therealdb thanks for the reminder. So that's done (well Use announcement set to 1)
I've configured all my Echos to have announcements enabled, but how do I actually send one? If I use Reactor>Device Action>Say> with group zone ALL they are still unsynced. If I use group zone Everywhere (the name of my group) I get no sound at all.
Cheers!
C
-
Look at the logs. The group name is the way to go. ALL will still cycle.
-
@therealdb said in My migration from Vera, or what I did on my holidays:
Look at the logs. The group name is the way to go. ALL will still cycle.
Logs don't log stupidity
Was firstly using the Vera instance, then trying to set announcements on the Vera instance. Setting it on the Openluup instance and using that worked first time
C
-
@CatmanV2 said in My migration from Vera, or what I did on my holidays:
Logs don't log stupidity
...we could add it as a feature, but you’d have to sign up to be a beta tester.
-
One thing I could test with aplomb
Cheers
C
-
Amusingly and with full reference to this:
I've not had a Luup reload since Monday lunchtime. Odd since all my automation is still on the Vera. I have, however, killed all the Vera / Alex skill availability
C
-
@CatmanV2 not suprising at all. If you remove all the load from the controller, it will be stable. If you don't have too many (let's say 60+) devices, Zwave will be stable enough. When you have a lot of devices and/or some not-really-supported-but-works-with-Vera (TM) devices, the Zwave network stability can dramatically decrease.
-
But I haven't reduced the load, is my point. All my devices, all my automation apart from stuff that I use Alexa for, is still on the Plus. In fact, the load should be higher since it's getting polled by the Vera Bridge.....
The only real difference so far is that I use HA bridge running on the new Openluup box to do voice control. And that's hilarious. Even running through UI7 by doing a get to the Openluup box which which then goes through Verabridge, 90% of the time the switch has changed before Alexa has managed to say 'OK'
C
-
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
49/105
