I pulled the air gap. The switch rebooted but still shows “No Response” after an hour. Is my next step a reset?
I’ve tried all of these suggestions and cannot get the switch to pair with anything. The LED shows that the switch has been factory reset (many times), but I cannot pair with Apple Home, Alexa, or Google Home. I am only showing 9 Inovelli switches in my Matter Accessories under settings on my phone. I’ve tried the air gap, factory reset, etc countless times. I’m kind of at a loss as to what to do now to get this switch paired again. Any other thoughts/suggestions?
Installed my white dimmer switch back in August via Apple HomeKit. Is it normal for it to still be on firmware version 1.0.0?
Would like to try changing between trailing and leading edge to troubleshoot my led recessed lights flickering when they are dimmed but I don’t think that’s an option unless firmware is 2.15.
The only official firmware now is 1.0.0. The feature you’re looking for is available - if you can’t do it via HomeKit, you can do it manually pressing buttons: White Series 2-1 Switch • Button Combinations, Quick Tap Sequences & Local Configuration Options | Inovelli Help Center
1 Like
Thanks for the quick reply. I’ll give it a try manually.
When issuing commands through Siri, the dimmer switches LED light bar sometimes turns solid full white and doesn’t go back to the original set color (blue). Turning off and on the light temporarily gets it back to blue but then goes solid white again after a couple seconds. The solid white persists in both on and off states.
I was able to fix this by pulling the power from the light and letting it reboot. Also sometimes pressing the config button several times resolves it as well.
Edit: I see now that addressing the lights through siri sometimes tells the light bar rather than the light itself. Can fix it by turning off the light bar in homekit. Still an annoying situtation.
This has been addressed by changing the naming convention. Siri is just dumb and you have to account for that.
1 Like
It would be great if there was a firmware option to remove control of the light bar entirely from HomeKit.
3 Likes
That’s something apple would have to integrate. Make devices not accessible to Siri or make Siri ignore devices. You can ignore devices on platforms such as home assistant. It’s not a firmware issue with the switch.
1 Like
The firmware could make the LED bar non-addressable. I found another thread where this is being discussed White switch Apple Home - #31 by otherguy
2 Likes
I just set up my White Series Dimmers in Google Home and I’m a little confused by all of these additional entities that are created for configuration options. Is there any way that I can disable creation of these entities and only use the manual configuration method for modifying the configurations? I don’t want all these entities in my Google Home app.
Unfortunately, until Google improves their matter implementation, I think these entities are going to appear. It does seem like they are working on it because they used to provide no purpose, but at least now they are showing the mode select options. I know it isn’t ideal, but sharing the device to Home Assistant lets you better customize what is shown and what isn’t . . .but then it kind of pulls you away from the Google ecosystem.
1 Like
@EricM_Inovelli – Having now used my numerous White dimmers for months, I’ve identified some bugs and some things that I think would be improvements.
- If possible, allow the radio transmit power to be configurable within a range. Some switches are futher than others from the rest of the network and need a little more “oomph.” But having all switches transmit at high power is counter-productive; this can cause interference, especially with a large network.
- Fix the flickering that occurs when Matter connectivity is being established/re-established. I have seen this now over and over again, essentially every time there’s a Matter server reset that causes rediscovery of devices. Multiple devices across the house will have brief flickers. Possibly power draw that’s a little too strong / sporadic related to storage writing or radio chatter?
- Expose the remainder of the switch’s settings that are not yet exposed to Matter. The most important ones to me right now are trim levels (both min and max), but really, there are a handful of other settings I would like to tweak but have avoided because touching dozens and dozens of switches takes hours. Any reason they can’t all be exposed?
- When Load Level Indicator Timeout is set to “always off” (0), and when the LED indicator light is currently turned on and set to any color, the LED indicator will temporarily turn off whenever the switch is pressed up or down, then turn back on after a moment. It’s as if the load level is being “shown” to the user, but because “always off” is set, the LED doesn’t actually light up. But it does interrupt the current LED color. This is surprising/annoying, happening a lot for us because we use the indicator lights in a number of places and don’t want them blinking off/on everytime we touch a switch.
Thanks for the suggestions! I’ll make note of them in our system to share with the engineers. A rough schedule for our next update (at least beta) is going to be first quarter next year. The big improvements will be an update to SDK 1.4 (which should hopefully improve network reliability and fix other rare bugs) and adding energy and power monitoring (which is made possible because of the new SDK).
Edit: Oh, and to answer this question, right now we are using the Mode select cluster to expose config options. Each Mode Select has to be tied to an endpoint (which we only have six of). We might be able to combine some settings into the same endpoint to add some more options though.
3 Likes
My Google Home experiment has ended and I’m working on Home Assistant now. I noticed just a couple of things preventing these switches from being perfect in my eyes:
- When Home Assistant toggles the power state of the dimmer with a specified transition duration, that transition duration is not respected. For example, if I call light.turn_off on one of these dimmers with a specified transition duration of 20 seconds it does not fade out over 20 seconds, it instead uses the firmware configured transition time. This is not the case if I call light.turn_on to change the brightness from one value to another when the light is already on, this does respect the specified transition duration.
- When the light is controlled from Home Assistant, the dimmer tries to provide live progress as to the status of the fade which causes some weird behavior with UI controls. For example, if you toggle a dimmer switch quickly it will pretty quickly fall behind your clicks because it’s getting caught up on old data. I think that these transitions should be hidden from the network and any state changes should be reflected immediately in the device. Basically if I dim the dimmer from 100% to 1% in 10 seconds I shouldn’t see 50% at 5 seconds, I should see 1% as soon as the device receives the command and the device should handle the dimming on its own.
I don’t think I did a great job explaining either of those concepts very well so if needed I can provide some example videos.
Inovelli’s implementation is correct (and I believe its simply handled by the Matter developer’s SDK, rather than specifically coded by Inovelli). This behavior is defined by the Level Control Cluster specification set out in Section 1.6 of the Matter Application Cluster Specification . Per the standard, the level is reported by the specific cluster attribute CurrentLevel, The standard requires that attribute “SHALL report the current level of the device”. So, doing what you suggest might be a good idea, but it would violate the standard in that you would be reporting a future level rather than the current level. What is really needed is a report of the target level - but unfortunately, Matter didn’t specify an attribute for it (there are other places in the standard where targets are reported, so it seems a bit of a miss that it isn’t available for the Level Control Cluster.).
From the Matter standard:
There is a second attribute “RemainingTime” which is also reported by the device to the controller and the controller could use this to provide an indicator to the user that the device is still in transition, but I don’t think any controller makes use of it yet.
Note that the same issues are present in Zigbee which formed the blueprint for much of the Matter cluster reporting scheme.
4 Likes
Here’s the feedback I submitted to Apple for the issue of Siri control, if anyone else wants to submit something similar: https://feedbackassistant.apple.com/
Title: Siri should ignore devices set to “Exclude from Summaries”
This device includes 2 light endpoints - one of which is a “status/notification” light. If I tell Siri to “turn on/off the lights” I want the status light to be ignored.
The “Exclude from Summaries” option would be perfect for this use case. Siri should only control lights which are shown in the “Lights Summary.”
For what it’s worth I’ve solved this issue with a fairly simple automation:
IF Notification Light Turns On THEN Turn Notification Light Off
Native to HomeKit, though it needs a third party app for setup since Home.app won’t allow an automation with the same device in both the if and then clauses.
Step 1: Create an automation in Home.app that turns the notification light off. The trigger for the notification can be anything except for the notification light itself.
Step 2: Open your third-party HomeKit app (Controller, Home+, Eve, etc.) and change the trigger for the automation from whatever you set previously to “notification light turns on”
Rinse and repeat for each switch, and your notification lights will be “off” forever.
I’ve run into an issue I hope the community can help with.
I use an automation so that when my light is off and I hit the down paddle, the light turns on to 1%. When the light is on and I hit the down paddle the light turns off as usual, and the automation does not run.
So far so good. However, if I enable “instant on” and try to turn the light off with the paddle, my automation now runs and the light ends up at 1% instead of off.
I think the issue here is that by the time the automation is run the light is already off, and so the condition is now true. Does anyone know how to make an automation that doesn’t run when the light is turning off but does run at every other time?