Yeah sure, i'm in the same predicament too. My pattress boxes seem to be less than 25mm, which I thought was the minimum. I currently need to use the spacers with the Lightwave's. If I need to go to the effort of getting deeper pattress boxes i'll most likely wait for the Shelly Dimmer/SL modules to come out.
1 Like
I haven't seen these before. My impression from the website is that these are wifi devices not zigbee.
Probably wrong. 
Yeah they're wifi, but at <£20 each + <£5 for a reatractive switch/plate they're far cheaper, especially when you're doing a lot of rooms. They just need deeper pattress boxes.
Another advantage of using modules, for me at least, is if you have a double light switch and you only want 1 of the 2 to be dimmable, you could use grid switches with a retactive switch for the dimmable light, and a standard switch for the other.
Yes you can add it to your dashboard and control it remotely. I do.
1 Like
I have something similar that is Z-Wave, but a lot more expensive.
https://www.amazon.co.uk/gp/product/B017DV54ZO/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1
https://www.amazon.co.uk/gp/product/B01FW2AGSG/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1
Yeah they're similar functionality to those and the Fibaro Dimmer 2, the Shelly also handles from 10W without needing a bypass module.
Is the shell on this dimmer actually transparent blue? That clear-nostalgia sure hits in a good way.
1 Like
Yes but once the module is behind the face plate you don’t see it.
I'd just need to find clear faceplates 
minimum boxes are 16mm, tend to be rare nowadays, but if you're unlucky enough to have them nothing fits on them.
My house was built in 2000, probably on the cheap for the church next door that built it. I will take a plate off tomorrow to confirm.
Yup, no chance of fitting so sending it back. The switch itself looks nice though.
Thought I'd get a dimmer to try.
Fitted it to a plate and installed it ok.
HE found it as a generic zigbee dimmer and it is reporting its status ok which is good.
I'm not sure about the blue backlight being on all the time but at the moment I'm satisfied with it.
The dimmer itself is actually slightly smaller than the non smart one I took apart to fit this module.
2 Likes
If you read back on the thread you'll see someone found a way to disable the blue light. When the device reset (possibly after a power cut) the blue light came back on again. But if you look up the thread you'll find it. I've left mine on.
2 Likes
Ah ha. Thanks for that @Langas.
It does the trick.
The trouble is the next time I have a power cut I will have forgotten how I turned the blue led off. 
As an aside, do you know if these are repeaters or not. I've sent a query into Aurora asking the question but just wondered if you knew.
1 Like
According to the HE routing tables they are indeed repeaters.
2 Likes
A single 14W bulb each, typically though dimming behaviour is different with any dimmer due to wiring differences, etc.
I don't think that it adjusts the range as such, it adjusts the lower end output to stop flickering. Further experimenting shows that if that adjustment is different between rooms then the perceived rotary action is then different. So in one room that adjustment is minimal and it's one notch round on the rotary dimmer before the light comes on. In the other room that adjustment is higher, so it's more notches before the light comes on. So it's like the rotation on the dial is still doing 0% -100% but the light doesn't come on until X% based on that adjustment, if that makes sense.
With the Fibaro Dimmer 2 for example (that these Aone replaced) you could do all sorts of adjustments to adjust the dimming range / speed / end stops but the dimming range (0% - 100%) matched the output range, so 1% turns on the light at whatever its lowest output is. And it's less noticeable with a momentary switch anyway.
It does, but I don't know why they would program it like that it doesn't make sense.
Yes this is what I have, they are far superior for things like that. I haven't found anything else that do as good a job with the lamp as the Fibaro, I just wish they were ZigBee.
Apologies in advance for the long post, but I’ve tried to include as much information as I can.
After using Hubitat for around 1 year with my Ring devices and Hue hub, I decided to take the plunge and purchase my first Hubitat attached zigbee device, the Aurora Smart Rotary Dimmer Switch (as discussed in the latest Hubitat Live). This is ideal as being in the UK I don’t have a neutral wire to my switch, which the Aurora doesn’t require.
I’m on the latest Hubitat firmware release (2.2.0.128) and I’ve changed the Hubitat Zigbee channel to 11 so that it doesn’t conflict with the Hue bridge (26) or WiFi. Pairing to Hubitat is slow and requires a few attempts for the switch to be discovered and complete the initialise process, but after a few attempts it eventually gets there and is discovered as a generic dimmer device.
At that point I can control the dimmer from the device page and the status is updated correctly for both digital and physical operation of the switch.
Unfortunately, what I’ve then found is that after some time (could be 1 hour), the device does not recognise the state changes of the switch. Usually what happens is Hubitat activates the switch via a motion sensor rule, then later I switch it off manually, but the device status still reads “on”. This then means that my automated rules don’t work as they are checking the status.
When it’s in this state, I can still turn the lights on/off using the Hubitat device, but the status is not reflected and there are no messages in the Hubitat logs (even with debug on for the device). If I hit the refresh button on the device, this sometimes triggers some log messages (some of which look like they could be from previous operations) and the state is then updates as shown in the following log messages.
This is an example of when the state was not responding, then I hit refresh and the state is updated.
dev:3852020-05-08 08:32:37.244 infoGeneric Zigbee Dimmer was turned off [digital]
dev:3852020-05-08 08:32:37.242 debugevt- rawValue:0, value: off, descT: Generic Zigbee Dimmer was turned off
dev:3852020-05-08 08:32:37.234 debugParse: read attr - raw: 62A60100060A00001000, dni: 62A6, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 00
dev:3852020-05-08 08:32:35.491 debugrefresh
dev:3852020-05-08 08:31:53.798 debugParse: catchall: 0104 0006 01 01 0040 00 62A6 00 00 0000 0B 01 0000
Generic Zigbee Dimmer2020-05-08 08:32:37.268 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:0, lastHopRssi:-92
I’ve read that a firmware upgrade may be required for the switch, although I don’t know if this is the case for my switch. (I don’t have a ST or Aurora hub). I also don’t know the reason for the firmware upgrade and if the firmware upgrade would have any effect to the problem that I’m experiencing.
I’ve attached the logs from when the switch joins Hubitat, does this provide the information to understand which version of the firmware it’s using and if I need to upgrade, or is there another reason why Hubitat is not reflecting the true state of the switch after a period of time?
dev:3852020-05-08 07:57:03.893 debugParse: catchall: 0000 8004 00 00 0040 00 62A6 00 00 0000 00 00 4C00A6620CF2E0A1660000012100012100
dev:3852020-05-08 07:57:01.011 debugParse: catchall: 0000 8004 00 00 0040 00 62A6 00 00 0000 00 00 4D00A6620CF2E0A1660000012100012100
dev:3852020-05-08 07:57:00.966 debugParse: catchall: 0000 8004 00 00 0040 00 62A6 00 00 0000 00 00 4A00A6620A03040102000001060000
dev:3852020-05-08 07:57:00.817 infoGeneric Zigbee Dimmer was turned on [digital]
dev:3852020-05-08 07:57:00.815 debugevt- rawValue:1, value: on, descT: Generic Zigbee Dimmer was turned on
dev:3852020-05-08 07:57:00.498 debugParse: read attr - raw: 62A60100060A00001001, dni: 62A6, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 01
dev:3852020-05-08 07:57:00.398 debugParse: catchall: 0104 0006 01 01 0040 00 62A6 00 00 0000 07 01 00
sys:12020-05-08 07:56:59.891 infoCreated Zigbee Device Generic Zigbee Dimmer
dev:3852020-05-08 07:56:59.870 debugrefresh
dev:3852020-05-08 07:56:59.868 debugConfiguring Reporting
dev:3852020-05-08 07:56:59.849 warnconfigure...
sys:12020-05-08 07:56:37.647 infoZigbee Discovery Running
sys:12020-05-08 07:56:35.866 infoZigbee Discovery Stopped
app:592020-05-08 07:56:35.015 debugDiscovering Konnected devices on the network via SSDP
sys:12020-05-08 07:56:11.845 infoInitializing Zigbee Device 000D6FFFFE6C2981, 62A6
sys:12020-05-08 07:55:57.693 infoCreated Unknown Zigbee Device
sys:12020-05-08 07:55:35.861 infoZigbee Discovery Running
Generic Zigbee Dimmer2020-05-08 07:57:44.689 profileId:0x0, clusterId:0x8001, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:05.395 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:04.989 profileId:0x0, clusterId:0x8021, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:04.181 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:03.979 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:01.066 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:00.963 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:00.761 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Generic Zigbee Dimmer2020-05-08 07:57:00.439 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:59.634 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:59.432 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:59.330 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:58.927 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:57.518 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:57.316 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
62A62020-05-08 07:56:56.006 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:0, lastHopRssi:-91
Yes, it's not supported yet, it says in the live episode that their stuff will start to be supplied from the NEXT firmware version. So give it a month and you should be good 
. In reference to the devices firmware, you need the ST or their own hub to update that. How many of their devices do you have? It may be worth contacting them and asking about updates.
Also in future rather than copy and pasting logs it better too use the snipping tool and copy and past the screen. This is much clearer to read 
