Hello Vera newcomers! I’m excited to share my journey with Vera and how it’s transforming my smart home experience. As a new user, I’ve been diving into Vera’s features and wanted to address some common questions and share my experiences. Here’s what I’ve discovered so far:
Triggers and Logic
I was curious about how Vera handles triggers—whether they use AND or OR logic. From what I’ve observed, Vera primarily uses OR logic. This means that if any of the conditions in your trigger are met, the associated action will execute. For example, if you set up a trigger that activates when either Motion Sensor A or Motion Sensor B detects movement, the lights will turn on if either sensor is triggered. This is incredibly flexible and allows for a wide range of automation scenarios.
Scenes and Triggers Interaction
Another area I explored was how scenes and triggers interact. Vera allows you to set up scenes with conditions, and these can coexist with triggers. However, it’s important to note that scenes typically take precedence over triggers. If a scene is set up with specific conditions, it will execute those actions regardless of any existing triggers. This hierarchy ensures that your scenes remain the primary automation tools, while triggers can be used for more specific or supplementary actions.
Custom Alert Messages
Customizing alert messages was another topic I looked into. Vera provides a good level of customization for alerts, allowing you to set specific messages for different events. You can adjust the alert text in the device settings or through Vera’s web interface. If you’re using third-party apps or services, you might need to use a custom dashboard or integration to achieve more tailored alerts.
Scheduling
When it comes to scheduling, Vera’s scheduler is quite robust. The ‘after sunset’ schedule typically stops at sunrise, providing a natural cycle for your lighting and other automated devices. However, Vera also allows you to set custom end times if you prefer a different schedule.
Device Type Configuration
I encountered an issue where my door/window sensors were initially detected as motion sensors. This was easily resolved by changing the device type in Vera’s settings. Under the device’s details, there’s an option to set it as a door sensor. Once that’s done, the triggers and automations work as expected. If you’re having trouble setting up triggers, double-check that the device type is correctly configured.
Lua Code Automation
For those looking to dive deeper into automation, Vera’s Lua scripting is a powerful tool. I recently worked on a script to monitor two motion sensors and control a light based on their status. Here’s a simplified version of the code I used:
lua
local SENSOR_LIVE = 25
local SENSOR_DINE = 18
local LIGHT = 4
function turn_on_light()
local tripped1 = luup.variable_get(‘urn:upnp-org:serviceId:SwitchPower1’, ‘Status’, SENSOR_LIVE) or ‘0’
local tripped2 = luup.variable_get(‘urn:upnp-org:serviceId:SwitchPower1’, ‘Status’, SENSOR_DINE) or ‘0’
if tripped1 == '1' or tripped2 == '1' then
luup.call_action('urn:upnp-org:serviceId:Dimming1', 'SetLoadLevelTarget', {newLoadlevelTarget = '80'}, LIGHT)
end
end
– Schedule this function to run after sunset
os.execute([[luup.timer_add(turn_on_light, nil, ‘0 0 * * 0’)]])
This script checks both motion sensors and turns on the light if either detects movement. It also includes a scheduler to run the function after sunset, ensuring the lights come on when needed.
Conclusion
Vera’s flexibility and robust automation capabilities make it a fantastic choice for smart home enthusiasts. Whether you’re setting up simple automations or diving into Lua scripting, Vera offers a wide range of options to suit your needs. If you’re new to Vera, I encourage you to explore its features and don’t hesitate to reach out to the community for support.
Happy automating! 