I've just completed my setup (after exactly 3 years from moving in, priorities!) and even if I wrote all the code in C#, I could port it easily to LUA (I guess )

I've used Fully Kiosk Browser + 3D Printed Mount (check https://makesbymike.com/) and a custom HTML dashboard, all running on an Amazon Fire Tablet:

WAF is very high

Sorry for the Italian interface. First row is temperature/humidity sensors (esterno = outside, piscina = pool, salotto = open space, zona giorno = 1st floor, zona notte = 2nd floor, lavanderia = laundry room).
Then I have a bunch of commands/scenes sent to Vera to change blinds/roller shutters (they are automatically managed, but wife pretends to be smarter than code, from time to time ). Last row has notifications for washer/dryer, with the cycle end date. When doing its cycle, the background becomes orange, then green when completed. It's probably the best feature, since the laundry room is in the basement. There's also a link to cams (videosorveglianza) and I automatically open TinyCamPro in case of movement outside/doors/gates are opened.

Is there any interest in a generic wall mount tablet plug-in, offering simple dashboard (maybe json-driven) and integration with Fully Kiosk API?

I'm currently dimming screen on/off, get the battery status and schedule a 20-80 cycle for the battery, via a smart plug and a bunch of lua code. I planned for this when I did the electrical setup, so the tablet has a standard european 503 (recessed) box with ethernet, that I attached to the 5V into the network closet to feed the tablet. I'm updating the screen via AJAX every 30 secs.

Here's a behind the scenes photo as well

So, I was messing with my Alexa routines and ha bridge, and I want to share something very cool you could do with the ability to get the last Alexa that heard your command. I mentioned it a couple of times on the old place, but Vera's OS is missing the jq package, but openLuup could have it installed.

Basically, just execute -lastalexa with my VeraAlexa plug-in:

local lastAlexa = luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", 
  "RunCommand",
  {Command="-lastalexa"}, 666)

Then use it in your scene, to dynamically generate your TTS response with the device you've asked your question seconds before!

local temperature = 25 -- get it from your sensor
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", 
  "Say",
  {Text="Ok, outise temperature is " .. temperature .. " degree", Volume=50, GroupZones= lastAlexa, Repeat = 2}, 666

Very cool indeed

I just released v2 of my Virtual HTTP Devices Plug-in. As always, 100% local, 100% standard, mobile friendly and working on openluup/altui as well.
GitHub

dbochicchio/vera

LUA Scripts for the eZlo Vera Platform (UI7). Contribute to dbochicchio/vera development by creating an account on GitHub.

What’s new in v2:

• Master/Children: now you can just create a master and have any number of children attached. They will still work separately, but this will greatly improve memory consumption on Vera. Please see GitHub for guidance on migration. No need to do it unless you have many devices on your system.
• async update of device's status. If you want to update the status of your device separately, just return something different than the HTTP code 200/300 family. it’s useful if your device doesn’t complete the response with the call and you want to update its status. Just use a normal Vera call to update the corresponding variable
  -added support for Scene Controllers (see my post in Shelly i3 for a use case)
• more work around switches/heaters
• stabilization and fixes

Get it from GitHub or from AltAppStore.

@CatmanV2 said in The Home Automation Controller Pyramid:

2020 or 2021? 2021 seems more likely. Short sprints only means lots of progress if you're actually capable of writing code. Given the number of recurring issues, this seems something that may be beyond them.

2020. Short sprints mean more bugs for sure, but better ability to fix them as well. I prefer over the previous approach, we'll see.

@rafale77 said in The Home Automation Controller Pyramid:

What they should have done was to put design a core firmware from the beginning

we all know. I was just reporting that they did a good thing. It doesn't mean that the results will be enough, or in time to retain theri customer base.

Openluup seems to be the best viable solution for a smooth transition.

here we are: https://github.com/dbochicchio/luup-mqtt

