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

@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.

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 !

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

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 will embark soon on the same path. I’m just waiting for my home vacation in August. I will leave my Vera on since I still have Nest, I like them and there’s no way to port them. It will just be a Nest gateway, but I’m done with Zwave on it. The last months have been impossible, thanks to more activity outside, as it’s usually for me during Christmas time and Summer.

@Elcid said in Video Doorbells:

My door is covered by a hidden microwave sensor. when triggered reactor sends a http request to my phone or tv box, depending on home or away. My phone/box uses Automate to receive the http request, Automate then opens the camera app and displays the camera. I can talk and listen though the camera app. Normally takes 5-10 seconds to complete. If i am home vera sends a TTS to alexa, informing me there is some one at the door.

I have a BTicino (part of Legrand, very common in France/Italy/Spain) doorbell. They have a proprietary system, but it's basically a video doorbell. I spent almost 1k to have it installed, but it's doing multiple entries, multiple inside points, etc. I have it hooked up with a binary sensor to get doorbell status, plus a switch to open the gate. It natively supports Android/iOS and I get a call and I can reply even when outside. I use it to let the packages in my porch, etc, since here in Italy open garden on the front yard is not common, we have the whole property closed to external guests.

I too have a similar setup as @Elcid. When someone rings, I send a notification to our phones and I turn on camera recording (I turn it OFF during the day, unless events are triggered), and I turn on a tablet in the open space to show all the external camera. It's near the video doorbell proprietary tablet, so you'll see the person on the doorbell, plus all the cameras. Everything is pushed via my telegram bot.

If it's night, I turn on all the lights (I have more lights outside that I turn on during parties or when doors/gates are opened). Overall, I like my setup, the only thing I regret is that this system is closed and I can't capture a screenshot of the wide-angle camera easily. I wanted to separate this from the HA system to have stability - and I was right, from that point of view.

anyway, @DesT , I published a new version using CURL instead of socket.http/ssl.https, if you want to try it and see if the json truncation is over (it should be). Thanks!

So, I received my units and start thinkering. So far, one is in place, while I need to build a support for the other.
Code is just a small node js app I built around a node library. Seems to work, and I'll report more in the future. Too bad the official hub has no local apis. I can't understand why smart people don't realize internet is not a available everywhere as in their offices...

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).

ok, so:

local _, async = pcall(require, "http_async")

if type(async) == "table" then
else
end

seems to be way to do it. Leaving this post here for the future me

I'm trying to implement the support for http_async in my Virtual Devices plugins. From my tests, Vera's UI seems less busy, but I want to automatically detect if it's installed. Right now I'm using a code like this one:

if pcall(require, "http_async") then
  
else
...
end

but I'm not sure it's the best way to do it. Any one? @akbooer? Thanks!

@sender said in Smaller and local alternative to MicroBots:

but I use D1 mini and flash with tasmota via "tasmotizer"

I have many of them across the house, mainly to get fancy sensors (distance, humidity, light, pressure, etc), and I integrate them with my own MQTT to luup bridge, plus my virtual plugins.

Anyway, this is an appliance I can't hack at the moment, since it's still under warranty. I've ordered two and will try to integrate via BT. SwitchBot has an open BT API, documented and supported by Home Assistant, so it should be easy to just get the script and replicate it with some luup calls or whatever I'll come with

Yep, swichbot seems to be a viable solution. Local control is possible via bt. I'll order one and try it. Unfortunately I can't change the button.

I have a need to just push a button, since I can't hack the thing at the moment. I know there's MicroBot, but they're bluetooth, requires and hub and are not local.

I'm OK with BT or an additional hub, but I really really want local control.

Anyone? Thanks!

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 had a brief health problem in the latest days that put me completely KO, but I'm recovering. Code is almost done, I just need some time to test it under load and write some doc. I hope to finish it later today.

@rafale77 I have a simple version almost ready. I'll debug later today or tomorrow, and put on GitHub. Here's an excerpt of the config:

{
	"MQTT": {
		"Username": "vera",
		"Password": "openluup",
		"Port": 1883
	},

	"Devices": [
		{
			"Name": "Pool",
			"ClientID": "sonoff-pool",

			"TopicName": "tele/tasmota/SENSOR",
			"TopicPath": "AM2301.Temperature",

			"DeviceID": 12,
			"Service": "urn:upnp-org:serviceId:TemperatureSensor1",
			"Variable": "CurrentTemperature"
		},

		{
			"Name": "DeHumidifier",
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "ON",

			"DeviceID": 12,
			"Service": "urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
			"Variable": "ModeTarget",
			"Value": "HeatOn"
		},

		{
			"Name": "DeHumidifier",
			"ClientID": "tasmota-dehum",

			"TopicName": "stat/sonoff/POWER",
			"TopicValue": "OFF",

			"DeviceID": 12,
			"Service": "urn:upnp-org:serviceId:HVAC_UserOperatingMode1",
			"Variable": "ModeTarget",
			"Value": "Off"
		}
	]
}

I think it's more than enough to understand how the things will gonna work