PS: To clarify; my version is the Zigbee/Blue lineup.
I’m noticing a discrepancy between the parameter descriptions in the Hubitat drivers for the red and blue mmWave switches. Could use some clarification and may be appropriate to update the descriptions for consistency (unless intentional for some reason). I don’t see that these parameters are described yet on the red series parameters page.
Blue series:
Parameter 108. mmWave Stay Life
*The delay time of the stay area is set to 50ms when it is set to 1, to 1 second when it is set to 20, and the default value is 300, that is, 15 seconds
Range=0..4294967295 Default=300
Red Series:
Parameter* 108. mmWave Stay Life
Time in seconds before reporting no motion after target leaves detection area
Range=0..3600 Default=300
–> So the Blue series seems to set the parameter in 50ms ticks (time (seconds) = value × 0.05), whereas the red series indicates the parameter is set in 1s ticks (time (seconds) = value). But the 300 default value seems quite long, so it makes me wonder if this was intended to be the same scale as the blue series?
Could you clarify whether the scale for the red series is in fact seconds or if it is in 50ms increments like the blue series?
Same question for Parameter 114:
Blue Series:
114. mmWave Detection Timeout
*Amount of time after presence detection that a no-presence report is sent
Range=0..4294967296 Default=20
Red series:*
114. mmWave Detection Timeout
Amount of time in seconds *after presence detection that a no-presence report is sent.
Range=0..4294967296 Default=30
No real rush on this, but just something that might be good/easy to fix as you’re pushing out other updates. Though some clarification in the meantime would be helpful!*
2 Likes
I am continuing to have issues setting up each of the 10 switches and have confirmed for me, Settings just dont take unless everything is done one by one and/or sent multiple times with long wait times and refresh each time.
I am wondering if there is also a driver issue. (With hubitat at least). I am on the latest driver published. When I try to use a rule to change a parameter, it errors out.
org.codehaus.groovy.runtime.metaclass.MethodSelectionException: Could not find which method setParameter() to invoke from this list:
I was trying to set the switch to not turn on unless it’s dark (using lux). This should ideally part of the base functionality. Would highly appreciate this to be an enhancement for the future (after the settings/driver issues are resolved)
Wow that’s interesting that the Hubitat drivers say second. Home Assistant says 50ms in the UI, but I’ve done testing that shows that it is being set in seconds. A driver or documentation update would be appreciated.
Also interesting that the description in Hubitat for params 108 and 114 are so similar. It makes me think that they are both doing the same thing, which I’m starting to suspect but haven’t nailed down a way to test
Param 108: Time in seconds before reporting no motion after target leaves detection area
Param 114: Amount of time in seconds after presence detection that a no-presence report is sent.
Just a follow-up, it looks like I got a driver update on Jan 28th and now the settings show with the innovelli driver. However I do still get the toast that says “the device hasn’t updated all of it’s status information”. Even with the official driver, setting the distance parameters seem to have no affect and it is still detecting through walls far beyond the limits I’ve set.
Today my z-wave motion dimmer stopped being able to turn on my lights through both the physical switch and through home assistant. It was still reporting, settings were correct, etc and I was not able to find any issue. After pulling the physical power tab and restarting the switch, it was working again. Looks like there is something causing instability. Any recommendations on what to collect if this happens again?
In the hubitat driver
111. mmWave Module Commands
Stays to what you last set for options other than reset, and the options are not really clear on what they do. Could we get better descriptions, and if they are one time commands instead of settings move them to the commands tab instead of preferences.
Are there any updates here yet? Really disappointing that we don’t have even feature parity with the blue version, yet alone the bugs with room size and such. I haven’t been able to use my switches as anything but regular switches because of this. Kinda wish I had switched to blues when I had the chance, would have if I known this was going to be the result.
1 Like
Yes, see:
FYI - I’ve installed this updated firmware (2.01) and found it to resolve that issue.
Shoot, my bad, I somehow missed that. Gonna install these this week, should solve 80% of my issues. Now I just need multi-zone and I should be able to hopefully fix the issue in my office with the last switch.
They have only provided a bug fix so far.
No additional features are planned from the feedback, and have been unresponsive as to what their plan is on addressing the challenges that they are encountering exposing the same settings as the blue version. Not sure why this was not known before making the choice to continue with production.
I use 90% z-wave and 10% Zigbee, but would have considered switching to blue if I would have known that red would be left behind.
To be honest, I am in the same boat. My current system is 50/50 between Zwave and Zigbee. I would have gone to Zigbee route if I would have known that they are pushing Zigbee more than Zwave in terms of software. Eric also told within same post that they are not pushing for development for zwave which also means that we will not see improvement on zwave next 2-3 months except bug fixes.
1 Like
It does not align with the roadmap that was announced for 2026. One of the key points was to “Further developing our Z-Wave product line to be consistent with the other lines”.
I installed a couple more to try and tune a large room and it’s just too much of a guessing game as I am getting inconsistent results.
FWIW - As far as I know multiple area support was never promised as a feature on this product when it was in the pre-order or development stage. I see it as a “happy benefit” that they were able to expose this functionality on the blue series in the first place.
They didn’t say that they weren’t going to try to get it on the Red series. They said that they aren’t making a commitment to it right now because they don’t have a path forward to exposing it within the Z-Wave specifications (which are a lot more rigid than Zigbee are).
These things take time to do correctly and the approach has to be approved by the Z-Wave certification group.
3 Likes
See this post and previous posts. I am not happy about it either. For a second, I thought about RMA to replace Zwave mmWave with Zigbee. Just to try to replace them. I am not sure that it is feasible or not.