SmartHome Community

CatmanV2

Sorry, just had to...

C

CatmanV2

Well, if I see further, it's because I stand of the shoulders of giants. I've got where I got because of the experts here. I started about 15 years ago with some really basic X10 stuff. When we moved in 2011 for some reason it simply would not work in the new house, so z-wave was the thing. Vera lite then Vera Plus.

I'm a child of the 70s. I want the car on the drive to be KITT and my lounge a cross between the bridge of the enterprise and the Lars farm on Tattoine.

Not there yet, but with about 250 devices (virtual and real) things are fun (when they work!)

The absolute killer app for me is Alexa bi directional speech. To the extent that I've walked into hotel rooms and said 'Alexa turn the lights on....'
I'm within a spit of never buying another control and doing everything via Alexa and Reactor (had to drop that in)

So that's pretty much me.

C

CatmanV2

Perhaps another thing to point out is that WiFi<> Internet and there is absolutely no technical reason you cannot have a WiFi network simply because you have no internet access

C

CatmanV2

Well here we go. A slow, considered migration from Vera to something (I hope) more reliable.
Hopefully we'll end up with a decent documented process for people as right now I'm still not quite clear
Starting point:
I have a 'mature' Mios set up running on an extrooted Vera Plus with roughly 100 devices, both physical and virtual
Integration with Alexa both voice control and TTS
iPhones for Geolocation
Volumio devices for music playing around the house.
I have no user defined scenes, all automation is run from Reactor.

My impetus is final dissatisfaction with the quality of UI7 software delivery and operational rigour (for full disclosure I am a senior IT Operations leader with circa 20 years experience delivering properly stable systems, so I probably have un-realistic expectations )

So initial steps:

Raspberry Pi 3 B+ (I think this is my 5, and 6th Pi in total. I may have a problem)
Raspbian
OpenLuup
Verabridge

That I think is stage 1

C

CatmanV2

Just to close this off, I managed to get a Harmony Elite and Hub from ebay. Lightly used at a reasonable price.
God knows why they are pulling out of the market. First impressions is it's an ace bit of gear. Didn't realise quite what the hub could do and am thinking of getting another to replace my Broadlink in the cinema.

Thanks, all

C

CatmanV2

OK so time for an update. This has kind of drifted off the 'Here's how you do it'

Most of getting Openluup, HA Bridge, AltUI, and getting Z-way up and runningwas pretty trivial (all things considered)

The migration from Vera to Z-way, was not as simple as I'd have hoped. Pretty much 2 days of fettling.

Couple of gotchas:

My restore to the UZB dongle took a couple of shots. It took quite a long time as well.
Migration to Z-way per se was pretty simple
However, Z-way requires a totally different way of thinking. Pretty much every service creates an individual device. If you're not ready for this you can get in a hell of a mess trying to name stuff. I still have a few odd devices that I'm not quite sure what they are. I suspect tamper switches!
Some devices are not what you think. Sirens. In fact these are shown as switches. Makes total sense when you think about it, but doesn't look great on the interface.
The rooms were not migrated. So although all my rooms already existed in AltUI / Opeluup (from Vera) new devices all appeared in a ZWay room. In retrospect this could be because I already had rooms named, and they had different UIDs
Reactor is still fantastic
There are a couple of devices that aren't supported in Openluup / AltUI. Meh might be worth checking in advance.

Finally a huge thankyou to @akbooer @rafale77 @therealdb Partrick (is he here? If not can someone ping him the other place) and the rest of you that have made this work.

This is so much faster, more sensible, reactive, responsive and everything else. Now I just want to do more

Respect

Chris

CatmanV2

@therealdb well we got this place....

C

CatmanV2

@librasun said in Finally gave up on my Ezlo Plus:

Sound familiar?

Never heard that!

C

CatmanV2

https://www.keene.co.uk/keene-ir-anywhere-ir-over-ip-modules-pair.html

Keene are great for all this kind of stuff.

C

CatmanV2

After much (un-necessary) faffing on Debian 10 I got MSR up and running in about 10 minutes flat this morning, on the same box as AltUI

As a warning, expect lots of stupid questions.

C

CatmanV2

@a-lurker said in ChatGPT - finally I can now retyre in piece and quite, knowing everting is in goof hands.:

It:

CatmanV2 is a member of the Internet of Things (IOT) forum, an online discussion platform for professionals and enthusiasts in the IOT industry. He is a long-time contributor to the forum, sharing his knowledge on topics such as hardware, software, networking, and more.

Actually, I'm just a prototype

C

CatmanV2

This may explain it....

C

CatmanV2

@therealdb Yes. Sorry it's sometimes tricky for me to know / recall which bits of my system 'belong' to whom!

Cheers as ever

C

CatmanV2

Ahh, just pulled the latest script from Git and all is fixed.

Apologies!

C

CatmanV2

Thanks. You mean delete

alexa_remote_control.sh

?
There's a new version in Git?

Odd announcements to 'Everywhere' get stuck with the volume of the announcement, but calls to individual devices do not.

