DIY HomeKey locks via Reactor

[wmarcolin]

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?

[Matohl]

I use my Vera+ for the z-wave and 433 devices (I even have one in reserve) together with MSR and Home Assistant, working well. If I remember well I think @toogledbits have said he is experimenting with the MSR on Vera but I'm not sure if that is on the table today.

[toggledbits]

@matohl said in Any decent destination for a Vera Plus?:

@toogledbits have said he is experimenting with the MSR on Vera

That was Ezlo... I do have it running on an Ezlo Plus. Not something I'm probably going to release, though, at least, not just yet.

[akbooer]

I still use a Vera Edge as a Zwave to HTTP bridge, as a peripheral to an openLuup system.

[PerH]

I have two VeraPlus running at the cabin (in separate houses), one at my parents house, and they work well with only a few devices(z-wave and 433) and cameras.
I will probably have to replace them when ezlo pulls the plug on the server though.

[gwp1]

@perh Have they indicated an official EOL date now?

[therealdb]

@perh just decouple them and you’ll be fine. I’m running off the cloud in the latest year and my Vera plus has never been more stable than today. It’s just a Zwave bridge with a reload once per week, due to some code still running and that I’ll port outside very soon.

GitHub - toggledbits/Vera-Decouple: Scripts to decouple Vera Home Automation Controllers from their parent cloud services

Scripts to decouple Vera Home Automation Controllers from their parent cloud services - toggledbits/Vera-Decouple

[PerH]

But then i'd have to figure out a way to remote connect to them first.. how do you do that? Can Dataplicity be installed perhaps?
Haven't read about EOL date, so it might be years still.

[therealdb]

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

[wmarcolin]

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.

[toggledbits]

@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 an arrayobject, 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.

[wmarcolin]

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

[wmarcolin]

@toggledbits opened Mantis 300.
Thanks.

[toggledbits]

Sorry, not a bug, I just gave you the wrong syntax. I fixed my earlier post.

[wmarcolin]

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

[tunnus]

@toggledbits double-checking that for InfluxFeed plugin configuration syntax is:

  filter_entities:
         - "vera>device_398" 
         - "vera>device_413" 

[toggledbits]

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.

[wmarcolin]

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

[toggledbits]

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

[wmarcolin]

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.