…had to happen.

@CatmanV2 said in Home Assistant Voice:

Cheers! I shall try and make some time
(Is it just me that hates having to watch videos? Can't we just have instructions written down? )

Not just you! Such a lot of very poor narration and not so easy to refer back to! A modern disease.

I didn’t go the HA route, but have voice control through Apple HomeKit and Siri. Works OK, but don’t use it much.

What’s the difficulty? Does your switch wiring have a neutral? What country are you in?

Impressive.. great when it all works too!

I’ve been very happy since I moved everything I could to Synology.

A
K

Yes, if it’s openLuup, then I was going to suggest that… rather depends on what you were trying to do.

Bizarre! … but good catch.

I’m a Siri user, myself. How do you link Alexa to openLuup? My link to Siri is via HomeKit (of course) for Hue and Shelly devices.

@a-lurker said in openLuup email server:

To keep things so they are more likely to work, it's suggested the email address should be totally case insensitive regardless.

Yes. I see from the ource code comments tht eraly-on I removed address wrapping to lower case. It's an easy change, but I'm going to find out why I did that in the first place, before reverting.

@a-lurker said in openLuup email server:

Is it your preference to leave the saved files in the raw mode or would you consider translating the base64 text in the openLuup code base?

Don't see why not. Again, I need to dig in to see why that isn't working out of the box. There's plenty Base64 decoding going on within the server anyway.

@a-lurker said in openLuup email server:

On a side note, does the reception of an email by openLuup generate some sort of trigger that can be watched.

Your best bet would surely be to register a callback handler to listen for messages on a specific address?

I have another big project ongoing with some sort of a deadline at the start of December, so I'll need to leave things until then before I can get back to this code.

Thanks again for your documentation efforts. I did say I would provide a link from the openLuup app... perhaps in the footer, like there is for the forum?

You have been doing your homework!

I need to remind myself of what I did way back when before being able to reply sensibly.

But thanks for the excellent analysis.

Not sure if your controller handles WiFi controlled devices?

As it says, this will need a Zwave hub to work.

Not quite clear on what you’d need, but have you looked at the Shelly range of products for remote switching?

I should have thought so.

Can you post the JSON for the scene from the console scene page?

Go to the AltUI Attibutes page and enter 1 into the disabled attribute box.

Restart Lua.

Everything will still be there in case you want to reactivate it.

You’ll note from your first attached image that there are three types of trigger recognised by openLuup:

1. openLuup Variable watches
2. AltUI variable watches
3. Luup UPnP

#3, as noted in that image, are all ignored by openLuup. This system was hopelessly flawed, which prompted @amg0 to create variable watches (#2).

When I removed all AltUI dependencies from openLuup (my operational system doesn’t even have AltUI installed) I needed a replacement for those variable watches, hence #1.

The openLuup watches are recognised by AltUI as a form of #3, because the Vera-compatible data structures are used, in a very limited way, to implement them, and save them in the JSON file.

So with AltUI installed, both will work (if enabled.)

Hi there.

'Best', of course, is subjective. What are your needs/wants really?

Also, what type of IT infrastructure do you have, or are you used to? Apple, PC, Linux, ...?

Lots of choice, to be sure.

Yes.

An alternative is to create the module table at the start, and define the functions directly as module components…

local _M = {}

function _M.myfunction(…)
  — whatever
end

function _M.anotherFunction(…)
  — whatever
end

return _M

The module call is, for good technical reasons, set to a no-op in openLuup.

It’s also an outmoded/deprecated pattern in newer Lua versions.

You should, instead, ensure that the module itself ends with a return statement, with a table including the required module contents.

There’s several ways to accomplish this. In openLuup itself I’ve generally done something like this:

— my module

local function f1()
  whatever
end

local function f2()
  whatever
end

return {
  f1 = f1,
  f2 = f2,
}

Thanks for this fabulous hardware “how to” !

For Zwave, I used to love the 4 button MiniMote, but for similar functionality (non Zwave) I now use Philips Hue smart switches (detachable for hand held.) Labelling the buttons in either of the cases is a non-starter, really.

For voice control, I can use an Apple HomePod Mini, through HomeKit, but for single buttons I’ve also got some Shelly devices.

For wall-mounted buttons, I use the MK Grid system, with Shelly i4 or relays in the wall box. This has the advantage of being available in 1, 2, 3, 4, 6, and 8 wallplate configurations with interchangeable toggle or push buttons, and you can get buttons with etched labels for common functions (fan, etc.)

No really good winning solution here.