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

mrFarmer

@mrFarmer
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
About
Posts
104
Topics
6
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • RFC: When disaster strikes (sorry it's a bit verbose)
    M mrFarmer

    Using the USB ports on a Synology looks to be a pain for anything else than storage. There are hacks around, but nothing officially supported I could find. So that is why I opted for Hubitat as that seems to be pretty stable for my needs (nothing cutting edge on that front). O and I did add more memory in my NAS too, not original Synology as that is insainly expensive.

    General Discussion

  • RFC: When disaster strikes (sorry it's a bit verbose)
    M mrFarmer

    I put what I could on containers on my NAS, and use Hubitat for Zwave. For the latter you can buy a full backup/restore subscription. The containers I could spin up on a PI (4 or better with at least 4GB memory and SSD) rather quickly if needed. I did not use containers prior, but the simplicity and quickness to get those running with existing data has made using them over bare metal a no-brainer.

    As my NAS is fairly new and the data should not go lost in case it does go belly up. I am not too concerned about the data. Just the ability to run the containers using the same IP addresses.

    But your right. Having it go down for even a day or two (ordering a new NAS and restoring everything) would have a serious impact on the WAF for months after. So you now got me thinking too....

    Cheers Rene

    General Discussion

  • [SOLVED]Hass websocket falsely reporting ready on boot??
    M mrFarmer

    @vezinpi Correct the will no longer show after a restart has completed and a browser refresh. It just feels counter intuitive. Without the wait, no messages, with the wait error messages, even if there is no negative effect on how reactor functions.

    Multi-System Reactor

  • [SOLVED]Hass websocket falsely reporting ready on boot??
    M mrFarmer

    Yes, clear status messages. Click reload. Wait until I see Connected and then go to the status page to see them in alerts.

    Multi-System Reactor

  • [SOLVED]Hass websocket falsely reporting ready on boot??
    M mrFarmer

    As I sometimes seen the Controller off-line message I thought to give this a try. Added wait_all_controllers and startup_wait. When I then restart Reactor in Tools, I get a controller offline in the status window for all controllers!?! All of them are up as I am only touching reactor. I took the two options out again and status messages gone. Oddly in the reactor.log no message about off-line controllers.

    [latest-25016]2025-02-07T09:08:01.620Z <app:null> Reactor build latest-25016-d47fea38 starting on v22.12.0 /usr/local/bin/node
    [latest-25016]2025-02-07T09:08:01.620Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #72806 SMP Thu Sep 5 13:41:01 CST 2024; locale (undefined)
    [latest-25016]2025-02-07T09:08:01.621Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
    [latest-25016]2025-02-07T09:08:01.621Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
    [latest-25016]2025-02-07T09:08:01.644Z <app:null> Resolved timezone=Europe/Amsterdam, environment TZ=Europe/Amsterdam; offset minutes from UTC=60
    [latest-25016]2025-02-07T09:08:01.647Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
    [latest-25016]2025-02-07T09:08:01.664Z <app:null> Loaded locale en-US for en-US
    [latest-25016]2025-02-07T09:08:01.665Z <app:null> Local date/time using configured timezone and locale formatting is "2/7/2025, 10:08:01 AM"
    [latest-25016]2025-02-07T09:08:01.714Z <Structure:null> Module Structure v24287
    [latest-25016]2025-02-07T09:08:01.716Z <Capabilities:null> Module Capabilities v24312
    [latest-25016]2025-02-07T09:08:01.736Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 25004 revision 1
    [latest-25016]2025-02-07T09:08:01.747Z <Plugin:null> Module Plugin v22300
    [latest-25016]2025-02-07T09:08:01.767Z <TimerBroker:null> Module TimerBroker v22283
    [latest-25016]2025-02-07T09:08:01.770Z <Entity:null> Module Entity v25014
    [latest-25016]2025-02-07T09:08:01.773Z <Controller:null> Module Controller v25014
    [latest-25016]2025-02-07T09:08:01.784Z <default:null> Module Ruleset v24288
    [latest-25016]2025-02-07T09:08:01.784Z <default:null> Module Rulesets v24220
    [latest-25016]2025-02-07T09:08:01.789Z <GlobalExpression:null> Module GlobalExpression v24209
    [latest-25016]2025-02-07T09:08:01.800Z <Predicate:null> Module Predicate v24350
    [latest-25016]2025-02-07T09:08:01.806Z <AlertManager:null> Module AlertManager v24099
    [latest-25016]2025-02-07T09:08:01.809Z <Rule:null> Module Rule v24329
    [latest-25016]2025-02-07T09:08:01.813Z <GlobalReaction:null> Module GlobalReaction v24220
    [latest-25016]2025-02-07T09:08:01.814Z <Engine:null> Module Engine v24344
    [latest-25016]2025-02-07T09:08:01.819Z <httpapi:null> Module httpapi v24298
    [latest-25016]2025-02-07T09:08:01.831Z <wsapi:null> Module wsapi v25016
    [latest-25016]2025-02-07T09:08:01.832Z <app:NOTICE> Starting Structure...
    [latest-25016]2025-02-07T09:08:01.855Z <InfluxFeed:null> Module InfluxFeed v23341
    [latest-25016]2025-02-07T09:08:01.857Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed)
    [latest-25016]2025-02-07T09:08:01.857Z <Structure:INFO> Structure#1 loading controller interface openLuup (VeraController)
    [latest-25016]2025-02-07T09:08:01.881Z <TaskQueue:null> Module TaskQueue 24138
    [latest-25016]2025-02-07T09:08:01.924Z <VeraController:null> Module VeraController v25014
    [latest-25016]2025-02-07T09:08:01.979Z <Structure:INFO> Structure#1 loading controller interface hubitat-C8 (HubitatController)
    [latest-25016]2025-02-07T09:08:01.995Z <HubitatController:null> Module HubitatController v24355
    [latest-25016]2025-02-07T09:08:02.035Z <Structure:INFO> Structure#1 loading controller interface hubitat-C7 (HubitatController)
    [latest-25016]2025-02-07T09:08:02.048Z <Structure:INFO> Structure#1 loading controller interface hass (HassController)
    [latest-25016]2025-02-07T09:08:02.057Z <HassController:null> Module HassController v25010
    [latest-25016]2025-02-07T09:08:02.282Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController)
    [latest-25016]2025-02-07T09:08:02.288Z <DynamicGroupController:null> Module DynamicGroupController v24279
    [latest-25016]2025-02-07T09:08:02.291Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
    [latest-25016]2025-02-07T09:08:02.294Z <SystemController:null> Module SystemController v24279
    [latest-25016]2025-02-07T09:08:02.298Z <Structure:INFO> Starting controller VeraController#openLuup
    [latest-25016]2025-02-07T09:08:02.298Z <VeraController:NOTICE> VeraController#openLuup starting...
    [latest-25016]2025-02-07T09:08:02.298Z <Structure:INFO> Starting controller HubitatController#hubitat-C8
    [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller HubitatController#hubitat-C7
    [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller HassController#hass
    [latest-25016]2025-02-07T09:08:02.299Z <HassController:NOTICE> HassController#hass starting...
    [latest-25016]2025-02-07T09:08:02.299Z <Structure:INFO> Starting controller DynamicGroupController#groups
    [latest-25016]2025-02-07T09:08:02.301Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online.
    [latest-25016]2025-02-07T09:08:02.301Z <Structure:INFO> Starting controller SystemController#reactor_system
    [latest-25016]2025-02-07T09:08:02.302Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
    [latest-25016]2025-02-07T09:08:02.367Z <Engine:null> [Engine]Engine#1 config [Object]{ "enabled": true, "wait_all_controllers": true, "startup_wait": 60000, "monitored_entities": [ "vera>device_XXX" ] }
    [latest-25016]2025-02-07T09:08:02.371Z <VeraController:INFO> VeraController#openLuup performing one-time initialization for VeraController class
    [latest-25016]2025-02-07T09:08:02.378Z <Controller:INFO> VeraController#openLuup loaded vera capabilities ver 22253 rev 1 format 1 
    [latest-25016]2025-02-07T09:08:02.398Z <Controller:INFO> VeraController#openLuup loaded implementation data ver 25014 rev 1 format 1 
    [latest-25016]2025-02-07T09:08:02.398Z <HubitatController:INFO> HubitatController#hubitat-C8 performing one-time initialization for HubitatController class
    [latest-25016]2025-02-07T09:08:02.399Z <Controller:INFO> HubitatController#hubitat-C8 loaded hubitat capabilities ver 24279 rev 1 format 1 
    [latest-25016]2025-02-07T09:08:02.407Z <Controller:INFO> HubitatController#hubitat-C8 loaded implementation data ver 24345 rev 1 format 1 
    [latest-25016]2025-02-07T09:08:02.407Z <HassController:INFO> HassController#hass performing one-time initialization for HassController class
    [latest-25016]2025-02-07T09:08:02.408Z <Controller:INFO> HassController#hass loaded hass capabilities ver 25004 rev 1 format 1 
    [latest-25016]2025-02-07T09:08:02.414Z <Controller:INFO> HassController#hass loaded implementation data ver 25004 rev 2 format 1 
    [latest-25016]2025-02-07T09:08:02.417Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
    [latest-25016]2025-02-07T09:08:02.421Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.178.201:8123/api/websocket
    [latest-25016]2025-02-07T09:08:02.424Z <app:NOTICE> Waiting for controllers to start up...
    [latest-25016]2025-02-07T09:08:02.429Z <HubitatController:NOTICE> HubitatController#hubitat-C8 performing initial connection and inventory
    [latest-25016]2025-02-07T09:08:02.430Z <HubitatController:NOTICE> HubitatController#hubitat-C7 performing initial connection and inventory
    [latest-25016]2025-02-07T09:08:02.444Z <HassController:NOTICE> HassController#hass connected, starting protocol
    [latest-25016]2025-02-07T09:08:02.445Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.178.201:8123; fetching initial data...
    [latest-25016]2025-02-07T09:08:02.490Z <HassController:INFO> HassController#hass Hass reports version "2025.2.0" location Home timezone Europe/Amsterdam state RUNNING safe_mode false
    [latest-25016]2025-02-07T09:08:02.493Z <HassController:ERR> HassController#hass reported Hass version "2025.2.0" is not supported!
    [latest-25016]2025-02-07T09:08:02.519Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant
    [latest-25016]2025-02-07T09:08:02.528Z <HassController:NOTICE> HassController#hass no signature match for sun.sun
    [latest-25016]2025-02-07T09:08:02.535Z <HassController:NOTICE> HassController#hass no signature match for tts.google_en_com
    [latest-25016]2025-02-07T09:08:02.536Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_4
    [latest-25016]2025-02-07T09:08:02.536Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_3
    [latest-25016]2025-02-07T09:08:02.537Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_1
    [latest-25016]2025-02-07T09:08:02.537Z <HassController:NOTICE> HassController#hass no signature match for event.hue_switch_1_button_2
    [latest-25016]2025-02-07T09:08:02.561Z <HassController:NOTICE> HassController#hass no signature match for update.hacs_update
    [latest-25016]2025-02-07T09:08:02.562Z <HassController:NOTICE> HassController#hass no signature match for update.entso_e_transparency_platform_update
    [latest-25016]2025-02-07T09:08:02.563Z <HassController:NOTICE> HassController#hass no signature match for update.hubitat_update
    [latest-25016]2025-02-07T09:08:02.564Z <HassController:NOTICE> HassController#hass no signature match for update.power_flow_card_update
    [latest-25016]2025-02-07T09:08:02.564Z <HassController:NOTICE> HassController#hass no signature match for update.apexcharts_card_update
    [latest-25016]2025-02-07T09:08:02.574Z <HassController:NOTICE> HassController#hass no signature match for update.netdrive_dsm_update
    [latest-25016]2025-02-07T09:08:02.605Z <HassController:NOTICE> HassController#hass no signature match for event.sun_screens
    [latest-25016]2025-02-07T09:08:02.615Z <HassController:NOTICE> HassController#hass no signature match for remote.woonkamer
    [latest-25016]2025-02-07T09:08:02.642Z <HassController:NOTICE> HassController#hass no signature match for update.fritz_box_5590_fiber_fritz_os
    [latest-25016]2025-02-07T09:08:02.647Z <HassController:NOTICE> HassController#hass no signature match for event.garage_door_motor_button_1
    [latest-25016]2025-02-07T09:08:02.647Z <HassController:NOTICE> HassController#hass no signature match for event.garage_door_motor_button_2
    [latest-25016]2025-02-07T09:08:02.686Z <HassController:NOTICE> HassController#hass no signature match for hubitat.hub
    [latest-25016]2025-02-07T09:08:02.688Z <HassController:NOTICE> HassController#hass no signature match for image.fritz_box_5590_fiber_rbguestaccess
    [latest-25016]2025-02-07T09:08:02.764Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged
    [latest-25016]2025-02-07T09:08:02.770Z <Controller:NOTICE> Controller HassController#hass is now online.
    [latest-25016]2025-02-07T09:08:02.779Z <HubitatController:INFO> HubitatController#hubitat-C7 Maker API responded with 21 devices
    [latest-25016]2025-02-07T09:08:02.814Z <HubitatController:WARN> HubitatController#hubitat-C7 native capability URL no definition data; skipped
    [latest-25016]2025-02-07T09:08:02.827Z <Controller:INFO> HubitatController#hubitat-C7 0 dead entities older than 86400000s purged
    [latest-25016]2025-02-07T09:08:02.827Z <HubitatController:NOTICE> HubitatController#hubitat-C7 A connection health probe device was not configured. A randomly-selected device will be used.
    [latest-25016]2025-02-07T09:08:02.827Z <HubitatController:NOTICE> Please refer to the HubitatController configuration docs for more information.
    [latest-25016]2025-02-07T09:08:02.829Z <HubitatController:INFO> HubitatController#hubitat-C7 connecting to hub's eventsocket WebSocket API at ws://192.168.178.107/eventsocket
    [latest-25016]2025-02-07T09:08:02.833Z <HubitatController:INFO> HubitatController#hubitat-C8 Maker API responded with 66 devices
    [latest-25016]2025-02-07T09:08:02.881Z <HubitatController:WARN> HubitatController#hubitat-C8 native capability URL no definition data; skipped
    [latest-25016]2025-02-07T09:08:02.899Z <Controller:INFO> HubitatController#hubitat-C8 0 dead entities older than 86400000s purged
    [latest-25016]2025-02-07T09:08:02.899Z <HubitatController:NOTICE> HubitatController#hubitat-C8 A connection health probe device was not configured. A randomly-selected device will be used.
    [latest-25016]2025-02-07T09:08:02.899Z <HubitatController:NOTICE> Please refer to the HubitatController configuration docs for more information.
    [latest-25016]2025-02-07T09:08:02.900Z <HubitatController:INFO> HubitatController#hubitat-C8 connecting to hub's eventsocket WebSocket API at ws://192.168.178.104/eventsocket
    [latest-25016]2025-02-07T09:08:02.993Z <Controller:INFO> VeraController#openLuup 0 dead entities older than 86400000s purged
    [latest-25016]2025-02-07T09:08:02.994Z <Controller:NOTICE> Controller VeraController#openLuup is now online.
    [latest-25016]2025-02-07T09:08:03.015Z <HubitatController:INFO> HubitatController#hubitat-C8 successful connection to ws://192.168.178.104/eventsocket
    [latest-25016]2025-02-07T09:08:03.016Z <HubitatController:INFO> HubitatController#hubitat-C7 successful connection to ws://192.168.178.107/eventsocket
    [latest-25016]2025-02-07T09:08:03.078Z <HubitatController:NOTICE> HubitatController#hubitat-C8 current mode is Home (65)
    [latest-25016]2025-02-07T09:08:03.117Z <VeraController:NOTICE> VeraController#openLuup reload detected (status query with LoadTime 1733911518 in response; expected "1469238424")
    [latest-25016]2025-02-07T09:08:03.164Z <HubitatController:NOTICE> HubitatController#hubitat-C7 current mode is Home (6)
    [latest-25016]2025-02-07T09:08:03.168Z <Controller:NOTICE> Controller HubitatController#hubitat-C8 is now online.
    [latest-25016]2025-02-07T09:08:03.185Z <HubitatController:WARN> HubitatController#hubitat-C7 'Allow control of HSM' appears to be disabled in your Maker API configuration
    [latest-25016]2025-02-07T09:08:03.186Z <Controller:NOTICE> Controller HubitatController#hubitat-C7 is now online.
    [latest-25016]2025-02-07T09:08:03.186Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups
    [latest-25016]2025-02-07T09:08:03.199Z <app:NOTICE> All 6 controllers successfully started.
    

    Cheers Rene

    Multi-System Reactor

  • 'Random' lights turning on
    M mrFarmer

    Have you asked the wife? Mine likes to randomly turn lights on (never off!) just to get me confused 😁
    Cheers Rene

    General Discussion

  • 'Random' lights turning on
    M mrFarmer

    You had to ask 🙂
    Have a look here https://www.amazonforum.com/s/question/0D56Q0000BafbkqSQA/alexa-created-routine-on-its-own
    Cheers Rene

    General Discussion

  • 'Random' lights turning on
    M mrFarmer

    In Alexa there is an option that it 'learns' from 'your behavior'. When I turned that off and removed the rules it created for that 'feature' this spook behavior stopped. I would look into the rules on your Alexa, you may find some you do not remember creating.
    Cheers Rene

    General Discussion

  • MSR UI on a mobile browser
    M mrFarmer

    On an Android phone with either Chrome or Firefox I cannot really use MSR. Toggling the hamburger menu shows most pages except status. That rarely shows a widget especially in landscape mode. I would not think about making or changing rules on a small screen, but being able to look at the status would be nice.

    Multi-System Reactor

  • Logitech logic
    M mrFarmer

    Is the V6 box in direct sight of the Hub or do you use a IR extender just for that? Did that unplug or die? Else, I have no idea. I just hope my harmony keeps working for many many years (knock wood)
    Cheers Rene

    General Discussion

  • Scene Controllers -- What are you using?
    M mrFarmer

    I like the Heat-it z-push wall controller. You can use it with one, two or three paddles mounted that can be used as switch and scene controller. The design fits with my normal wall power outlets and operate like a normal switch to anyone who does not know (or care like the misses). They are 800 devices and after a year the battery still shows at 100%
    Cheers Rene

    Hardware

  • openweather plugin ?
    M mrFarmer

    Hi Ak,
    Not sure what the issue is for me then. I first had it running on Pi3 with Debian, now on Pi4 with Ubuntu, same issue of not getting the token. I did copy the user_data.json, so maybe something in that.
    As a test I tried on my openLuup clean test install running in a container and that is working. So must be something at my end.
    Thanks again anyway, I have a new workaround :-).

    Plugins

  • openweather plugin ?
    M mrFarmer

    I might update then. I do need ALTUI still because of some of my plugins. Slowly moving to HA, but not totally there yet.

    To update a plugin now, How would that work if not via the ALTUI publish function?

    Plugins

  • openweather plugin ?
    M mrFarmer

    Thanks Ak, the Google token refresh does not work unless you run AltUI on a Vera and I do not have those up and running anymore. We did find that before. The token refresh gets stuck in some loop and a luup reload is needed to stop that. It is too deep in ALTUI and some google scripts for me to figure out and @amg0 does not seem to be around any more.

    I am on openLuup 23.01.06. When not using MTTQ, Shelly, Zwave stick, any reason for an update to the latest?

    Cheers Rene

    Plugins

  • openweather plugin ?
    M mrFarmer

    Hi, I have updated the plugin code. You will have to install it manually as the MIOS App Market nor the ALTUI App Store are working. Get the file from github at https://github.com/reneboer/MultiStationWeather/blob/main/src/L_MsWeather.lua

    Note that you will need to get a One Call 3.0 API key. The old one will not work.

    Cheers Rene

    Plugins

  • MSR, Repeat While not evaluated?
    M mrFarmer

    Redesign in progress. Thanks again for this great multi platform tool.

    Multi-System Reactor

  • MSR, Repeat While not evaluated?
    M mrFarmer

    Thanks. So I'd probably better split the rule then. Not a problem, but then I have five per appliance. O well, who's counting 🙂

    Multi-System Reactor

  • MSR, Repeat While not evaluated?
    M mrFarmer

    Hi,
    Running the latest version 24212 on docker.
    I want to run some appliances when my solar panels deliver over 1200 watts to the net. In this example the dryer. So when the dryer is turned on, the rule starts (SET). There first is a 3 min delay in case the dryer is turned on manually, that is group "Check if auto start is needed". If the dryer is not running, the status is set to waiting, and the shown Repeat Until should wait as long the power delivered is higher than -1200 for at least 120 seconds and the status is still waiting. Higher as the value is negative. For some reason that repeat until "DR Wait for solar high or manual start" looks skipped. Nothing in the logs. What am I missing?

    [latest-24212]2024-08-07T12:38:49.895Z <Rule:INFO> rule-Dryer Automatic Cycle Start (rule-lzjtr8w7 in House Controls) evaluated; rule state transition from RESET to SET!
    [latest-24212]2024-08-07T12:38:49.900Z <Engine:INFO> Enqueueing "rule-Dryer Automatic Cycle Start<SET>" (rule-lzjtr8w7:S)
    [latest-24212]2024-08-07T12:38:49.910Z <Engine:NOTICE> Starting reaction rule-Dryer Automatic Cycle Start<SET> (rule-lzjtr8w7:S)
    [latest-24212]2024-08-07T12:38:49.911Z <Engine:NOTICE> rule-Dryer Automatic Cycle Start<SET> delaying until 1723034509911<8/7/2024, 2:41:49 PM>
    [latest-24212]2024-08-07T12:41:49.912Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET> (rule-lzjtr8w7:S) from step 3
    [latest-24212]2024-08-07T12:41:49.924Z <Engine:NOTICE> Starting reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwf7)
    [latest-24212]2024-08-07T12:41:49.954Z <Engine:NOTICE> Starting reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/DR Check auto start (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwfc)
    [latest-24212]2024-08-07T12:41:50.125Z <HubitatController:INFO> HubitatController#hubitat-C7 action x_hubitat_HealthCheck.ping([Object]{  }) on Switch#hubitat-C7>69 succeeded
    [latest-24212]2024-08-07T12:41:50.125Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/DR Check auto start (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwfc) from step 2
    [latest-24212]2024-08-07T12:41:50.125Z <Engine:NOTICE> rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/WM Check auto start delaying until 1723034525125<8/7/2024, 2:42:05 PM>
    [latest-24212]2024-08-07T12:42:05.125Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/DR Check auto start (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwfc) from step 3
    [latest-24212]2024-08-07T12:42:05.215Z <HubitatController:INFO> HubitatController#hubitat-C7 action power_switch.on([Object]{  }) on Switch#hubitat-C7>69 succeeded
    [latest-24212]2024-08-07T12:42:05.216Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/WM Check auto start (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwfc) from step 4
    [latest-24212]2024-08-07T12:42:05.219Z <Engine:INFO> rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed/DR Check auto start all actions completed.
    [latest-24212]2024-08-07T12:42:05.234Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed (rule-lzjtr8w7:S-rule-lzjtr8w7-1j83mwf7) from step 5
    [latest-24212]2024-08-07T12:42:05.234Z <Engine:INFO> rule-Dryer Automatic Cycle Start<SET>/DR Check if auto start is needed all actions completed.
    [latest-24212]2024-08-07T12:42:05.249Z <Engine:INFO> Resuming reaction rule-Dryer Automatic Cycle Start<SET> (rule-lzjtr8w7:S) from step 4
    [latest-24212]2024-08-07T12:42:05.249Z <Engine:INFO> rule-Dryer Automatic Cycle Start<SET> all actions completed.
    

    Reactor Automation.png (g_DryerStatus should have been "waiting" and not "running" the moment the log was captured, so that should not be the issue. Unless it takes some time for a variable to actually change?)

    Cheers Rene

    Multi-System Reactor

  • openweather plugin ?
    M mrFarmer

    Hi, it is on my to-do list to make the change. Might be this week, no promises.

    Plugins

  • Having an issue with calling a HA service from MSR
    M mrFarmer

    That did it. Thanks for your help.

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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