I learned this at CES 2018 and First Alert didn't like it. Didn't like it at all. In fact, they brought over someone else for me to speak with so they could try to save face and hush me up.
Luma was once a darling in the Wi-Fi industry. Well, all the way up to releasing their product. It seems they couldn't fill orders fast enough and when they did the folks waiting the longest still stood empty handed. It was feature short and owners and fans quickly realized it would be consumed by another product. It didn't have the features or the customer service to keep up with companies like Eero and Netgear. Fast forward to January 2018 and First Alert now is the proud owner of a mesh Wi-Fi company! Can you guess what they will put in their smoke alarm next?
I ask the person I was handed off to, "Why no announcement?" Answer, "We don't announce these type of things." He air-quoted, "Corporate." I grilled him more and encouraged an announcement if for anything, the people who have purchased Luma devices. They deserve to know. I got nowhere with First Alert. They were not going to budge and politely asked me not to write it. No scoop for you! I like this company so I obliged. Did they follow up? No. Did they thank me? No. I don't need a thank you but I kept my word. Well, I did call @jcollison to file the report with him so someone would believe me when the news finally did break. I knew it would, but I made a promise to a company, and I kept it.
This is a good fit for Luma because as I stated earlier they were no match for their rivals. I don't know if it is a good fit for their customers, early adopters, and fans however. I sold my Luma gear so nobody contacted me telling me the roadmap. Did they contact you?
It could be a better product now, I have no idea! I spoke with them at CES 2017 and they were excited for the new year but with reservation as they knew the road behind them was bumpy.
But hey, now we can have a smoke alarm with Wi-Fi in it! Let's just hope they don't do anything silly like put Alexa in it or make it a speaker.
Oh, guess I'm too late on that request. I hear it sounds "Onederful." All kidding aside, I like the idea of Wi-Fi in a product like this. Their roadmap will bear that fruit. I don't like "Alexa in the sky" and the sound of this speaker at CES was abysmal and will not compete with Sonos and all the new countertop smart speakers. Maybe it was just show floor noise but let's hope they improve upon that sound.
They hurriedly packaged the Luma app into their own in order to demo the Wi-Fi enabled Smart Smoke Alarm Combo device. So hurried in fact that they failed to remove a Luma Logo. Ya, busted. I knew prior to that though. I kept telling the demo person that this app looks familiar. "Isn't this the Luma app I asked?" Wow, did she freeze and stammer throughout the rest of the demo. "This looks like the Luma app," I proclaimed, and then boom. One little screen deep into the app. Luma Logo. BUSTED!!!
Not even a demo unit. You think they would at least send me a demo unit to hush me up!
There is a bright side for you Luma fans!
You can get a 3 Pack for $99
Source: Me, at CES 2018
These guys published first though. I kept my word.
Hi guys and gals, new listener to the pod cast and first time posting here. Anyway I finally took delivery of my Luma 3 pack. So far it’s been a bit bumpy road like the rest of you. I can vouch for it’s speed when it’s actually working! I have mine setup behind a Sophos UTM, I allow TCP 4242, TCP 4505 and TCP 4506 out so that they can connect back to the cloud. The odd thing is that they seem to be working in bridge mode! This is something I want them to do but it’s something I don’t think they should be doing with this current firmware. Is anyone else getting behavior like this? Any ideas as to why? I also get about 3 days of use before they decide to lock up. Not sure if this is a bug in the internet pause feature or they just wonk out. It doesn’t kill my wired network traffic just the wifi. The only way to restore connectivity is to unplug them one at a time. Just for the record I have not used the pause feature so it is not user error on my part!
Side note, I see a lot of dropped packets in the logs of Sophos and backup pfSense box. I will snoop around in the log files and check wireshark this weekend and see what I can see. Anyone have any ideas/solutions or similar experiences?
As LUMA's wireless mesh devices start to roll out, I imagine this topic will come up more than once so permit me to relate my experiences getting LUMA to play nicely in the sandbox with Sonos. Because there is so little literature on the topic at this point, my experience (and ultimate success) was mostly the product of trial and error. My setup is the ubiquitous antiquated MI424WR Verizon Actiontec cable modem/router. I have the following paired Sonos components: 2 sets of paired Play 1s, 1 set of paired Play 5s (1st edition), and 2 Sonos Connects. With the new wireless network, I had previously removed the Ethernet cable from my Play 5 located closest to the router. Once I installed all 3 LUMAs from my newly arrived 3-pack, and without any adjustments to my Verizon router settings, my Sonos app could no longer find the Sonos network. I tinkered with a variety of solutions, getting one pair of Play 1's to be recognized when my phone was in close proximity to them. However, as soon as I walked about 30 feet away, the phone app. could once again no longer find the Sonos network.
Well to make a long story short, with several solutions proving to be dead ends, I decided to plug an ethernet cable from the back of one of my Play 5 stereo pairs (the one that had formerly been plugged into the Actiontec router before Sonos went completely wireless) into the OUT port on the back of the LUMA, The In port of that device was plugged into my Actiontec router. All my Sonos components magically appeared. Moreover, I was able to travel throughout the house and even into my backyard without losing the connection to the Sonos components. I note that I did this first without disabling the wireless on the Actiontec router. That's the curious thing about LUMA - although you can run it as your only wireless, it appears you don't have to. Effectively, this means you can have some components on your 192.168.1.XX Actiontec DNS range, and others on the LUMA 192.168.55.XX range.
But my next test was to see if it would still work when I turned off the wireless on the Actiontec router. (I note that keeping the Actiontec wireless enabled effectively circumvented LUMA's ability to cut off internet service; devices would just reroute to the Actiontec router.) So I wanted to see if I could maintain my Sonos connection after disabling the wireless on the router. With the Play 5 now plugged into the LUMA and the LUMA, in turn, plugged into an open LAN port in the back of my router, I was pleased to see that the Sonos app continued to work even after the Actiontec wireless was set to off.
In sum, the simple, if not intuitive, solution turned out to be the best. No resetting the controllers or fooling around with the DNS server ended up being necessary. Just a spare ethernet cord was all it took.
Incidentally, while I am not blown away by the speed of the LUMA (which never seems to change according to the app and seems to be about double what my Speedtest app says it is), I am impressed by its range. I have a 4000 square foot house with very poor wifi range using the Actiontec router. With the 3 LUMAs strategically placed on the left, center and right sides of the houses, I was able to get excellent coverage throughout the house and a good 50 feet into the backyard. That alone has made the purchase worthwhile.
Hope this helps.