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.
A

ArcherS

@ArcherS
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
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
About
Posts
258
Topics
10
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Power monitoring options
    A ArcherS

    Like @Crille I have an electrical meter with a P1 data port. I use a DIY ESP8266 reader that I described some time ago in this thread. Since writing my post I have changed the software on the ESP, the version I am using now publishes the meter data approx every 10s as a json.

    A good wifi solution for the whole house if lacking a dataport is to use a Shelly 3EM. It is a three clamp meter that can measure all three incoming phases, assuming you have that. I have a few of these for measuring both single and multiple phase consumers, e.g. a two-phase water heater. It reports both energy, power, voltage and current per phase.
    The only downside I can see is that the clamps are a bit big, so some space is required to get them in place around the incoming power lines.

    Vera

  • OpenLuup installation
    A ArcherS

    So I thought I would report back on the restore of openLuup onto my new server.

    What I did was roughly:

    • set up a fresh install of openLuup on my new server
    • stop the old and new server with
      http://192.168.1.xxx:3480/data_request?id=exit
    • copy all the content from the folders "files" and "icons" from the old server to the new server (this I had to do with sudo rights in the Terminal)
    • copy the latest backup file to the backup foder on the new server
    • run the reload openLuup script from the cmh-ludl folder
      ./openLuup_reload backup/backup.openLuup-nnnn.lzap
    • restart the server

    After this the new server contained all the items from the old installation. Most things has worked, but some things did not.

    I had to reinstall the Z-way plugin (plugins->update now button) to get it working, the login fields did not exist (see above) until I did that. After the reinstall I could log in and get it to work.
    I also had to reinstall Reactor and the Telegram plugins (plugins->update now button).
    Reactor said the database was old and the update button was not there so it could not be updated.
    Telegram did not work but everything looked as it should. After the update it worked.
    The only remaining oddity from this error is that I now have a Reactor sensor that I cannot remove. It crashed during editing it before I realised that the plugin did not fully work (it is now empty when I open it, so no delete button).
    I recreated the logic in a new sensor and disabled the old one.
    Any advice on how I can remove the failed sensor would be appreciated. 🙂

    Yesterday I discovered that my Remotec ZRC90 remotes did not work. The sl_CentralScene did not update when pressing the buttons on the remote. Based on the advice in this thread I reinstalled the development version of the Z-way plugin from the App Store and then it worked. Strange problem, unclear what could be the reason for it.

    So a few quirks here and there, it seems as if some data does not survive the restore, unclear why.

    @akbooer is it better to do a reinstall from App Store when restoring a backup of from of from Plugins->update now button? Or should it not matter? 🙂

    As a small side note I also reinstaller Grafana onto the new server. I found a useful tip that it is possible to copy the grafana.db file from the old server to move all of the configuration. This worked perfectly at least on my 8.1.1 installation. The only issue is to make sure to have the same version Grafana on the new server as on the old. This is is easy to do with the help of their webpage.

    openLuup

  • OpenLuup installation
    A ArcherS

    @catmanv2 MSR is definitely on the list of things to setup and try. It seems really nice and a natural step forward from Reactor. 🙂

    openLuup

  • OpenLuup installation
    A ArcherS

    @catmanv2 yes it can quickly become tricky to have back-ups of everything. I have no clear strategy but some bits-and-pieces that I use.

    For the Zway server that is running on a separate Pi I make a complete image with Win32 Disk Imager when I update the server. I run it on a 2.5" ssd, so I have two. That way I can revert back if it crashes hopefully.

    For openLuup I do manual backups (Table Controllers->Backup Controller) before changing things. I keep them on another PC for safe keeping. A fresh install and copying the files and icon folders before running the reload script seems to work ok.

    Now that I look at migrating to Proxmox I will test another strategy. In Proxmox it is super easy to make a complete copy of the VM. This can then be deployed in a few minutes, no need to set everything up from scratch again. My idea is to use this as a fall back also in combination with openLuup backups. Also to use it when testing things on a temporary VM before updating the live VM.

    I have not moved over to MSR yet so thte Reactor logic is part of the openLuup backups.

    The plan is also to run my Home Assistant on the Proxmox server to be able to have a live server and a test server in parallel.

    openLuup

  • OpenLuup installation
    A ArcherS

    @akbooer that seems to have worked quite nicely when checking quickly on all the devices, thank once more for the quick response. 🙂

    One thing that does not work is the connection to the Z-Way server. The devices do not update when changing them either in the new openLuup or in the Zway UI.
    I suspect I need to login again to connect the bridge with the server.
    If I remember it correctly I should do that in the Console under "actions" for the Z-Way bridge. However it is empty there:

    8253efd8-3e8f-4461-9a26-1ff3bd1be79f-image.png

    Any ideas on that one?

    Edit: I have version 21.1.19 of the Z-Way bridge. On my old installation the login fields are there under "actions".
    fd1c629f-ffc9-4517-9324-43b6160d03a8-image.png

    Edit 2: I updated the Z-way plugin. This gave me a second plugin, also the username/passwd dialogues reappeared on the old bridge.
    After having deleted the new bridge, logged in into the old one and restarted openLuup it seems to work. I will see if anything looks strange.

    openLuup

  • OpenLuup installation
    A ArcherS

    Next question. 🙂

    When restoring from a backup file from another OpenLuup what is the best approach to get everything up and running on the new openLuup installation with icons, plugins etc?

    Should I manually copy e.g. icons and something else before restoring. Also do I have to install the plugins again?

    //ArcherS

    openLuup

  • OpenLuup installation
    A ArcherS

    That did the trick! 🙂

    Alpine and Docker, need to look at that also later on. 🙂

    Thank's @CatmanV2 and @akbooer for your swift help!

    openLuup

  • OpenLuup installation
    A ArcherS

    Hi,

    I am trying to install openLuup on a new Debian 11 server. It is a clean install Debian 11 running as a VM on Proxmox.

    I have installed lua 5.1, lua-socket, lua-filesystem and lua-sec.

    When installing openLuup with "# lua5.1 openLuup_install.lua" I get the following response:

    debian-pve:~/cmh-ludl$ lua5.1 openLuup_install.lua
    openLuup_install   2019.02.15   @akbooer
    getting openLuup version tar file from GitHub branch master...
    un-zipping download files...
    getting dkjson.lua...
    creating required files and folders
    initialising...
    downloading and installing AltUI...
    sh: 1: curl: not found
    lua5.1: ./openLuup/L_AltAppStore.lua:567: attempt to call upvalue 'next_file' (a nil value)
    stack traceback:
    	./openLuup/L_AltAppStore.lua:567: in function 'update_plugin_job'
    	openLuup/init.lua:254: in main chunk
    	[C]: ?
    openLuup downloaded, installed, and running...
    visit http://192.168.1.210:3480 to start using the system
    olsson@debian-pve:~/cmh-ludl$ Sat Aug 27 13:35:31 2022	device 2 '    openLuup' requesting reload
    

    When I try to go to the url "http://192.168.1.210:3480" I get the following response:

    No handler for data_request?id=lr_ALTUI_Handler
    

    In other words it seems as if there is a problem starting AltUI.

    If I instead go to the Console (http://192.168.1.210:3480/console) openLuup is up and running.

    The startup_log in the Console reads:

    2022-08-27 13:35:31.488   :: openLuup STARTUP :: /home/olsson/cmh-ludl
    2022-08-27 13:35:31.488   openLuup.init::        version 2021.06.14  @akbooer
    2022-08-27 13:35:31.489   openLuup.scheduler::   version 2021.03.19  @akbooer
    2022-08-27 13:35:31.510   openLuup.io::          version 2021.03.27  @akbooer
    2022-08-27 13:35:31.510   openLuup.mqtt::        version 2021.06.08  @akbooer
    2022-08-27 13:35:31.511   openLuup.wsapi::       version 2019.08.12  @akbooer
    2022-08-27 13:35:31.511   openLuup.servlet::     version 2021.04.30  @akbooer
    2022-08-27 13:35:31.511   openLuup.client::      version 2019.10.14  @akbooer
    2022-08-27 13:35:31.512   openLuup.server::      version 2020.03.26  @akbooer
    2022-08-27 13:35:31.518   openLuup.scenes::      version 2021.06.02  @akbooer
    2022-08-27 13:35:31.520   openLuup.chdev::       version 2021.05.04  @akbooer
    2022-08-27 13:35:31.521   openLuup.userdata::    version 2021.04.30  @akbooer
    2022-08-27 13:35:31.521   openLuup.requests::    version 2021.02.20  @akbooer
    2022-08-27 13:35:31.521   openLuup.gateway::     version 2021.05.08  @akbooer
    2022-08-27 13:35:31.522   openLuup.smtp::        version 2018.04.12  @akbooer
    2022-08-27 13:35:31.523   openLuup.historian::   version 2021.06.12  @akbooer
    2022-08-27 13:35:31.523   openLuup.luup::        version 2021.05.14  @akbooer
    2022-08-27 13:35:31.524   openLuup.pop3::        version 2018.04.23  @akbooer
    2022-08-27 13:35:31.524   openLuup.compression:: version 2016.06.30  @akbooer
    2022-08-27 13:35:31.524   openLuup.timers::      version 2021.05.23  @akbooer
    2022-08-27 13:35:31.524   openLuup.logs::        version 2018.03.25  @akbooer
    2022-08-27 13:35:31.524   openLuup.json::        version 2021.05.01  @akbooer
    2022-08-27 13:35:31.524   luup.create_device:: [1] D_ZWaveNetwork.xml /  /    ()
    
    2022-08-27 13:35:31.525   openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
    
    2022-08-27 13:35:31.530   luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json   (openLuup)
    2022-08-27 13:35:31.530   openLuup.init:: loading configuration user_data.json
    2022-08-27 13:35:31.530   openLuup.userdata:: loading user_data json...
    2022-08-27 13:35:31.532   luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0
    2022-08-27 13:35:31.532   openLuup.userdata:: loading rooms...
    2022-08-27 13:35:31.532   openLuup.userdata:: ...room loading completed
    2022-08-27 13:35:31.532   openLuup.userdata:: loading devices...
    2022-08-27 13:35:31.532   luup.create_device:: [1] D_ZWaveNetwork.xml /  /    ()
    
    2022-08-27 13:35:31.532   openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
    
    2022-08-27 13:35:31.534   luup.create_device:: [3] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json   (urn:schemas-upnp-org:device:AltAppStore:1)
    2022-08-27 13:35:31.534   openLuup.userdata:: loading scenes...
    2022-08-27 13:35:31.534   openLuup.userdata:: number of scenes = 0
    2022-08-27 13:35:31.534   openLuup.userdata:: ...scene loading completed
    2022-08-27 13:35:31.534   openLuup.userdata:: loading installed plugin info...
    2022-08-27 13:35:31.534   openLuup.userdata:: [openLuup] openLuup (21.7.25)
    2022-08-27 13:35:31.534   openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30)
    2022-08-27 13:35:31.534   openLuup.userdata:: [VeraBridge] VeraBridge (not.installed)
    2022-08-27 13:35:31.534   openLuup.userdata:: [8246] Alternate UI (not.installed)
    2022-08-27 13:35:31.534   openLuup.userdata:: [Z-Way] Z-Way (not.installed)
    2022-08-27 13:35:31.534   openLuup.userdata:: [Arduino] MySensors (not.installed)
    2022-08-27 13:35:31.534   openLuup.userdata:: ...user_data loading completed
    2022-08-27 13:35:31.534   openLuup.init:: running _openLuup_STARTUP_
    2022-08-27 13:35:31.534   luup_log:0: startup code completed
    2022-08-27 13:35:31.534   openLuup.init:: init phase completed
    2022-08-27 13:35:31.534   :: openLuup LOG ROTATION :: (runtime 0.0 days) 
    

    Any ideas on what could be wrong and why AltUI does not work?

    openLuup

  • Considering changing to HA - but what installation method?
    A ArcherS

    Just for fun I decided to test and setup Home Assistant OS on two virtual machines.

    The first is a HA OS VM on a Windows 10 i5 NUC with VirtualBox. Quite easy to setup, some information can be found on the HA website, I also looked at this guide.

    The second VM I installed on an old Core2 PC. I installed Proxmox and then HA OS in a VM. A bit more complicated to setup but there is a good guide here. The Core2 seems ok for this setup, in comparison with the old Athom PC that did not do the job.

    Both installations seem to work ok. I will test them later on with a backup of my production setup to see if that changes anything.
    The Windows installation got corrupted when I had to hard reset the PC. As expected HA OS did not like that, however quite easy just to delete the VM and set it up again. I only had a test installation of HA on the VM, but as always a backup of HA is a good idea.

    I have not tested any USB devices (e.g. Zwave stick) since I do not use it. As far as I have understood it both should work with USB devices.

    What to use? The plan is to stay with my current Debian/Docker setup since it has so far been very stable. If the HA devs continues to move away from the Docker installation I may need to reconsider this.

    The other VM's could be an option for test rigs I think.
    I like the Proxmox setup, it feels quite solid and is built for VM. The Windows setup feels a bit more uncertain with the MS Windows 10 automatic updates etc.

    Home Assistant

  • An electricians or wiring experts here?
    A ArcherS

    @cw-kid it is really difficult to say. I think your drawing looks quite similar to the one I posted, but not quite sure, it could be different. The earthing in the pattress box is unfamiliar with me, the boxes here are in plastic. But I assume it is simply an earth to the box since it is made of metal.

    The colours are always tricky in old houses. They can have changed, different standards over time etc. Not to be trusted in other words. The only way to know is really to try understand what they all are and where they all go.
    You may need to disconnect the cables on the two switches to fully map things out. Marking the original position of all cables, cutting the power while working etc. 🙂

    I do not have any Dimmer 2, but will it not need neutral to operate? This means that you would need to get neutral to behind one of the light switches.

    Another solution could be to put the Fibaro at the light instead, if it fits safely there and is allowed in your location. That could perhaps be a solution not having to get new cables drawn into the boxes.

    Regarding your switches momentary should work or are even needed for being able to dim the light.

    I found a sketch showing one way to connect two momentary switches to a Fibaro Dimmer (the older version I think since it says "O" for the connnection that goes to the light). Maybe it could be of use.
    As always continue with care and cross-check with the Fibaro diagram, they could have changed something in the new version.

    f4e3f986-2d6b-42b7-a054-e68d60607563-bild.png

    Basically if I understand the sketch correctly the two switches need to be connected in parallel over S1 and SX.

    Not sure I can help more, good luck! 🙂

    General Discussion

  • An electricians or wiring experts here?
    A ArcherS

    In Sweden the most usual connection in that situation is a "stairway connection". It typically is done like this:

    618783f3-e7ce-4bc1-8c58-1d6486e49859-bild.png

    Maybe what you have is something like this connection?

    General Discussion

  • Considering changing to HA - but what installation method?
    A ArcherS

    I am running HA Supervised in a Docker container on Debian on a small i5 Lenovo. Installed HACS without any problems, there are a few guides on how to do it.
    It has been stable so far anyway.

    The only concern I have is that it seems as if the HA developers want to push users away from the Docker way of running HA over to the HA OS way.
    What this means is that the requirement now is more or less a vanilla Debian with only HA in Docker. If you do not stick to this the installation becomes "unsupported".
    My installation was "supported" but now I can see that it has become "unsupported" due to the Portainer installation.
    My idea was to add e.g. MSR in Docker at some point in time, but maybe the Docker route will be a dead end for HA?

    It could be so that a HA OS installation on a VM, e.g. in Proxmox is the better choice in the longer run. The other option to only install HA OS on e.g. a fairly modern NUC seems a waste of resources to me since you cannot use it for anything else then.

    I tested Proxmox and it seemed quite nice, the problem was that the old Athom PC I used was too old for the combination Proxmox/HA. So if I will go down that route I need to reinstall my i5 from scratch. Hmm.

    To be honest I think it is a bit annoying that HA has complicated the setup/installation so much, not sure why they did that.

    Home Assistant

  • openLuup: MQTT server
    A ArcherS

    Answering my own question, perhaps of some use for someone else. 🙂

    Today I upgraded my Home Assistant to 2021.11.5 and the connection to the OpenLuup Mqtt server seems so far to work as it should.
    (Running on OpenLuup v21.11.8)

    openLuup

  • HVAC Control
    A ArcherS

    I have a setup that works quite nicely for controlling my "mini split" HVAC.
    It is a quite old unit that is more or less totally stupid, it has a remote and that's it.

    Some time ago I put together a Tasmota IR device that can control quite a few different HVAC units including mine. Pretty cheap, not too difficult to build and with a nice case it looks ok.

    One nice aspect of the Tasmota solution is that both receives and sends IR so I mounted the IR Transciever close to the HVAC so that it also recieves commands from the IR remote. Another upside with the Tasmota route is that it is independent of what hub one uses since it is Wifi and Mqtt.

    The next question was how to control it. With the help from @therealdb and his excellent VirtualDevices plugin together with the Mqtt capability of OpenLuup I managed to get a working solution in place.There is some information in the Mqtt Bridge thread on this.

    Since I use Homewave the next logical step was to be able to control it from inside Homewave. A few dimmers with fixed steps and a Reactor with some logic and I got something working in place to control on/off, temperature and mode.
    Not the prettiest solution but it does the job. The limitations in the old Vera gui and device types do show.
    42532144-7ce0-44b3-a315-7144ff4a13e9-bild.png

    After recently having started playing around with Home Assistant I found a really nice integration for Tasmota IR HVAC control. It was really easy to get in place, it looks quite nice and can control most/all of the functions on the HVAC.

    a73a0416-93a1-4e7d-b72d-3b31dd954791-bild.png

    Hardware

  • openLuup: MQTT server
    A ArcherS

    @toggledbits said in openLuup: MQTT server:

    Also I can't connect my Home Assistant 2021.11.5 to the broker. This in the logs:

    I may have missed this, but was this solved?

    The reason is that I am currently on Home Assistant 2021.10.06 and was planning to upgrade to the latest 2021.11.5.
    On 2021.10.6 I am using the Mqtt server in OpenLuup and it is working fine.

    openLuup

  • MQTTController map different values from same topic?
    A ArcherS

    @Crille I do not use the MSR (yet! 🙂 ), but I do have a Tasmota device reporting three Xiaomi Mi BLE devices to OpenLuup over Mqtt.

    They report the following:

    {"Time":"2021-11-24T16:00:25","ATC-6d5d44":{"Temperature":20.6,"Humidity":48.0,"DewPoint":9.2,"Battery":76,"RSSI":-89},"ATC-9446bf":{"Temperature":19.6,"Humidity":52.0,"DewPoint":9.5,"Battery":42,"RSSI":-84},"ATC-f159bf":{"Temperature":19.6,"Humidity":55.0,"DewPoint":10.3,"Battery":45,"RSSI":-84},"TempUnit":"C"}
    

    on the following topic:

    tele/TasmotaBLE/SENSOR
    

    The message contains all three devices each under their name.

    Not sure how about the syntax in MSR but in e.g. Home Assistant you write something in this direction in the config.yaml to retrieve the temperature for one device.

      - platform: mqtt
        name: "Temperatur"
        state_topic: "tele/TasmotaCO2Ax/SENSOR"
        value_template: "{{value_json['ATC-6d5d44'].Temperature}}"
        device_class: temperature
        unit_of_measurement: "°C"
    
    Multi-System Reactor

  • openLuup: Shelly Bridge plugin
    A ArcherS

    @akbooer said in openLuup: Shelly Bridge plugin:

    Can you give latest development (v21.11.8) a try?
    I don't think I'm quite there yet, but the dimmer control should work to some extent.
    This is surprisingly hard, since the status/control aspect of the Shelly dimmer is not quite the same as that of a ZWave one... I've always hated the way that Vera handled dimmers anyway! But I'm doing the best I can.

    I installed v21.11.8 and now it almost seem to work. 🙂

    In short what is not entirely in place is that the dimmer slider on the AltUI desktop in some cases does not follow the set value.

    Example:
    When I change the dim value in the Shelly GUI it updates in OpenLuup inside the dimmer but the slider on the desktop does not update.

    Starting with the dimmer off and all sliders on 1% and then dim to 40% on the Shelly GUI gives:

    In the Shelly GUI:
    e7c627df-45d9-4f5f-93f4-2bfc5f859970-image.png

    On the desktop in AltUI:
    9f36d698-ca0d-43a2-a25b-61b9f0b72b0f-image.png

    Inside the dimmer controller in AltUI:
    0b967f7c-784b-424e-a2da-84e705a94309-image.png

    Variables:
    ee2d8d13-d247-4e89-9ca9-25fa44dc6b97-image.png

    light/0/status:
    {"ison":true,"source":"http","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":40}

    If I instead change the dim value from AltUI either from inside the dimmer controller or from the desktop it works and everything is updated. Also the slider inside the AltUI dimmer seems to work as it should.

    Let me know if you need more information.

    Based on your input I tested the latest fw (v1.11.4) on a Shelly Plug and it does indeed seem to work with Mqtt. Great news that it actually works now.

    Plugins

  • openLuup: Shelly Bridge plugin
    A ArcherS

    @akbooer said in openLuup: Shelly Bridge plugin:

    Well, we'll see (the device arrived yesterday)...
    Latest development version of openLuup (v21.11.2) has an initial attempt to service the Dimmer2 device:

    inputs are handled exactly as the switch device – so, essentially, as a scene controller showing the latest activated scene: short press; long press; etc... This should work for both input switches (if you have any with two.)
    on/off button on the control panel should work for the dimmer bulb.
    slider control is not yet implemented.

    ...my current issue is that, although I now have the Shelly Dimmer2 device, I don't have any dimmable bulbs! Everything I have is LED, and they're either non-dimmable or smart devices anyway. In particular, I can't tell whether the power and Watts parameters work correctly for the dimmer.
    So I'd appreciate a listing of any bugs that you find, and I'll continue to work on the slider control.
    Incidentally, I've update to the latest firmware for this device: 20210909-150154/v1.11.4-DNSfix-ge6b2f6d since it came with a very old version that didn't even publish the model number. It seems to work fine, but I've not updated any other of my devices.

    @akbooer thank you for the effort, I installed v21.11.2 and have tested this a bit. 🙂

    For a start I have my switch connected to "sw 1". It is a single button switch, defined as a "one button mode" in the Shelly GUI.
    "sw 1" seems to report as "light/0" in the Mqtt message.

    It does not work fully in OpenLuup yet, below I list what I have found.

    Turning on/off with the physical switch:

    • The status in AltUI does change when turning the light on and off.

    • When I turn the light "off" with the physical switch I have:
      light/0:
      off
      light/0/status: {"ison":false,"source":"input","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":80}

    • When I turn the light "on" with the physical switch (at 80%) I have:
      light/0:
      on
      light/0/status:
      {"ison":true,"source":"input","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":80}

    Turning the light on/off in AltUI:

    • The light does not turn on/off when I turn it on/off in AltUI.

    • When I turn it "on" in AltUI I have:
      light/0:
      off
      light/0/status:
      {"ison":false,"source":"input","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":80}
      relay/0/command:
      on

    • When I turn it "off" in AltUI I have:
      light/0:
      off
      light/0/status:
      {"ison":false,"source":"input","has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"mode":"white","brightness":80}
      relay/0/command:
      off

    When I turn it "on" in AltUI it looks like this:
    55db41a9-7577-41f1-a89f-5b517af01877-image.png

    When I turn on the light with the physical switch it looks like this:
    99f567b5-50e2-43fc-be6d-64f7d9ef76e4-image.png

    In Mqtt Explorer I have the following:
    Light on (i.e. turned on with the physical switch):
    33a274c4-2c2f-4f8e-a364-ab80d6bbee0b-image.png

    Light off (i.e. turned off with the physical switch):
    d1d21430-8705-46bc-b857-606884d367da-image.png

    Turning on in AltUI (but light off):
    f79f10d4-0c08-4cd7-a9f7-4fa7b42cc589-image.png

    Turning off in AltUI (light still off):
    52144f39-c0d3-4206-bc60-378e0fc9805e-image.png

    The "relay/0/command" command that is sent from AltUI does in other words not to give any effect on the Shelly device. In fact with a fresh Mqtt Explorer session it only emerges when turning on/off in AltUI.

    Hopefully this gives some hints to what is wrong. Let me know if you need more information.

    @akbooer said in openLuup: Shelly Bridge plugin:

    ...my current issue is that, although I now have the Shelly Dimmer2 device, I don't have any dimmable bulbs! Everything I have is LED, and they're either non-dimmable or smart devices anyway. In particular, I can't tell whether the power and Watts parameters work correctly for the dimmer.

    Dimmable LED lights are a bit tricky still. Some of them work and some of then do not work very well. It can be a bit of a pain to find good ones. The upside is that the Shelly dimmer can be changed from trailing and leading edge dimming (under "Calibration"). This should hopefully mean that it can be a little bit better to adapt to different lights.

    @akbooer said in openLuup: Shelly Bridge plugin:

    Incidentally, I've update to the latest firmware for this device: 20210909-150154/v1.11.4-DNSfix-ge6b2f6d since it came with a very old version that didn't even publish the model number. It seems to work fine, but I've not updated any other of my devices.

    Excellent news that the latest FW seems to work, I will test it later on one of my devices. 🙂

    Plugins

  • openLuup: Shelly Bridge plugin
    A ArcherS

    @akbooer top notch service as always! Hopefully you will get good use of it also. 🙂
    So far I am happy with mine. The dimmer supports all kind of switches. I use it with a spring loaded wall switch in "one button mode", i.e. as a push button with push-and-hold for dimming.

    As a side note I am still on 1.9.x on my Shellies since I did not get mqtt to work with the new firmware. On the EU Shelly support site it is very easy to set up an ota-url for flashing older versions on a device.

    Plugins

  • openLuup: Shelly Bridge plugin
    A ArcherS

    @akbooer sorry, no I am in Sweden.
    I only have one dimmer unit so far and it is in my son's room, he will not like being without ceiling lights this time of the year in our parts of the world. 🙂

    Plugins
  • Login

  • Don't have an account? Register

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