No panic from my side (I've managed this long)

I think it's only come to light since I fixed the Everywhere group.

C

CatmanV2

Hardly a big deal, and likely user error. Bare metal install on Debian Bullseye

Observed behaviour:
TTS announcements are made with the correct volume. So a message to group 'Everywhere' with Volume 40 is announced. Asking an individual echo device to state its volume after the announcement gets the response 'This device is at volume 4'
So far so good.

Using the:

x_vera_svc_bochicchio_com_VeraAlexa1.SetVolume

In an MSR reaction appears to have no impact when either applied to the group 'Everywhere' or a specific device.

So executing this reaction:

Is acknowledged by the device (with a 'beep') and shows the Lua Log below:

2023-01-31 09:21:45.778   openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x5572399831f8
2023-01-31 09:21:45.779   openLuup.server:: GET /data_request?GroupZones=Office&DesiredVolume=10&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action=SetVolume&output_format=json&_r=1675156905777 HTTP/1.1 tcp{client}: 0x5572399831f8
2023-01-31 09:21:45.780   luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.SetVolume 
2023-01-31 09:21:51.670   luup.variable_set:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.LatestResponse was: sending cmd:speak:<s>Volume Set</s><break time="0s" /> to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS cu... now: sending cmd:vol:10 to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS customerid:A1CVTZEBJIUFJI #hooks:0
2023-01-31 09:21:51.671   openLuup.server:: request completed (35 bytes, 1 chunks, 5891 ms) tcp{client}: 0x5572399831f8
2023-01-31 09:21:51.683   openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572399831f8
2023-01-31 09:21:51.685   openLuup.server:: request completed (930 bytes, 1 chunks, 42818 ms) tcp{client}: 0x557239726708
2023-01-31 09:21:51.687   openLuup.server:: request completed (930 bytes, 1 chunks, 42548 ms) tcp{client}: 0x5572392c0fd8
2023-01-31 09:21:51.688   openLuup.server:: request completed (930 bytes, 1 chunks, 12501 ms) tcp{client}: 0x5572392c7f88
2023-01-31 09:21:51.692   openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572392c7f88
2023-01-31 09:21:51.704   openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557239be10b8
2023-01-31 09:21:51.704   openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66666322&MinimumDelay=50&output_format=json&_r=1675156911703 HTTP/1.1 tcp{client}: 0x557239be10b8
2023-01-31 09:21:51.905   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675022474387 HTTP/1.1 tcp{client}: 0x5572392c0fd8
2023-01-31 09:21:53.042   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675079237873 HTTP/1.1 tcp{client}: 0x557239726708

However direct interrogation of the device reveals the volume has not changed.

I assume I'm doing something wrong or not understanding how this is meant to work?

One other observation is that messages announce to the 'Everywhere' group appear to make the volume 'stick' where as messages to an individual device appear to revert to the previous volume setting.
My expectation would be analagous to a radio i.e. the volume stays as it was last set, but happy to be corrected.

TIA!

C

CatmanV2

Done. Many of your questions are rather equivocal though. What I do and what I would do may be totally different

C

CatmanV2

OK thanks. Much hacking it turns out it was unhappy with the cookie (for no clear reason, and despite multiple replacements)
Went old skool, changed password, new browser, new cookie and we're good.

Many thanks!

C

CatmanV2

@therealdb No and I was about to ask that

C

CatmanV2

@therealdb Ta

catman@openluup:~/Notvera/VeraAlexa$ ./alexa_remote_control.sh -d 'Everywhere' -e speak:'This is a test'
cookie does not exist. logging in ...
^C

Which is odd:

catman@openluup:~/Notvera/VeraAlexa$ ls -ltra
total 840
-rw-r--r--  1 root root   7249 Jun 25  2020 .alexa.devicelist.txt.old
-rwxr-xr-x  1 root root  49902 May 29  2021 alexa_remote_control.sh.old
-rwxr-xr-x  1 root root  33826 May 29  2021 alexa_remote_control_plain.sh.old
-rwxr-xr-x  1 root root  34367 May 29  2021 alexa_remote_control_plain.sh
-rwxrwxrwx  1 root root  47437 May 29  2021 alexa_remote_control.sh
-rw-r--r--  1 root root    216 Dec 14  2021 TestLua
-rw-r--r--  1 root root   1413 Mar 25  2022 cookies.txt
drwxr-xr-x 15 root root  12288 Nov 17 19:04 ..
-rw-r--r--  1 root root 147036 Jan 18 17:44 .alexa.login
drwxr-xr-x  2 root root   4096 Jan 18 17:45 .
-rw-r--r--  1 root root  12274 Jan 18 17:45 .alexa.devicelist.json
-rw-r--r--  1 root root 455307 Jan 18 17:49 .alexa.cookie
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.de3b4a21ca844817bc180e826e636425
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.G090U50991550NLS
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.G090U50991720NTM
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.G090XG1215150M64
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.90F00818720507LD
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.G090U5099156024K
-rw-r--r--  1 root root      9 Jan 20 12:14 .alexa.volume.G090LF1181220107
-rw-r--r--  1 root root   1366 Jan 20 12:14 .alexa.cmd

C

Home Assistant add-on

Renaming Global Expressions possible?

How to reset kwh

ChatGPT - finally I can now retyre in piece and quite, knowing everting is in goof hands.

Super newbie here. Need help with lots of stuff

Setting Aeotec Siren 6 volume and duration not working

MSR controller status panel

Short survey

Way to copy or export Alerts?

Alexa TTS volume does not update as expected

Include Entity by Name in Dynamic Group Controller

Need help in finding the right smart switch for my kitchen lights

[Solved] MSR actions aren't running anymore-- can't find what's broken

Reactor (Multi-System/Multi-Hub) Announcements

My MQTTController templates contribution

Sonoff zbmini-l and philips hue

Ezlo Controller - Error Incompatible serialization data - api cloud Timeout

MQTT log levels & log rotation

CatmanV2

@CatmanV2

Best posts made by CatmanV2

Latest posts made by CatmanV2