I have never observed this, Are you sure it isn't a network problem (switch maybe?)
R
rafale77
@rafale77
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
-
Nuke Vera Script -
Z-Wave RF optimizationInteresting! I have moved and have taken down my entire system. It will be a few months before I get a new one up and running but it does indeed look like the noise level is quite a bit lower. Not sure if it is due to reporting differences or if it true noise decrease.
-
Vera firmware 7.32 betaI have been mostly silent on this forum for some time now with the exception of the occasional notifications for questions addressed to me because I just moved to a new house and my system had been rock solid for over a year... mostly since I got rid of the vera.
I now have to re-build everything from scratch in my new house while I had literally zero reliability issues with my previous setup in spite of its complexity (200+ devices integrated running 3 different software platform interconnected between z-way for zwave, Homeassistant for AI/cameras and the rare cloud integrations or integrations not existing on openLuup/vera and openLuup for scenes/automation/control interface.)
I considered long and hard to sell my old home with the automation but at the end I decided to move as much as I could over mostly because I noticed an increasing trend of the industry to go towards wifi for ease of setup but which cannot scale to large installations and have to encroach into wifi bandwidth. It is getting a bit harder to buy zwave and even zigbee devices. I also didn't want to spend the time to go through the learning curve of hubitat which would have yielded no benefit to my setup.
Dumping the vera was the single biggest improvement to my system and please, no ezlo... They are cost reduced and downgraded controllers to the vera in every important practical aspect.My new setup will be much lighter. Probably will not get to 175 zwave nodes, more likely <100 without the window coverings, fewer lights, fewer sensors. Heck I think I will dump the Phillips hue altogether too. I can't recommend enough migrating away from vera and go to openLuup or MSR in combination with Home Assistant for zigbee and integrations and z-way for z-wave while keeping devices as local as possible by avoiding all the wifi stuff which tend to be cloud dependent (with all their reliability and security disadvantages) and less efficient both in power and RF bandwidth. Still a new adventure...
-
Is anyone using the Ring Doorbell plugin ?My ring doorbell fell victim of my cloud dependance eradication project a few years ago, so I can't help with that one. I can only recommend replacing it with the one I am using... Superior in every way by offering a local 3MP RTSP stream, 5GHz wifi. It's already 3 years old but I haven't found anything better since. The only thing I wish it had is H.265 encoding. Mine is still going strong and is integrated into my system. I run facial recognition on it to trigger a variety of scenes on openLuup.
It is the single most active doorbell thread in this forum:
New RCA HSDB2A 3MP Doorbell IP Camera
Has anyone gotten their hands on one yet? Is it a Hik rebrand as well? RTSP/ONVIF support? The specs look promising otherwise. 3MP, 5GHz wifi, and I really like the included up/down/side tilt...
-
Smart home with no WIFIIndeed! An ethernet network requires a router... or at least you need a DHCP server for these hubs (normally a function of any router and present in most managed ethernet switches).
-
Smart home with no WIFIEuhh, I think something is amiss here. Why running everything off of Zigbee have anything to do with getting internet in the future? If you get a hubitat, your hub will be hubitat. Wifi is just a different type of wireless network communication like zigbee and zwave. They just work on different protocols and frequencies and have different purposes:
WIFI or WLAN is meant for high bandwidth, high power devices like your mobile computer and is meant to offer a bandwidth as close as possible to the wired ethernet (LAN) network it is piggy backed to. Not the most appropriate for smarthomes and especially for battery operated devices because it consumes more power and each device uses bandwidth. Given how little bandwidth smarthome device require, the communication overhead associated with WIFI makes it very wasteful but at this day in age, some people may have plenty of wifi bandwidth to use...
Zwave is a dedicated smarthome protocol which has a fairly good universality mostly due to the fact that it was controller by a single company. Devices tend to be more expensive as a result but prices have been dropping.
Zigbee is another dedicated smarthome protocol but it operates in the same wireless frequency band as WIFI. It is more opened and a lot of companies are involved in maintaining it and therefore has taken off quite nicely.
Zigbee and Zwave require a controller like Hubitat which also need to connect a wired network through ethernet. The controller would have both the radio and small computer on board in which you would setup a software from which to control your devices.
WIFI on the other hand, because of the ubiquity of its use, reuses the radio either on your WIFI router or WIFI access point but usually sends the controlling software out in the cloud so you would need internet access. There are also platforms which enables WIFI devices to be controller locally with a software you would download from the internet.Internet Access and WIFI are not the same. You can have internet access without WIFI or WIFI without internet access. Typically internet access comes in through a MODEM be it from Cable, Telephone or Fibre. There also now 4G/LTE Modem which enable connection to the cellular internet service which would be slower and more expensive and then output it through wire.
Your smarthome fundamentally doesn't need WIFI or internet access but you do need a home wired network in any case to be able to access your controller. Adding WIFI or internet later has no impact whatsoever on your Zwave or Zigbee setup.
-
Smart home with no WIFIMost of us use both for flexibility. Zigbee has cheaper devices and some devices only exist on zigbee. Z-wave also has some unique devices. Since you won't have wifi, you probably don't care that Zigbee interferes with Wifi but also microwave ovens, BT and most cordless phones.... Wifi is a very inefficient protocol for RF. Z-wave is the most efficient from an energy consumption and RF emission perspective, closely followed by Zigbee. I avoid wifi smarthome devices myself because they are fundamentally a waste of bandwidth and energy.
-
Controller shift - How do you do it ?I didn't test extroot on the verasecure because I didn't have one to try it on. I think others on the forum did it and reported to work fine. There is nothing about the vera secure which makes it perform better than the plus. The extra core is unused... the vera UI is single threaded. It also does not use the CPU enough for the speed to make a difference. Same for the DRAM. The only benefit is the battery which to me would be more of a problem than benefit since they have limited lifetime and prevent me from easily power cycling the unit.
-
Controller shift - How do you do it ?You must have missed my posts there... It has an extra CPU core indeed but the DRAM is unused by the software and the flash drive was catastrophically partitioned... netting less useable space than the Plus. After they got bought and my posts about the disastrous engineering they noodled around the partition with symlink (which I initiated with a script I provided on the forum too). I later moved on to boot the vera off of a USB SSD. I know about the zwave chip only because I dug into it. It makes no difference in functionality as the bridge mode the plus and edge had were not used by the vera. It makes the zwave firmware different though.
-
Controller shift - How do you do it ?Oh gosh... I need to remember this. I think at one point I found the firmware for the chip and using a serial updater, managed to manually upgrade the chip firmware through SSH. That was a long time ago. I think I published how to do this in the old forum but not sure if it's been deleted. At the moment, I no longer have any veras... Also the Vera secure runs on a different/cheaper chip than the vera plus I had.. Why don't you just let the vera run on the dongle?
-
Controller shift - How do you do it ?Using the vera backup process you would have to go up or remain on the same version. If you backed up your vera which is on 6.01 into a stick in 6.02, you should be able to restore onto another vera with an SDK 6.02 and above. Have you tried that? Upgrading the vera?
To answer your question if you have both your controller with the same node ID, it will cause a mess to your network. In that case I would add the second controller so it takes a different node ID. (I ran vera and zway together this way for several months).
Here is the type of mess it will cause:
Controller1: turn the light one
Light: Ok the light is on
Controller2: Got it... euh What? who told you to?
Controller1: Are you on yet? Timeout, let me ask again. Retry!This will cause the network to be very busy as nodes do not who to report back to or think they already reported and got an ack...
-
Controller shift - How do you do it ?5.33 =5.32 and 5.36=5.37 if I remember correctly. They were just version numbered for Razberry vs UZB.
-
Controller shift - How do you do it ?You should be able to downgrade back... But yeah that's what I feared... Upgrading too far would make it impossible for the vera to restore...
-
Controller shift - How do you do it ?You caught me there. I was probably smarter then than I am now.
My entire system has been working so well that I stopped tinkering or upgrading it save for only occasional additions or optimization of a scene here or there on openLuup. I lost a lot by not practicing.
-
Controller shift - How do you do it ? -
Controller shift - How do you do it ?This is weird... It should be above 6. Not sure what this 4.38 corresponds to. It looks like you need to keep going... Or try it to see if it migrates. You never know.
-
Controller shift - How do you do it ?Before you keep on upgrading, I would recommend to try the vera migration. 29304 is the bootloader I am currently on. So I am not sure what the new bootloader does. It doesn't look like I went down this upgrade path...
-
Controller shift - How do you do it ?Always upgrade bootloader before the firmware. I at times ended in a dead end and ended up having to use the linux tool to upgrades. The Z-way-server firmware upgrader doesn't always offer the "beta" versions which can be a necessary step to another official version. You can see more by inserting an "all" token but I prefer the lower level linux tool...
Note that you may need to go up all the way to do the backup/copy. You just need to get close enough in the SDK version.
-
Controller shift - How do you do it ?Looks like you should be going to 5.26 and then 5.27. These are already 6.xx stack versions though.
-
Controller shift - How do you do it ?