20 amp smart physical switch (to control Infratech heater) - preferable to be outdoor rated, but any
Hi all, I'm looking for a 20 amp (minimum) smart switch (physical, so as to either tap switch or remote/Alexa/HomeKit/etc) so that I can control several outdoor Infratech heaters (220V). If they're outdoor rated, even better. Thanks.
I have Wyze cameras and they’re mostly great but would like to find an IP camera that allows scrubbing on playback.
Any recommendations?
Welcome to our HE users! This new Q&A section is for you...
Hi.
I have a ton of different Ledvance bulbs, pluggs sensors and lights.
So far everything works fine.
Bot there is one thing I want too figure out.
I can link lights with the sensor so the light turns on when I enter the room.
But I want to put a timer on it.
Like 5 min without movement and the light turns of. I just can't figure out how..
I use LVD app.
Hello - I'm building a new home with zwave throughout. I want to install a flow detection shutoff, and flow meter for three different areas - a pool autofiller, irrigation system, and the home usage. I'd like to be able to detect any leaks in the system, as well as see the flow/usage by each area. What would you recommend?
hello
i am searching for a universal hub that takes my 433 remotes signals and repeats them 433mhz or converts them into bluetooth, wifi, IR, z-wave etc…basically into all the other signals. so my 433mhz remote becomes a universal remote.
it should have an app to configurate, maybe a learning function as well
i belive the homey pro can do that but it costs like 400$ …right?
so is there a cheap “china” product that works like that for at least 433 into IR, bluetooth, wifi
there are so many chinaproducts and i cant figure out which can do which trick !/ this for example https://de.trck.one/redir/clickGate.php?u=Ha2Rd3xX&m=1&p=9yUI69TI8b&t=kLf5673Z&st=&s=&url=https%3A%2F%2Fwww.techpunt.nl%2Fde%2Fhomey-bridge.html%3Fgclid%3DCj0KCQiA9YugBhCZARIsAACXxeJvViv59ieDen9zOXTP1jhc_OisKQxPlCZOJsPGX20nWo7UROROuJcaAix5EALw_wcB&r=https%3A%2F%2Fwww.hardwareluxx.de%2Fcommunity%2Fthreads%2Fbillige-chinaversion-von-homey-pro-gesucht.1333803%2F
i am working with 433mhz intertechno protokoll remotes .
please help
thanks, christoph
Looking for a simple solution that doesn't require running wire (replacing a switch receptacle is fine)
The problem: the only light switch in my garage is not near a door. So have to walk into the garage to turn the lights on.
Ideal Solution: physical remote I can stick on the wall next to the door to toggle a switch. Is there a product that is a toggle switch to replace the basic switch in the receptacle that I can also operate with a remote?
Is anyone actively developing anything on these IoT chips?
In particular, using NodeMCU for Lua programmability?
Just got a development board to play with myself...
After a fruitless search for WiFI pulse utility meter readers (can't believe I couldn't find anything suitable) and also having resolved a while ago not to include any homebrew hardware in my HA configuration, I've decided in the end to try this out, after all.
Having cut my teeth on Lua, thanks to Vera, it seems promising to use it for development, rather than Arduino programming, and the hardware is SO much cheaper, smaller, and neater than a RPi or the like.
Any experiences welcomed!
AK
Shelly i3 is an unbelievably cheap (9,99 EUR/USD) WiFi device that’s part of the fantastic Shelly family. It supports REST API, MQTT and much more.
https://shelly.cloud/knowledge-base/devices/shelly-i3/ 10
It’s just L,N and 3 inputs. No relays, so it’s a scene controller with bonus point to the fact that you can use your own buttons and keep the aesthetics of your house. Bonus points for WAF. It’s very small, so it will fit in your standard wall box easily.
While I built my own Scene Controller Virtual Device and I’m using MQTT for other devices of the family, Shelly can call your HTTP endpoints on button presses and in this case is more than enough.
The buttons support different actions (press, long press, double/triple press) and you can just call a service endpoint, or update a variable:
f3e509c0-f2a7-4f40-a099-af765e87c9fe-image.png
Go get it if you need a very cheap, very reliable scene controller for your home.
Finally, I’ve found an adequate replacement for my beloved MiniMote four-button remotes (I’ve had nine of them for the last 10 years or so!). I should have realised this earlier, but with four buttons and approximately the same form factor, the Philips Hue remotes are viable replacements…
…however, they are, of course, Zigbee and not Zwave, but this doesn’t matter in my HA environment, which has now completely ditched Zwave and Vera for all lighting and control functions, and replaced them with Hue and Shelly devices. These are all brought together with a Homebridge installation running under Docker on Synology NAS with the Apple Home app as the UI. This gives, of course, both secure remote access and voice control.
The MiniMote buttons I had configured as scene triggers to do whatever I needed, most usually toggling lights. The same functionality is easily achieved within the Home app by appropriate shortcuts.
I’m still using openLuup as a secondary hub which mimics all the various devices using MQTT and the ALTHUE plug-in and logs all device and sensor data using the built-in Historian and viewed through Grafana.
Works for me!
AK
After a long wait for an updated version of the rather crude and unfinished Z-Way integration to HASS, i'm now looking (reluctantly) in to replacing Z-Way with Z-wave JS..
Mind you this is a big existing network, not a new controller stick..
I threw up a docker for z-wave JS UI, and tried to connect it to the UZB stick.. It loads the whole network from the stick, but the driver keeps restarting?
Looking at the logs, I see a lot of Dropping message because the driver is not ready to handle it yet.
It seems like the stick just keeps talking like z-way was still listening? This ends up in the driver crashing repeatedly.. Any ideas to how I can get them talking?
In the code snippet below, you see the driver restarting with the graphic letters, seemingly while the stick is mid-sentence, or because of ACK timeout...
2022-10-02T19:19:59.664Z CNTRLR received additional controller information: Z-Wave API version: 6 (legacy) Z-Wave chip type: ZW050x node type Controller controller role: primary controller is the SIS: true controller supports timers: false nodes in the network: 1, 5, 6, 10, 11, 12, 13, 14, 17, 18, 21, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 36, 37, 38, 39, 41, 42, 43, 44, 45, 46, 4 7, 48, 52, 55, 69, 70, 71, 73, 74, 75, 77, 78, 79, 81, 82, 83 2022-10-02T19:19:59.765Z CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated 2022-10-02T19:19:59.766Z CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated 2022-10-02T19:19:59.767Z CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated 2022-10-02T19:19:59.768Z CNTRLR [Node 001] [+] [Manufacturer Specific] manufacturerId: 277 2022-10-02T19:19:59.769Z CNTRLR [Node 001] [+] [Manufacturer Specific] productType: 1024 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [+] [Manufacturer Specific] productId: 1 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [Version] firmwareVersions: metadata updated 2022-10-02T19:19:59.771Z CNTRLR [Node 001] [+] [Version] firmwareVersions: 5.39 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [Version] sdkVersion: metadata updated 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [+] [Version] sdkVersion: "6.9.0" 2022-10-02T19:19:59.772Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms 2022-10-02T19:19:59.792Z SERIAL » 0x01050006640f97 (7 bytes) 2022-10-02T19:19:59.792Z DRIVER » [REQ] [SetSerialApiTimeouts] payload: 0x640f 2022-10-02T19:19:59.815Z SERIAL « [ACK] (0x06) 2022-10-02T19:19:59.816Z SERIAL « 0x01050106640f96 (7 bytes) 2022-10-02T19:19:59.817Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.177Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:03.178Z DRIVER version 10.2.0 2022-10-02T19:21:03.179Z DRIVER 2022-10-02T19:21:03.179Z DRIVER starting driver... 2022-10-02T19:21:03.199Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:03.212Z DRIVER serial port opened 2022-10-02T19:21:03.213Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:03.229Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.232Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.233Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.234Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.261Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.273Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.274Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.274Z DRIVER loading configuration... 2022-10-02T19:21:03.298Z CONFIG Using external configuration dir /usr/src/app/store/.config-db 2022-10-02T19:21:03.298Z CONFIG version 10.2.0 2022-10-02T19:21:04.284Z DRIVER beginning interview... 2022-10-02T19:21:04.286Z DRIVER added request handler for AddNodeToNetwork (0x4a)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for ReplaceFailedNode (0x63)... 1 registered 2022-10-02T19:21:04.287Z CNTRLR querying controller IDs... 2022-10-02T19:21:04.484Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:04.485Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:04.487Z SERIAL « 0x0123000400511a9f039900b834787d066515a4b79c45bb3af55ea7f6203006010 (37 bytes) 80120c84d 2022-10-02T19:21:04.489Z SERIAL « [DISCARDED] invalid data 0x9ef4 (2 bytes) 2022-10-02T19:21:04.490Z DRIVER Dropping message because it contains invalid data 2022-10-02T19:21:04.490Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:05.488Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i n 100 ms. 2022-10-02T19:21:05.591Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:05.592Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:06.596Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i n 1100 ms. 2022-10-02T19:21:07.698Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:07.699Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:08.717Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D river.ts:3980:23) at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co ntroller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js /src/lib/driver/Driver.ts:1207:26) at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive r/Driver.ts:1014:16) 2022-10-02T19:21:08.723Z DRIVER destroying driver instance... 2022-10-02T19:21:08.728Z DRIVER driver instance destroyed 2022-10-02T19:21:08.739Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:08.740Z DRIVER version 10.2.0 2022-10-02T19:21:08.740Z DRIVER 2022-10-02T19:21:08.740Z DRIVER starting driver... 2022-10-02T19:21:08.745Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:08.751Z DRIVER serial port opened 2022-10-02T19:21:08.752Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:08.754Z DRIVER loading configuration... 2022-10-02T19:21:08.755Z SERIAL « 0x01080120c84d9ef40138 (10 bytes) 2022-10-02T19:21:08.757Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:08.758Z DRIVER « [RES] [GetControllerId]Hi,
I have an old analog intercom (Golmar) that has this horrible buzz sound when someone rings my apartment from the buildings front gate. This becomes very annoying at night so I need to make this buzz silent from 10:00pm till 7:00am
I have a "Shelly Plus 1" connected to the intercom. (wire #0 and wire #3 are responsible for closing the circuit for the buzzer).
I have set Webhooks and Scenes, but my wiring does not work. Can anyone tell me what i have done wrong?
Cheers!
Wiring Shelly 1 plus v12.1.png Golmar intercom current wiring.png
Well with all that has been going on with Vera/eZlo, many people are abandoning the Vera hubs and moving on to other solutions, such as Hubitat (my case), HASS, HA, and many other controllers.
In the past, I had already been informed that when the migration was over, my Vera would go to the incinerator, or under the wheel of my car, and of course, I did not comply.
So I wanted to open a debate, for those who have not yet sold their Vera on eBay, are with the equipment idle, what destination could be given?
I see many saying that it has become a laboratory, I don't see much sense, since it is becoming obsolete and without a drive. But it can be a destiny. Has anyone thought about whether it is feasible to change the hub's SO so that it becomes a host for MSR, for example? Or even Home Assistance? I have no knowledge, but it seems to me that processor and memory have to do something like that, already has embedded wifi and network.
Does anyone have any idea if it is possible to give this equipment a destination other than a box?
I just started [uncloud] forum to gather in one central place all smart devices working without the cloud, since this is not information easily available on the Internet.
I thought this might interest some users of this forum and any feedback are welcome.
And let me know if you know more devices that I should add to the list!
- Marco
Good afternoon. Due to the new ezlo not being available in europe yet, I wanted to change the z-wave getway that works with the reactor to add to the home assistant. What advises?
Thanks
I didn't see an existing Topic for heating-ventilation-air conditioning, so here goes...
Is anyone successfully controlling a "mini split" (i.e. ductless) A/C or heat pump system at home? I will be adding such a system soon to new construction, and wondered if certain brands/models interface better via Z-Wave or WiFi than others in a HA setting.
I know a bunch of these "splits" come with handheld remotes, but having robust Home Automation control (preferably without a dedicated plug-in needed on the Vera side) would be idea.
Happy to hear suggestions. Thanks!
LibraI have a legacy Vera system that in my home and I need to add a few devices to a cottage on my property. The Vera zwave won't see devices that far away. Both the house and cottage are on the same LAN. Can I bridged an Ezlo Plus to my existing Vera plus and if so are there instructions?
Hey guys...
Is it just me or the GE/Jasco switch or very sensible to power outage ?
Almost each time we have a power outage, I need to replace at least 1 switch to replace.
Each time, same behaviour, the blue led is flashing rapidely and nothing works.
Last power outage, I got 3 switches. 95% of our switch and dimmer are GE/Jasco.
Any decent destination for a Vera Plus?
-
@perh I'm using my Synology to (securely) expose it when needed, under https. For longer maintenance, I'm just using a VPN.
Having heavily invested in automations, I'm honestly doing this no more than 2-3 times per year. I rarely use remote control, so this is working very well fom me, and overall, the solution is more secure, since I'm not exposing anything to them. As I've said, it has never been so stable.
-
Hi!
Reading the comments the destination I am giving to my Vera Plus are:
- simulation lab, I have installed the Switchboard Plugin, the old and good Reactor and SiteSensor from @toggledbits , and I think I will download the tools from @therealdb;
- I'm also using the Vera with SiteSensor to ping the internet, Hubitat, and MSR, as external control. If one fails, I send a Telegram, connect a switch, and then initiate action on either Hubitat or MSR.
Now a question, I do not know if @toggledbits can help.
Is it possible to make some settings in MSR, so I can exclude devices that are published from Vera to MSR? I see for example that the three pings that I set up are triggering the MSR unnecessarily, as well as other devices from the lab.
Is it possible to have an exclusion table that I don't need MSR to load and synchronize some devices from Vera?
Thanks.
-
@wmarcolin said in Any decent destination for a Vera Plus?:
Is it possible to make some settings in MSR, so I can exclude devices that are published from Vera to MSR?
Specifically for VeraController, you can use
filter_entity
in your config for the controller. It's anarrayobject, and you list the (would-be) entity IDs you want to exclude....(redacted other config) implementation: VeraController config: source: "http://192.168.0.123:3480" filter_entity: device_10: true # true to filter the entity out, false to keep it in device_94: true device_401: true
Or, if you are excluding almost all of the devices, and just want Reactor to pick up a few, use
accept_entity
using the same form, listing the IDs of the devices you want Reactor to have.EDIT: Whoops! It's not an array, it's an object. Fixed above.
-
@toggledbits said in Any decent destination for a Vera Plus?:
filter_entity
@toggledbits hi!
Thanks for the prompt information, but I think something is not working right.
I tested the deletion first:
config: source: 'http://192.168.33.6:3480' filter_entity: - device_15 - device_6 - device_13
See that it didn't remove the devices.
Then I tested for keeping only the ones I am interested in.
config: source: 'http://192.168.33.6:3480' accept_entity: - device_9
Then removed all the devices.
Log second scenario, no error:
[latest-22023]2022-01-24T19:28:34.186Z <OWMWeatherController:null> Module OWMWeatherController v21354 [latest-22023]2022-01-24T19:28:34.189Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22023]2022-01-24T19:28:34.193Z <SystemController:null> Module SystemController v21358 [latest-22023]2022-01-24T19:28:34.195Z <Structure:INFO> Starting controller VeraController#vera [latest-22023]2022-01-24T19:28:34.196Z <VeraController:NOTICE> VeraController#vera starting [latest-22023]2022-01-24T19:28:34.248Z <VeraController:INFO> VeraController#vera loaded mapping ver 21346 rev 1 format 1 notice [latest-22023]2022-01-24T19:28:34.250Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-22023]2022-01-24T19:28:34.251Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-22023]2022-01-24T19:28:34.252Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state [latest-22023]2022-01-24T19:28:34.269Z <Structure:INFO> Starting controller HubitatController#hubitat [latest-22023]2022-01-24T19:28:34.285Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22023]2022-01-24T19:28:34.287Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online.
Since the device is not included, the MSR action shows an error in the log.
[latest-22023]2022-01-24T19:28:35.487Z <Rule:INFO> Hard Reset Sat 4am (Rule#rule-kxp4v1ly) evaluated; trigger state unchanged (false); rule state remains RESET [latest-22023]2022-01-24T19:28:35.494Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_9" ReferenceError: Can't find entity "vera>device_9" at Predicate._evaluateCondition (C:\MSR\reactor\server\lib\Predicate.js:635:27) at Predicate._evaluateGroup (C:\MSR\reactor\server\lib\Predicate.js:1015:103) at Predicate._evaluateCondition (C:\MSR\reactor\server\lib\Predicate.js:623:47) at Predicate.evaluate (C:\MSR\reactor\server\lib\Predicate.js:331:38) at Rule._evaluate (C:\MSR\reactor\server\lib\Rule.js:830:62) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async C:\MSR\reactor\server\lib\Rule.js:786:17 [latest-22023]2022-01-24T19:28:35.496Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_9" ReferenceError: Can't find entity "vera>device_9"
Thanks.
-
@toggledbits opened Mantis 300.
Thanks. -
Sorry, not a bug, I just gave you the wrong syntax. I fixed my earlier post.
-
@toggledbits testing!
Perfect removed the indicated
source: 'http://192.168.33.6:3480' filter_entity: device_15: true device_6: true device_13: true
Ok, kept only the informed one that had to stay, removed all the others.
source: 'http://192.168.33.6:3480' accept_entity: device_9: true
Thank you very much!
-
@toggledbits double-checking that for InfluxFeed plugin configuration syntax is:
filter_entities: - "vera>device_398" - "vera>device_413"
-
Check the docs; clearly after what I did to @wmarcolin , my memory is not reliable of these details!
In any case, the indenting is way off.
-
@toggledbits testing with version 22025 we have the following situation.
In the manual (https://reactor.toggledbits.com/docs/Troubleshooting-Entities/), it looks like this:
accept_entity: "device_123": true dump_entity: "device_123": true
I tested it this way in the new version and it works like the manual - without quotes (have to fix the manual):
config: source: 'http://192.168.33.6:3480' accept_entity: device_9: true
So, I tested the new version that I understand you have aligned with the other systems:
accept_entity: - device_9
OR
filter_entity: - device_9
IT WORKED!!!
Testing the way that mentioned @tunnus :
filter_entity: - "vera>device_9"
IT DOESN'T WORK, with or without the quotes it doesn't work.
IN SUMMARY, the form can be for Vera, don't know for other hubs:
accept_entity: device_9: true
or
accept_entity: - device_9
I hope I have helped.
-
@wmarcolin said in Any decent destination for a Vera Plus?:
IT DOESN'T WORK, with or without the quotes it doesn't work.
The reason it doesn't work is because you are including a controller ID to make it a canonical ID. Canonical IDs are not used in that context because the configuration is already specific to one controller -- you don't tell it the controller for
filter_entity
in a VeraController config because it's in the controller's config, so it already knows.InfluxFeed is different because it watches entities for all controllers, so when identifying an entity, you have to use a canonical ID.
As for quotes or no quotes, as long as the string doesn't contain any characters with special meaning to YAML, you don't need quotes. Do you know what those are? I don't keep that in my head. So I default to using quotes whenever it's anything other than A-Z, 0-9 and underscore. The
>
used in canonical IDs can definitely cause problems, so I always quote canonical IDs. -
New use for Vera, and helping to save him from the incinerator
One of the eventual problems I am having with Hubitat, are devices that are added with Security S0, and several community posts report that this is a problem.
So today I removed and reinstalled what had S0, but 4 there was no way to get in without Security, and to not create a problem in Hubitat's z-wave network, I installed again in Vera: Door Lock Yale B1L YRD110-ZW-0BP, Smoke Sensor Smoke (2x) and Bulb Zipato RGBW2.US.
Of course I had problems to include in the Vera, the bulb is failing, everything we already know in the Vera. Just unfortunate that Hubitat can not bypass this problem.
-
I have tried several times, removing the device and reinserting it, hoping to get the prompt to use the security code or not, but it didn't happen. So I put it in the Vera, so if there is a communication problem, it doesn't affect the Hubitat network, and the Vera ended up with only these 4 devices.
I also took the opportunity to remove the Vera from the cloud (https://github.com/toggledbits/Vera-Decouple) for stability.
-
I shared this information on the Hubitat forum, and received a message that I think is in line with your comment about the lock, that even though it is S0 I should keep it on Hubitat because in this case, not having recurring status communication would not affect the z-wave network. I think I will come back.
-
@wmarcolin said in Any decent destination for a Vera Plus?:
… I wanted to open a debate, for those who have not yet sold their Vera on eBay, are with the equipment idle, what destination could be given?
I have to admit, my Vera (of which I have 4 now, thanks to people who have jumped ship via eBay
) still runs my house, and being paired with a Rasp Pi - that provides me with additional command line capabilities too. Hence it’s still ticking the majority of boxes for me, and call me crazy but I do love the Vera UI.
My situation is perhaps a little different in that It took me well over a decade of using Veras, to understand aspects of what goes on under the hood (Lua/Luup wise), and I’ve just recently started to create my own Vera plugins (oh if my younger self could see me now ;-)). That capability is opening up area I never thought of before. So as you can see I’m very late to the party on that front, which is a shame..
With all that said, I know it’s not going to last forever, and sadly my dream of ezlo making Vera (Luup/UI) a community version for us all to build on is likely never gonna happen, but I have no idea where I’ll eventually end up.
I do love the open-source stuff and must have tried pretty much everything out there, HASS, OpenHAB, NodeRed etc. plus I’ve also been tempted by the Hubitat and Fibaro HomeCenter even ezlo Hubs if they get their act together.
Ultimately- I like the idea of having a ‘one-stop-HA-shop’ - with everything I need all in one place..
-
@parkerc Well said. I'm grateful to hang with the geniuses around here and contribute what I can over the years. But the situation with Vera and Ezlo doesn't stimulate confidence in any commitments to cooperation or extensibility, does it?
I have vacation rentals with Vera Plus or Secure. Lots of lovingly handcrafted scenes, lua code, defunct plug-ins glued together, scripts on Pis. I would love to pull together a "greatest hits" compilation of how-to documentation to set up automation analogous to Vera capabilities. Open-Luup on Pi? How to set up GUI and remote access? some hybrid with existing Vera UI7 GUI (mob app sux). But clearly decoupling is providing many benefits. Several have gone in different paths, would be great if there is a hardware/software/plug-in view for the future as a migration path outside of Ezlo
-
OK, well let’s see what a
non-Vera, Vera-like
set up could look like…openLuup - https://github.com/akbooer/openLuup
openLuup zway - https://github.com/rafale77/Z-WayAnd in your situation, each remote location will need some sort of a vpn server set up; so you can connect to it remotely, so maybe something like..
PiVPN - https://thesecmaster.com/how-to-set-up-open-vpn-on-raspberry-pi/
Assuming you can migrate your Vera plugins and zwave devices to the above Open-Luup set up - What else do you have to factor in ?
-
I have largely moved away from Zwave, excepting my beloved MiniMote 4-button controllers (about half a dozen of those) and a couple of electricity meter readers. These are also the only devices that remain on Vera… I just haven’t bothered to move them. ZWay would be a good alternative here, when Vera finally fails. Don’t say I didn’t warn of the demise of Vera, and Ezlo was never a contender.
Of course, openLuup does all my automation, along with Shelly devices via MQTT and Philips Hue. The whole thing is now supervised by Apple Homebridge running on a Synology NAS (along with openLuup) and it’s the Apple Home app that I use for occasional manual control and remote access… no need for a VPN.
-
@akbooer said in Any decent destination for a Vera Plus?:
Don’t say I didn’t warn of the demise of Vera, and Ezlo was never a contender.
It’s been a pretty long, drawn out demise
and thankfully, even in this limbo state, I’m still getting what I need from my Veras.
@akbooer said in Any decent destination for a Vera Plus?:
The whole thing is now supervised by Apple Homebridge running on a Synology NAS (along with openLuup) and it’s the Apple Home app that I use for occasional manual control and remote access.
Nice, I’ve been running Homebridge and openLuup on my QNAP - for a while, just to give me an iOS route into things, but I’ve never considered making it the overall supervisor - but you’ve got me thinking (as the house is largely Apple)
Which Vera Homebridge plugin are you using ?
My Docker/QNAP side-set up is pretty good, and i have multiple HA related containers (node-red, zoneminder, Homebridge , HomeAssistant, Homer etc.) all interacting with each other - but I must admit I do still like the idea of having everything I need focussed into a few, and all running on a Raspberry PI. (Perhaps that’s more for the confidence in using all my usb add-on elements ( Bluetooth, zwave and RFXtrx433).