Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
M

Maipensato

@Maipensato
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
Multi-System Reactor
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
About
Posts
20
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Migration Vera to HA > how to send sensor data from Vera to HA?
    M Maipensato

    @gwp1 I have no doubts that MSR is a great tool for sure when you use more than one platform.
    But sorry I repeat myself... my goal is to only use Home Assistant in the near future and I will migrate step by step from Vera.
    If I can not do all automations in HA I will most certainly seriously consider combining HA with MSR.

    In the meantime I have found the answers on my question myself.

    http luup request to get values of sensor data/variables from Vera.
    Example for a rain sensor:

    http://192.168.1.xxx:3480/data_request?id=variableget&DeviceNum=xx&serviceId=urn:upnp-org:serviceId:RainSensor1&Variable=CurrentRain

    Within Home Assistant I created RESTful sensors to get the data in.

    And it works great.

    Home Assistant

  • Migration Vera to HA > how to send sensor data from Vera to HA?
    M Maipensato

    Another option (maybe more simple? is to retrieve the sensor data from Vera within Home Assistant.

    This is the code to switch on a switch:

    http://192.168.1.xxx:3480/data_request?id=lu_action&output_format=xml&DeviceNum=185&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1

    How do I get the CurrentLevel of a temperature sensor:
    serviceId = =urn:upnp-org:serviceId:TemperatureSensor1
    How to define the action ?

    Home Assistant

  • Migration Vera to HA > how to send sensor data from Vera to HA?
    M Maipensato

    @Crille @gwp1 Thanks for your quick replies and recommendations.
    For sure I have considered MSR. Reasons why I did not opt for this:

    1. in the end I want to do everything within HA incl UI so transferring data from Vera to HA is temporary . HA offers a huge amount of integrations and a big community of users and developers
    2. I run the all inclusive HA OS on a HP thin client. I know there is a Reactor for Home Assistant add-on but read there are issues with it
    3. Switching from the Vera Reactor to MSR is doable but takes time and it is different. The biggest disadvantage in my case is that MSR can not handle LUA code and my most complex Reactors use quite some LUA code

    So this is why I opened a topic here with my specific question.

    Any help /'advice ?

    Home Assistant

  • Migration Vera to HA > how to send sensor data from Vera to HA?
    M Maipensato

    Hi,

    I started home automation in 2013 and using Vera controllers from the start. When Reactor plugin became available (super plugin of @toggledbits !!) I transferred all scenes to Reactor.
    I must say everything here works still okay and I have a lot of devices, plugins and Reactors. But I fear at some point my Vera's will stop working.
    I recognize many of your names here from the Vera forum. I also was banned a couple of years ago.
    Recently I decided to switch to Home Assistant. I already transferred some of my zwave devices from Vera to HA and made some new automations.
    I must say HA is great and with huge amount of integrations, add-ons, the HACS store and many examples (like blueprints) the opportunites to increase home automation are huge.
    HA will be for sure my central system (incl UI)

    But... the learning curve is quite steap (YAML is completely different from Lua/luup).
    So for the time being I will keep my most complex Reactor automations.
    I already found how I can connect/integrate Vera for binairy sensors via webhooks (as an example: changes in my home modes are directly send from Vera to HA).

    Now I also want to use some data like sensors or Reactor variables automatically to HA via https requests (put those in Reactor).
    I know I can create virtual sensors in HA via templates.

    As an example: I have my own PWS with a rainmeter. In Reactor I compare the amount of rain (in mm) in the actual year with historical figures (past 15 years) and calculate the difference actual vs history in % Every day at 0.00h these figures are updated. I defined variables in Reactor and use Multistring plugin (Variable container) to show the data.

    I know several specialists in coding with experience in both Vera and HA are active here on this forum.

    Who can help me with this ?

    Home Assistant

  • SiteSensor > how to fill in Value Expressions (json data) SOLVED !
    M Maipensato

    Well.... I tried again with "response.lastDayData.energy" and now it works ?? Really don't know what I did wrong, but now it works.

    So problem solved.
    Many thanks @akbooer

    Vera/openLuup plugins

  • SiteSensor > how to fill in Value Expressions (json data) SOLVED !
    M Maipensato

    Thanks!

    So why does the 2nd option I have mentioned not work?

    Vera/openLuup plugins

  • SiteSensor > how to fill in Value Expressions (json data) SOLVED !
    M Maipensato

    I still use Vera controllers in combination with ReactorSensors. I have several Reactor sensors in use to retrieve weather data from Wunderground (i have a personal weather station), my smartmeter etc.

    Recently I installed solar panels with a SolarEdge inverter. SolarEdge has an API to retrieve my power production data from their cloud.
    Output is in json.

    So I created a new Reactor Sensor. Connection is working (query okay).
    But I encounter problems at the Value Expressions. Either I get ""query okay" but no data or I get "query okay but 1 expressions failed"

    This is the json output

    {"overview":{"lastUpdateTime":"2023-05-12 10:45:57","lifeTimeData":{"energy":476310.0,"revenue":216.577},"lastYearData":{"energy":433001.0},"lastMonthData":{"energy":433001.0},"lastDayData":{"energy":8262.0},"currentPower":{"power":5647.0},"measuredBy":"INVERTER"}}
    

    So it has different layers/levels.

    I tried to put in the Value Expressions field several combinations to get the energy data of today (8262.0), like:

    response.lastDayData.energy
    response.overview.lastDayData.energy
    response.overview.lastUpdateTime.lastDayData.energy

    all fail...

    Who can help me with this ?

    Vera/openLuup plugins

  • Netatmo – Oath2 login
    M Maipensato

    @akbooer Does this update also work for Vera controllers without using openluup or Altui?

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    @toggledbits Okay clear, thanks for your quick reply!

    What about SiteSensor and select response type Generic (text). How can I define a "response pattern to match" in the next field.

    It's good to know it's possible within Reactor Sensor but it would be easier (I hope...) to solve it within SiteSensor.

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    @akbooer many thanks !
    Good to know this is possible.
    I doubt wether I can use this within SiteSensor.

    But I think I can use this within the Reactor plugin with some adaptions in the Lua code. It would have to send the invididual sensor data to the virtual weathersensors like every 30 or 60 seconds.

    Or use it within MSR when I would decide to migrate partially of completely from Vera to HA or Hubitat.

    @toggledbits can I use this kind of script within SiteSensor ? Hope you can help me in the right direction.

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    This is on Vera.
    xml output:

    <logger>
    <TH date="20221204143607" id="th0" temp="3.7" hum="84" dew="1.2" lowbat="1"/>
    <WIND date="20221204143606" id="wind0" dir="22" gust="1.7" wind="1.7" chill="1.5" lowbat="0"/>
    <THB date="20221204143541" id="thb0" temp="9.3" hum="59" dew="1.7" press="1016.0" seapress="1016.0" fc="0" lowbat="0"/>
    </logger>

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    @toggledbits My PWS uploads data to Wunderground via a Meteobridge device. I just found out I can retrieve live data of my weatherstation via a http request to Meteobridge. So this is a way to to get my weatherdata in Vera via SiteSensor plugin. Without being dependent on external cloudservers like Wunderground.

    The only issue is the output is not available in json, only in xml format or plain text. I see that you can select the response type Generic (text) but then you have to define a "response pattern to match" in the next field.
    I went though the SiteSensor thread on the Vera forum and found lots of examples for json output but none for generic text output.

    The output of the Meteobridge URL looks like:

    20221204112238 th0 3.4 84 0.9 1
    20221204112301 wind0 112 1.3 1.3 1.5 0
    20221204112241 thb0 9.4 59 1.8 1017.0 1017.0 0 0

    where first is time stamp, then device id and then all the data.
    th0 = temp/hum sensor 3.4 is temp (Celsius) 84 is hum% 0.9 is dewpoint and 1 = lowbat

    Can you help me in how to get for example temp and hum values; what should I put in the field "enter pattern to match"

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    @toggledbits Many thanks for your quick reply! Putting UseCurl on 1 made it working again!
    So for now I'm saved.

    Now I really have to start looking for another smarthome setup. I now have quite an extensive setup with 3 Vera controllers (Secure and Plus) with a lot of Reactor Sensors and Site Sensors etc. and also a Fibaro HC2 controller.
    And I use the Home Remote app that works with both Vera and Fibaro.
    I put a lot of hours in it to set this all up and adapt it to my wishes and I must say it works (almost) rocksolid past 2 years.

    Have to spend quite some time first to look at all the alternatives coming months. For sure I will find useful information here on this forum (e.g. Home Assistant in combination with your MSR)

    Vera/openLuup plugins

  • SiteSensor: get data from Wunderground suddenly stopped
    M Maipensato

    I use the excellent SiteSensor plugin of @toggledbits for some years to get the data from my PWS on Wunderground.
    This has worked flawlessly but recently it suddenly stopped working.
    I see this in my Vera:

    6899a8b1-ad67-430a-9dc8-f1da42b04b62-image.png

    When I copy/paste the URL code to be queried in my browser this still works.

    This is the URL:
    https://api.weather.com/v2/pws/observations/current?stationId=ILIMBURG130&format=json&units=m&numericPrecision=decimal&apiKey=xxxxxxxxxxxxxxxxxxxxxxxxx

    Patrick (or someone else on this forum) can you help me solve this ?
    Many thanks in advance!

    Vera/openLuup plugins

  • Netatmo – Oath2 login
    M Maipensato

    Any update? October is approaching..

    Vera/openLuup plugins

  • Netatmo – Oath2 login
    M Maipensato

    I also use the Netatmo plugin, not on openLuup but still using Vera. I really hope you can and are willing to update the app.

    Vera/openLuup plugins

  • Vera Decoupled from the cloud services
    M Maipensato

    @rafale77 thanks I will read that first

    openLuup

  • Vera Decoupled from the cloud services
    M Maipensato

    Ok thank you @therealdb and @rafale77 I have to dig in to how to set up an openVPN server. This is really new to me (meaning I'm not an expert ..😢).
    I have a Unify Dreammachine router.

    @therealdb: do you think Vera will release the 7.32 firmware coming weeks ? They have promised end last year it should be released already in January....

    openLuup

  • Vera Decoupled from the cloud services
    M Maipensato

    I seriously consider to decouple my Vera's from the Vera cloud services. In case they shut the servers down in the near future. You never know....
    I have read the readme document on @toggledbits.
    And have two questions.
    First of all I will lose remote access (via their cloud service). This is a big disadvantage for me. I used Imperihome app in the past to check and if needed control some devices or start some scenes also when I'm not at home. Now I use TheHomeRemote app and this works very well to controll my Vera's and Fibaro Home Center remotely. Good chance I will cange to MSR in the near future.
    To make this possible after decoupling my Vera's I need to use port forwarding. I have read on the Vera forum that some users advice not to do this because it is not safe. After some further googling I find very contradictive opinions wether using port forwarding is safe or not.
    So what is the opinion of the experts on this forum? Is it really not safe and why ? How can I reduce the safety risks ?

    Second question: should I wait for the upcoming 7.32 firmware update of Vera (I know some of you are beta testing this), is it wortwile?

    openLuup

  • Vera account suspended for a 1000 years
    M Maipensato

    Well....since this morning I cannot login to the vera forum anymore.. Account suspended for 1000 years. No warnings at all. What a joke....The almighty dictator that cannot endure any criticism and breaks every forum rule himself again proves what kind of person he is. Really unbelievable his recent behaviour towards rigpapa and akbooer !! Well I don't bother at all. Seeing the lack of progress in Ezlo controllers these will not be part of my (future) home automation system.
    @toggledbits: I liked your reactions towards the dictator (probably the reason he suspended me) and I really fully behind you !!
    @akbooer: ridiculous that the dictator calls you a thief (you stole away "his"customers). He'\s very good in chasing them all away himself.

    I use Vera controllers for almost 8 years now. Honestly I'm quite happy with how they function right now. Thanks to the great research and tips of @rafale77 and switching all my scenes to the magnificent Reactor plugin it is now working (although with on average 1 luup reload per day). My setup is quite complex and next to a lot of zwave devices I also use the plugins for e.g. Hue, Sonos, Netatmo, Milight, RFXcom, smartmeter, Datamine2. For short term I will consider decoupling my Veras from the Vera servers and/or start using Openluup. First dig in to this a little more, I already noticed this forum is very informative about all the options.

    I think much more members are banned now from the vera forum. Because if they ban me for liking the posts of rigpapa.... well I was not the only one.
    @toggledbits: are you still allowed by the almighty dictator?

    Vera
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved