Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    1. Home
    2. xAPPO
    • Home Assistant add-on

      M

      I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.

      GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon

      Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.

      Multi-System Reactor
    • DelayLight replicate in MSR

      P

      Hi Everyone,

      I am just starting to move over from Vera to Home Assistant using MSR.

      On vera I had been using DelayLight. I have tried to replicate it with help from youtube (https://www.youtube.com/watch?v=fc_ij0D1hXE) Reactor for Vera #006 - Emulating DelayLight in Reactor.

      I have created 6 rules that sort of work. but I am just wondering if this is best practice or should can it be built in 1 rule like the old vera way?

      Multi-System Reactor
    • Having an Echo device play mp3?

      F

      Hi!
      I tried to find an answer in both the forum and by myself, without any luck. I'm trying to make my Echo device play a mp3 file. The same mp3 file is easy to play with other smart speakers (Sonos, Google/Nest) - that it no problem. Same approch do not work with Echo devices. The mp3 files I want to use is located on my HA installation (config/www/audio), running on ver. 2023.5.4. I have MSR ver 23114.
      Is there a way to do this easily?
      Thanks!
      /Fanan

      Multi-System Reactor
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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
    • Sending numbers as payload type in actions enhancement

      J

      I'm controlling a HVAC device through the MQTTController. While setting up the entity config in reactor.yaml, I started with this on the action block:

      set_setpoint: topic: "ezlo_mqtt/set/item/%topic%/set/Tsetpoint" payload: expr: "parameters.setpoint" type: raw

      However, as the setpoint is a number in the UI, things were not fully parseable as a number and nothing was outputted to mqtt.

      So I've added this code to MQTTController.js at line 1449 to add the payload type 'number':

      } else if ( 'number' === act.payload.type ) { payload = String( payload ); } else if (''raw' !== ( act.payload.type || 'raw' ) ) {

      After this change, I was able to set the payload type to number:

      set_setpoint: topic: "ezlo_mqtt/set/item/%topic%/set/Tsetpoint" payload: expr: "parameters.setpoint" type: number

      And things worked as intended, being able to send numbers in the actions bit of a rule set.

      Multi-System Reactor
    • MIOS - UI5 web login

      Black Cat

      Can anyone help with the MIOS UI5 weblink? Not the getvera one.
      Still running UI5 on a couple of sensors & lights and need to tweak PLEG but for the life of me I can't remember the link to tunnel back to the trusty machine....

      General Discussion
    • SiteSensor > how to fill in Value Expressions (json data) SOLVED !

      M

      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
    • openweather plugin ?

      DesT

      Hey guys....

      long time 😉

      Since Dark weather is no more active, thanks Apple. Anyone switch to openweather to get weather data ?

      Plugins
    • Smart devices and mesh

      J

      The wifi on my router is turned off, and wifi around the house is provided using a mesh - 3 units altogether (one connected directly to the router) that are spread around the house.

      I would like to start automating certain tasks around the house and intend to try adding a few smart sockets to my setup.

      The mesh system I have supports both 2.4GHz and 5GHz, and does not provide me with the option to control them - i.e. turn one or both on/off, give each a different SSID, etc.

      The devices I wish to purchase/use only support 2.4GHz.

      Will turning the mesh units off and temporarily turning the 2.4GHz wifi on the router to allow me to set them up be enough? Will I then be able to return to my usual setup and everything will work as it should?

      Many thanks in advance

      General Discussion
    • Smart bed sensor

      C

      Hey everyone, I'm currently working on developing a bed sensor that can detect when you're out of bed. It could be used to trigger other smart home gadgets, like lights or blinds, temperature etc.
      The sensors are placed under the legs of your bed post. Should look and feel like "smart furniture pads" with size 2 inches in diameter and 1/4 inch thick.
      Before we go any further, I'd love to get your thoughts on this - would a bed sensor like this be something you'd find useful? We're still in the early stages of development, so any feedback you have would be greatly appreciated. Thanks in advance!

      smart möbeltass.JPG

      General Discussion
    • JSON payload in MQTTController entities actions (+ reverse color mapping to RGB)

      M

      Some background
      I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:

      switch (on/off) brightness color

      I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:

      expr: 'payload.brightness / 254'

      Here's the entity definition (don't know whether the type should be something else than the Switch)

      zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlight

      And the corresponding template (NOTE: rgb_color has not been defined in this example):

      lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'

      The problem
      In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.

      But the brightness should be controlled with the following payload:

      {"brightness": 196}

      And the RGB color like:

      {"color":{"rgb":"46,102,150"}}

      Here's the link for the documentation (the Exposes part defines the messages).

      So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.

      actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: json

      Another problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.

      Here's an example of published message after setting the color:

      Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }

      I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?

      Help would be appreciated @toggledbits
      br,
      mgvra

      Multi-System Reactor
    • Another Vera --> Home Assistant migration question

      T

      Good morning all,
      I've got a stable Home Assistant running on a RPI 4 with a Aeotec Z-Stick 7 Plus, and of course the Z-wave JS integration. I've manually moved a handful of devices, and I'm overall much happier with the HA z-wave capability than I am with Vera. There are still some things I'm trying to figure out that I have in Vera that I'm not sure how they'll work in HA, but no deal breakers.

      I've got all of my automation on MSR and off of luup Reactor, so really the only thing left for me is to migrate my Z-wave network. I saw @rafale77's post about using a Zwave.me UZB1 to Zway, but of course that's not what I'm using.

      Is there a similar method that I can use my Aeotec Z-Stick 7 plus to Home Assistant? I have around 70 Z-wave devices (give or take devices that generate multiple instances in Vera), so manual unpairing, including, etc, would be quite a chore.

      Vera
    • Home Assistant push notification for Reactor version update possible?

      T

      Good evening,
      I was wondering if it would be possible to send out a push notification when there is a update to MSR to HA users. I know how to set up notifications through Reactor to HA users, but I'm unsure what to look for in regards to updates. I know that MSR itself will tell me there is an update, but unless I'm logged into MSR in a browser, I'm not always going to see that.

      Just updated to latest-23114-e4060aae MSR
      Home Assistant 2023.4.6
      Supervisor 2023.04.1
      Operating System 10.0

      Multi-System Reactor
    • ChatGPT - finally I can now retyre in piece and quite, knowing everting is in goof hands.

      A

      ChatGPT samples:

      Me:

      Tell me about an iot program called openLuup.

      It:

      OpenLuup is an open source home automation system that is built on the VeraLuup platform. It is designed to be easy to install and configure, and provides users with a powerful and versatile way to control their home automation devices. OpenLuup offers a wide range of features, including support for many popular home automation devices, scheduling, scripting, and integration with other services. OpenLuup is designed to be customizable, allowing users to create their own home automation systems. It is an excellent choice for those looking to create their own home automation system without spending a lot of money.

      Me:

      Write an iot program using openLuup.

      It:

      --openLuup IoT Program-- -- Initialize Variables -- local device_id = "MyHomeDevice" local temperature_sensor_id = "MyTemperatureSensor" local temperature_threshold = 75 -- Create Devices -- luup.create_device("OpenLuup Temperature Sensor", 0, device_id, "D_GenericSensor1.xml", "I_GenericSensor1.xml", "S_TemperatureSensor1.xml", "") luup.variable_set("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 0, device_id) -- Start Timer -- luup.call_delay("check_temperature", 10, "", false) --Function to Check Temperature-- function check_temperature() local current_temperature = luup.variable_get(temperature_sensor_id, "CurrentTemperature", 0) --Check Temperature Threshold-- if current_temperature >= temperature_threshold then --Send Alert-- luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "SendTextMessage", {PhoneNumber="1234567890", Message="ALERT! Temperature exceeded threshold!"}, 0) end --Reset Timer-- luup.call_delay("check_temperature", 10, "", false) end

      Me:

      Write an iot program using openLuup.

      It:

      Write an iot program using openLuup. -- openLuup IOT Program -- -- Variables local lampState = false local lampTime = 0 -- Functions function lampTimer() if lampTime > 0 then lampTime = lampTime - 1 if lampTime == 0 then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 0, lampDeviceID) lampState = false end end end -- Setup luup.call_delay('lampTimer', 60, 0) -- Main Loop while true do -- Check for motion if luup.variable_get('urn:micasaverde-com:serviceId:MotionSensor1', 'Tripped', motionSensorDeviceID) == '1' then if not lampState then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 1, lampDeviceID) lampState = true -- Set lamp timer to 5 minutes lampTime = 300 end end luup.sleep(1) end

      What??

      luup.sleep(1)

      Not good - looks like I still have some semblance of a job to fulfill.

      Me:

      An iot program called openLuup was written by akbooer. Who is akbooer?

      It: (note: answer redacted and as I understand it, also incorrect re: AltUI):

      akbooer is the pseudonym of the software developer and home automation enthusiast. He is the creator of the openLuup home automation software, which is an open-source version of the Vera home automation system. He is also the creator of the AltUI graphical user interface for openLuup.

      Me:

      Who created of the AltUI graphical user interface for openLuup.

      and

      Me:

      Who created of the AltUI graphical user interface for the home automation system Vera.

      Names two different people - mmmm.

      Regardless very impressive - give it a few more years.

      General Discussion
    • Disabled groups in reactions

      tunnus

      MSR tooltip says that "disabled groups are ignored, as if they did not exist (conditions don't run)".

      Just want to clarify if it's by design that actions beneath disabled groups should run? They do run, but intuitively I was expecting them to be disabled as well.

      Running the latest build under Docker.

      Multi-System Reactor
    • Any interest in a Subcategory for Homebridge?

      parkerc

      Being an iPad/iPhone user, I use Homebridge for a number of things. Although it runs completely independently from my main Vera home set up.

      Is anyone else using Homebridge and if there is enough interest would a subcategory be of use ?

      Software
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
    X
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 19
    • Best 4
    • Controversial 0
    • Groups 0

    xAPPO

    @xAPPO

    7
    Reputation
    4
    Profile views
    19
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    xAPPO Unfollow Follow

    Best posts made by xAPPO

    • RE: MQTT interface... time for some testing. Where are my experts?

      All working well. However in the topic structure for echoed devices (from Hubitat anyway) the <entity-id> is used. Is it possible to instead or even better as well as, include the entity-name ?

      reactor/<mqtt-id>/<ctrl-id>/<entity-id>/state/<capability-name>
      

      perhaps

      reactor/<mqtt-id>/<ctrl-id>/<entity-name>/<entity-id>/state/<capability-name>
      
      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      It's like having my own on site developer team 🙂 Many thanks for that

      posted in Multi-System Reactor
      X
      xAPPO
    • MQTT - add rules support ?

      I'm thinking that a useful feature in MQTT would be a topic entry for each rule within Reactor and their current state set or reset updating in real time.

      reactor/rules/myRule1  = reset
      reactor/rules/myRule2  = set
      

      Additionally a topic available that could trigger the rule from MQTT.

      reactor/rules/myRule1/trigger  = set
      

      I would have to think about whether this would trigger the rule always or only if other triggers are also satisfied or an option for either. I would like to avoid manually adding the MQTT payload value as a trigger into each and every rule to achieve this. Maybe I should look at this from Reactions perspective.

      What do you think ?

      New to Reactor but Im assuming an event is available to MQTT code that would advise when rules set and reset and a call available to trigger them manually, perhaps bypassing triggers ?

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MSR support for openHAB?

      I read that both OpenHAB and Homey were being worked on although the expected date has slipped a little. I’m interested in both. It’s part of the reason I’m evaluating Reactor MH at the moment.

      You can interact with both of those currently via MQTT but having a tighter integration with entity discovery would be really nice.

      posted in Multi-System Reactor
      X
      xAPPO

    Latest posts made by xAPPO

    • MQTT - add rules support ?

      I'm thinking that a useful feature in MQTT would be a topic entry for each rule within Reactor and their current state set or reset updating in real time.

      reactor/rules/myRule1  = reset
      reactor/rules/myRule2  = set
      

      Additionally a topic available that could trigger the rule from MQTT.

      reactor/rules/myRule1/trigger  = set
      

      I would have to think about whether this would trigger the rule always or only if other triggers are also satisfied or an option for either. I would like to avoid manually adding the MQTT payload value as a trigger into each and every rule to achieve this. Maybe I should look at this from Reactions perspective.

      What do you think ?

      New to Reactor but Im assuming an event is available to MQTT code that would advise when rules set and reset and a call available to trigger them manually, perhaps bypassing triggers ?

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: [SOLVED]. Build 22021-f83a39c Status page is blank

      @toggledbits Sorry - your support is too on the ball 👍 - I had deleted the post as I realized it was non sensical and created a new post

      posted in Multi-System Reactor
      X
      xAPPO
    • Recently Changed Entities doesn't update on 22021

      The recently changed entities no longer updates when added to the status page. It does display some initial entries. Other widgets do update as do Entities. (Docker)

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MSR support for openHAB?

      I read that both OpenHAB and Homey were being worked on although the expected date has slipped a little. I’m interested in both. It’s part of the reason I’m evaluating Reactor MH at the moment.

      You can interact with both of those currently via MQTT but having a tighter integration with entity discovery would be really nice.

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      @toggledbits said in MQTT interface... time for some testing. Where are my experts?:

      Did you find the probably dated but maybe marginally helpful docs here?

      Yes I did .. a quick Q - how do I delete an entity ?

      The bit I'm adding currently is

      If the process may be protracted and lengthy, the Promise should resolve earlier and the entities by published as discovered.

      and trying to avoid having to loop through them all on restarts to see if they already exist. This is an aspect that you must have encountered with Hubitat and Hass.

      Making good progress and enjoying it .. great application.

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      I notice in the MQTT code you subscribe to the root level with a wildcard which means you receive every payload update. On my (untypical) broker this will produce 10’s of message per second. The good thing is Reactor seems to handle it but obviously it’s resource wasteful. Did you do this with a view to implementing discovery across the broker perhaps?

      Currently it might seem better to just pull the necessary topics from the MQTTController section of reactor.yaml even though this may result in lots of individual subscribes?

      Also just to mention I’ve got my first CBusController half written. It discovers and creates entities for all the 100+ lights I have on my Schneider C-Bus lighting but needs some refining. Learning as I go. Having the MQTT code as an example has been invaluable to me.

      Would you be up to releasing the Hubitat and HomeAssistant controller code as examples? I think that would help people in authoring new controllers, as might a minimal code template that does nothing really.

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      It's like having my own on site developer team 🙂 Many thanks for that

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      This is working well - thank you for the prompt update.

      For me having the <entity-name> before <entity-id> in the topic hierarchy would have been more informative as you can then see a list of names rather than numbers in expanded topics with say MQTT explorer rather than having to drill down in each one, but I totally understand why it is so much easier in terms of your existing implementation to position it afterwards and this is very workable too.

      70bebe6f-d981-4b60-93da-dade10eed90c-image.png

      Thank you again.
      Kevin

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      The incoming action request message to a topic must be complete with all segments as you can't wildcard a publish command. So the <entity-id> will always be unique and present there. You could should you wish subscribe to the topic from your code ignoring any <entity-name> segment with a + wildcard as you don't process it. So that should work fine.

      Human readability.. I agree it's a bit of a reach but my whole system is MQTT based with over 10K topics and 1K+ devices - remembering what they all are and linking to or from those topics from other controllers requires some hints as to what those devices are. Later examination of logic requires understanding what devices are related. Having to refer back to Reactor config each time to identify a device isn't practical (or user friendly).

      posted in Multi-System Reactor
      X
      xAPPO
    • RE: MQTT interface... time for some testing. Where are my experts?

      Topic hierarchy segments don't have to be unique - in fact I would say most aren't. Keeping the <entity-id> then within the hierarchy would ensure the topic remains unique. Having no easily human identifiable topic is not helpful to other integrations.

      posted in Multi-System Reactor
      X
      xAPPO