Discuss your vera problems and findings here

55 Topics 855 Posts
  • 0 Votes
    2 Posts

    Thanks! I have this on my roadmap, so it’s really appreciated. I’ll also work on a script/plugin to easy remap from one controller to another, since I’ll definitely need it.

  • 0 Votes
    11 Posts

    I developed this mapping table in answer to some of my own questions above.

  • floor heating automation

    0 Votes
    1 Posts
    No one has replied
  • Nuke Vera Script

    3 Votes
    20 Posts

    I havent needed Socat, just using Z2MQTT in a docker, and it connects to the vera just fine over network.. I ended up retiring the vera in the end in favour of UZB and Z-Stick, as some functions and security didn't work, but basic z-wave works well.

  • 0 Votes
    7 Posts

    Today I moved my last device from Vera to HomeAssistant. I do have mixed feelings about it. For all it's flaws and performance issues, it had a very easy interface to get started in and for the average person, could do most of what they needed. Started using PLEG but never got very far with it since I had to spend hours relearning it every time I wanted to add a new automation. Reactor was a breath of fresh air for the Vera and I am eternally grateful for all the assistant I have received from Patrick over the years including some beta code for my Leviton scene controllers and my Venstar thermostat. MSR allowed me to tie my Vera and Home Assistant together while I slowly migrated off Vera and had way more capabilities than I could ever master.

    As I get older, my wife keeps telling me that if I die she is selling the house because she cannot run it. That has given me some incentive to simplify my environment so I have gone to only Home Assistant. Would have stayed with MSR if I could have figured out how to get the addon to work in HA, but in the end was easier to move everything to HA and eliminated one more component.
    Thanks to all the people that have offered assistance on this community as well as the old Vera forum before EZLO.


    Have a nice Vera Plus available if anyone is interested. In the Seattle area but will ship. Make me an offer.

  • 0 Votes
    50 Posts

    @htcheng Out of interest what type of Vera are we talking about here? Ditto what sticks were you using?

  • Vera 3 with a Z-Wave.Me UZB stick

    0 Votes
    2 Posts

    It won't work. You are attempting to use a GEN3 device (Vera3) with a GEN5 or higher device (UZB).
    Z-Wave is backwards compatible but what you are endeavoring to do is the opposite.

  • iPhone locator or alternative.

    0 Votes
    5 Posts

    @akbooer Thanks again, I will poke around a bit. I have not explored anything with HomeKit yet, but it was something on my list.

  • Power monitoring options

    1 Votes
    9 Posts

    Like @Crille I have an electrical meter with a P1 data port. I use a DIY ESP8266 reader that I described some time ago in this thread. Since writing my post I have changed the software on the ESP, the version I am using now publishes the meter data approx every 10s as a json.

    A good wifi solution for the whole house if lacking a dataport is to use a Shelly 3EM. It is a three clamp meter that can measure all three incoming phases, assuming you have that. I have a few of these for measuring both single and multiple phase consumers, e.g. a two-phase water heater. It reports both energy, power, voltage and current per phase.
    The only downside I can see is that the clamps are a bit big, so some space is required to get them in place around the incoming power lines.

  • Getting FW version from Vera's FirmwareInfo

    0 Votes
    3 Posts

    Thanks for the pointers. I’ll try to look at plugs directly, maybe there’s a stick somewhere.

  • Vera to zwavejs

    1 Votes
    5 Posts

    Nevermind, I started the exclude include journey... almost gone from Vera... I must admit, I'm going to miss her. I whish including was as fast and stable as excluding 🤣

  • Vera firmware 7.32 beta

    0 Votes
    86 Posts

    I do it in startup Lua, so I don't forget. It also makes it easy to go in and change it when I want it back on (my feeble memory doesn't have to remember the precise spelling of the setting).

  • 0 Votes
    1 Posts
    No one has replied
  • Method to get the security key from Vera?

    0 Votes
    3 Posts

    Ah thanks so much 🙂

  • Why is VERA+ making calls to

    0 Votes
    7 Posts

    I've been working on a mechanism for this, but unfortunately, there are many cross-platform issues (e.g. how WIndows does it vs Linux, whether it's doable in a docker container or not, etc). Every environment is a little different.

    As a workaround for bare-metal Linux, there is a script in tools called that can be run by cron (as a non-root user). It will ping various sites and create/update x_reactor_system_extra.inet_ok on the Reactor System (reactor>system) entity.

    I have no such solution at the moment for Windows or Docker. In my own house configuration, I just use the flag from the entity for the Vera's Reactor master device.

  • Can I connect a Nokia/Withings scale to Vera?

    0 Votes
    3 Posts

    @parkerc Intriguing. I will look into that avenue, thanks!

  • Help with Luup Reloads

    0 Votes
    33 Posts

    @therealdb the files seem to be deleting by themselves. The plug-in itself though is still unstable though, I observed some new behaviours. I will post on the thread I started about the counter.

  • How to reset a Tripped state?

    0 Votes
    3 Posts

    If you're doing it from MSR, use the x_vera_device.set_variable action on the device to set Tripped (service Id urn:micasaverde-com:serviceId:SecuritySensor1 to 0.

    An HTTP would do essentially the same as the above ('http://vera-ip:3480/data_request?id=variableset&DeviceNum=NNN&serviceId=urn:micasaverde-com:serviceId:SecuritySensor1&Variable=Tripped&Value=0`).

    And of course, you can do it in Lua: luup.variable_set( "urn:micasverde-com:serviceId:SecuritySensor1", "Tripped", 0, device_number )

    Devices in the SecuritySensor1 service also support an AutoUntrip state variable that if set to a non-zero number of seconds will reset the Vera device (not the physical device) to untripped after that time. If you have to create the variable, the service ID is the same as that listed above.

    Keep in mind that any of these manipulations of the state variable have nothing to do with what the physical device thinks, so Vera won't report the actual reset of the device (because Tripped has already been set to 0/false), and any refresh of the device (e.g. Luup reload) may cause a retrigger.

  • 0 Votes
    3 Posts

    @futanare I've not really updated the App Store versions of my plug-ins in the latest months, partly because the dev portal is frequently offline/with errors, partly because I've lost faith in Vera as a platform. download it from GitHub and give it a go. If I find time, I'll update it on App Store as well.

    EDIT: also, set DebugMode variable to 1 and post some logs. Vera FW version and OpenSprinkler FW version are also appreciated.

  • 1 Votes
    10 Posts

    The Zooz stick and the Ezlo share a common Z-Wave chipset. In fact when I added the Ezlo to ZWave-JS it shows up with a product code of ZST10-700, which I believe is the Zooz stick.

    So, good news! I have both Z-Wave and Zigbee working in home assistant now, bypassing all the Ezlo software. The home assistant Zigbee integration connects directly to the Ezlo, and for Z-Wave I have ZWave-JS as an intermediary - but that's hass' recommended configuration anyway.

    I think I've figured out some initial stability issues I was having as a result of not setting socat up quite right, but don't quote me on that yet, and for some reason the status of the Z-Wave controller shows up as 'Dead' but it doesn't seem to matter? Not sure what that's about. Also if I start hass before the Ezlo is ready then it will never successfully connect - you have to run socat on the Ezlo first, then start Home Assistant. Other than that it seems to work well. Zigbee in particular is more stable and responsive in this configuration than it was on the sonoff zigbee bridge I was previously using in my setup.

    Here's how I did all this:

    Using the instructions on the openWrt site, compile socat for the Allwinner H3 SoC (or, if you're feeling trusting, download the binary I already compiled). Copy the .ipk to the Ezlo using whatever method you prefer. I used scp. Unfortunately you can't download the binary directly to the Ezlo because it doesn't support SSL and I don't have anywhere I can share the file from that doesn't enforce secure connections. Install it:
    opkg install socat_1.7.3.3-1_arm_cortex-a7_neon-vfpv4.ipk Kill the running ezlo processes: (One single error at the end about a process that can't be killed because it doesn't exist is expected).
    ps | grep "/ha-" | cut -b1-5 | xargs -t kill Share the Z-Wave and Zigbee radios over the network using socat:
    socat /dev/ttyS1,raw,echo=0 tcp-listen:3333,reuseaddr,keepalive,fork &
    socat /dev/ttyS2,raw,echo=0 tcp-listen:3300,reuseaddr,keepalive,fork & In Z-Wave JS' ZWave settings under serial port, ignore the choices in the dropdown menu and manually enter tcp:// (change the IP to that of your Ezlo) In Home Assistant's Zigbee integration select a radio type of EZSP and for the serial port enter socket:// ... Profit

    If you reboot the Ezlo it returns to its stock setup. I think my plan is to write a little script that checks whether the Ezlo processes are running and, if so, kills them and starts socat, then run that script as a cronjob. @rafale77, do you have any advice on a better approach based on your Nuke-Vera work? I don't want to nuke the Ezlo and do anything irreversible necessarily, but I'm also a little concerned that my plan might be leaving the thing functional enough to one day download a firmware update that breaks what I'm doing.

    If it's helpful to anyone, I also compiled binaries for ser2net (I never got it to work) and Nano.

Recent Topics