I'm doing something similar. Using FullyKiosk, TheHomeRemote and Dakboard running on a Kindle FIre 8HD. Using a MakesByMike mount as well. My wife let me "upgrade" our wall decor to be a bit more functional 
C
cubs2b23
@cubs2b23
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
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?
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.
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
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.
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?
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
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!
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.
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.
Posts
-
Wall mount tablet plug-in -
Getting status update from deviceI see things like this in my setup now that I've moved to z-way instead of Vera. Like it missed the status update. I can click on the "Update All" button from the Z-way Expert UI and then everything is accurate again. And it's not missing every status update and not even for the same devices. Just one maybe two. I've often wondered if there is a way to manually send the "Update All". But that status on my lock is definitely one that often incorrect.
@rafale77, would it be possible for you to go into more explanation of hacking the z-way lock plugin?
-
(Need Help) Migrate off Vera@rafale77 said in (Need Help) Migrate off Vera:
I think the best recommendation I can give you given the fact that you "only" have 30 zwave devices is to start from scratch using z-way since you already have a license for it.
For less complicated reasons I abandoned Vera with about this many devices. It wasn’t awful to start from scratch but I’m not going to lie and say it wasn’t frustrating to have to get to that point. I moved all zwave devices to Zway with only a few hiccups.
-
Playing sounds on the Zooz Siren ZSE19I think I'm going to try excluding and including the device again. I was trying a few Get/Set commands from the Zway Expert interface last night and the Set command seems to keep failing. I've also emailed Zooz to see if they have anything to suggest.
-
Playing sounds on the Zooz Siren ZSE19This is what is posted also on the Zooz website. Of course the article is geared toward using it on a Vera. But if it works on Vera then I'd have to think it should work outside of it. Maybe they didn't need to specify it as 0x79. I'll give it a shot.
-
Playing sounds on the Zooz Siren ZSE19Yea that makes sense that it was formatted with Vera in mind. Here was the luup call that was also given:
luup.call_action( "urn:micasaverde-com:serviceId:ZWaveNetwork1", "SendData", { Node="ddd", Data="x79 8 nn" }, 1 )
So how do I modify that to work with zway?
-
Playing sounds on the Zooz Siren ZSE19I'm trying to do this now that I have migrated the siren to Zway. Here's the thread from the Vera forums on how to do it with a Vera: https://community.getvera.com/t/playing-sounds-on-the-zooz-siren-zse19/211318
I'm guessing something needs to change in the code since previously it was calling out the vera specifically.
Here's what shows up in the logs when I tried to use Reactor for the SendData. Zway plugin is device 18. And my siren is device number 95 in my Zway network.
2020-12-01 15:37:27.052 openLuup.server:: POST /data_request HTTP/1.1 tcp{client}: 0x56194138c448 2020-12-01 15:37:27.052 luup.call_action:: 18.urn:micasaverde-com:serviceId:ZWaveNetwork1.SendData 2020-12-01 15:37:27.053 openLuup.server:: request completed (151 bytes, 1 chunks, 0 ms) tcp{client}: 0x56194138c448 2020-12-01 15:37:27.079 luup_log:18: ZWay: http://127.0.0.1:8083/ZWaveAPI/Run/SendData(95,x79 8 35) 2020-12-01 15:37:27.079 luup_log:18: ZWay: SyntaxError: Unexpected number 2020-12-01 15:37:27.184 openLuup.server:: request completed (8606 bytes, 1 chunks, 5939 ms) tcp{client}: 0x561941d02fe8 -
Status Board - What’s your HA Information Dashboard ?Today I tried to use Fully Kiosk on an old Samsung tablet but the AltUI wouldn’t fully loaded. But it would load fine in the regular Chrome app
-
Yamaha PluginThat worked! Thanks @akbooer
-
Yamaha PluginRunning it on Ubuntu 20. I’ll give that a shot anyway
-
Yamaha PluginHere's what I found in the log when installing the plugin.
2020-11-22 12:52:18.628 openLuup.chdev:: [string "L_YamahaRxHTTP1.lua"]:40: module 'lxp' not found: no field package.preload['lxp'] no file './lxp.lua' no file '/usr/local/share/lua/5.1/lxp.lua' no file '/usr/local/share/lua/5.1/lxp/init.lua' no file '/usr/local/lib/lua/5.1/lxp.lua' no file '/usr/local/lib/lua/5.1/lxp/init.lua' no file '/usr/share/lua/5.1/lxp.lua' no file '/usr/share/lua/5.1/lxp/init.lua' no file '../cmh-lu/lxp.lua' no file 'files/lxp.lua' no file 'openLuup/lxp.lua' no file './lxp.so' no file '/usr/local/lib/lua/5.1/lxp.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/lxp.so' no file '/usr/lib/lua/5.1/lxp.so' no file '/usr/local/lib/lua/5.1/loadall.so' -
Yamaha PluginIs that in the Variables section? Mine is blank right now
-
Telegram Plug-in to send text, images and video notificationsI'm seeing this as well with the dropdowns in both Firefox and Chrome. Running stable version of Reactor and v2.50 of ALTUI
-
Yamaha PluginAnyone using the Yamaha plugin currently? I installed it from the AltAppStore and put in the IP in the Attribute field but it never connects to it. This was working fine on the Vera side.
-
Set/Get Yale Lock Pin CodesNew to Z-way and it's interface and inner workings. How do I get the list of codes already set for my lock when I was using Vera? And then how do I set new ones? Should I be looking in the standard UI or the Expert UI?
-
(Problem) Migration Z-Wave NW from Vera to UZB1 dongleJust to update: I decided to bite the bullet and just manually move everything over from Vera to Z-way. Still a couple of outstanding devices to transition. It went mostly smooth. I have a couple of devices that aren't responding as they did with the Vera network. Shouldn't be an issue of coverage.
-
(Problem) Migration Z-Wave NW from Vera to UZB1 dongleNo go on the second attempt. So what are my other options if I don’t want to exclude/include everything?
-
(Problem) Migration Z-Wave NW from Vera to UZB1 dongleI might try the whole thing again. I just did a restore because at some point after I thought that none of it worked all my devices names were reset and all sitting in 'No Room'. Of course this was after I had switched the port back to the default Vera device. So something was happening maybe just at a snail's pace? Also how do I check the Vera's SDK version?
-
(Problem) Migration Z-Wave NW from Vera to UZB1 dongleLooks like I'm running into the same things @Trexx in migrating things over from the Vera. Stuck at the dongle.restore not being removed upon engine reload. I'm not sure if I saw if there was a resolution.
-
Push notificationsAnything in particular that I'm missing to get Prowl to work in Reactor? I'm trying to move everything off the Vera but I am getting a 404 error in the LuaUPnP log. Using the same Prowl API key that Vera used. Even created a new one and tested that it worked on the Vera.