Try it and let me know. It should be easy to acquire .NET Core SDK and build the app. It's very minimal, fast and should be easy to understand. Right now it's only updating variables (with virtual device I think it's more tha enough), but I could add other actions if needed.

I have a no brand chinese Zwave PIR outdoor under my patios since two years and they survived two winters (this year was warmer, last year we had a a couple of weeks under 0 C). They're protected from rain and sun. Ugly to look, but very effective (and 100% supported under Vera, if that matters to you anymore):

US $29.71 30% OFF|Zwave Plus Movement Sensor Motion Detector Sensor Alarm Z wave Z wave Wireless PIR Motion Sensor Smart Home Automation|Building Automation| - AliExpress

Smarter Shopping, Better Living! Aliexpress.com

So, I finally switched myself to HA bridge. This was caused by me using IFTTT with some local commands (bridged thru my own cloud server).

Wow, I'm impressed and that's because I can call my own local endpoints, so I can finally build more routines to please the wife. Happy wife, more automations!

I just published an update to my Virtual Devices Plug-in.

What's new in version 1.5:

• support for async HTTP (out of the box on openluup, just download https://github.com/akbooer/openLuup/blob/master/openLuup/http_async.lua and copy with the plug-in files on Vera)
• experimental support for setpoints management in Virtual Heaters (you know, the device will turn itself off if temperature is reached, and automatically on when temperature is not beyond the setpoint)
• external device for temperature in Virtual Heaters (just set urn:bochicchio-com:serviceId:VirtualHeater1/TemperatureDevice variable)
• small fixes, stabilization

Grab your copy from https://github.com/dbochicchio/vera/tree/master/VirtualDevices

As always, 100% local, 100% apps friendly, 100% supported by Alexa (and Google Home, I guess).

We have Fibaro (Not so) Smart Implant and Universal Binary Sensor in Europe.

I use them for:

• alarm status
• gate/door status (outside, where I don't want a bulk or battery sensor)
• wind/rain notifications attached to sensors

I agree with @Elcid. I will simply remote it, if possible. I'm a fan of minimalism and on a community forum that's even more important. Thanks for the hard work @DesT !

well, it's possible in LUA as well. I'm not that expert in the file system libs, but Google is your friend

How to get list of directories in Lua

I need a list of directory in LUA Suppose I have a directory path as "C:\Program Files" I need a list of all the folders in that particular path and how to search any particular folder i...

Just use io to open files, but I think that so many commands will probably crash your luup engine. We're potentially speaking of thousands of calls to try.

@a-lurker said in upnp event proxy:

Well it would obviously require a major rework of some of the code but some users do find installing stuff manually not so easy - including me at times!

Speaking of this, you can just detect openluup and stop doing the magical thing. Remember openluup can run on windows and Macos too and I'm not sure daemon could be so generalized.

Ping him, it's been very critical about Ezlo lately, so maybe it's willing to fix it, if necessary.

I'm not aware of anything like you requested. There are things that could learn codes, but they require a handheld. Have you tried calling the manufacturer? Maybe they will give you instructions about this issue.

Isn't rigpapa new version already on Github?

Can’t you just install ubuntu (it’s easy with windows subsystem for Linux , if you’re a windows user) and try it?

I will just remove this part completely and give instructions to manually install the daemon. People using openluup are usually able to do it and I’ll prefer this any day over a script messing with my config files.

Yep, I underestimated those cheap wifi devices, until I started to buy many of them, just for testing. While I prefer Zwave for "serious" work, since I have 3 access points on my home (and one outside), Wifi coverage is really good and their traffic is very low anyway, so I'm somewhat sold, especially for fancy sensors and/or difficult to reach zones for my Zwave mesh.

Just to update this thread, I've installed my sensor, added my virtual sensor and this seems to work. I'm still operating the blinds at specified time (but looking at the real amount of light to choose to operate them or not), but weather is starting to suck here in Italy, so I'm working on something smarter than this. I'll probably write some averaging logic, in order to avoid to operate the blings too frequently.

So, I was messing with my Alexa routines and ha bridge, and I want to share something very cool you could do with the ability to get the last Alexa that heard your command. I mentioned it a couple of times on the old place, but Vera's OS is missing the jq package, but openLuup could have it installed.

Basically, just execute -lastalexa with my VeraAlexa plug-in:

local lastAlexa = luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", 
  "RunCommand",
  {Command="-lastalexa"}, 666)

Then use it in your scene, to dynamically generate your TTS response with the device you've asked your question seconds before!

local temperature = 25 -- get it from your sensor
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", 
  "Say",
  {Text="Ok, outise temperature is " .. temperature .. " degree", Volume=50, GroupZones= lastAlexa, Repeat = 2}, 666

Very cool indeed

I use my own internal ntp time server. I'm not sure why, maybe open a ticket, they're usually very fast to reply.