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
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
There is an alternative to homebridge-mqttthing
CrilleC
Just throwing out a general hint to the people running Homebridge and MQTT. Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge. I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function. It took a while to migrate everything but I'm pleased and can recommend.
Software
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
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