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?
New Luma owner here. Have to say that I am not that impressed with the Luma system as a whole. I like the WiFi signal, but frankly that is only a part of a home network. I am really disappointed in the lack of visibility to the system. I get that it might gear more toward "Plug and Forget" type people, but you still have to have some visibility to troubleshoot problems.
So... here is mine...
Setup the new Luma 3-Pack last night throughout my house. The main Luma is connected to the cable modem on the in port and the out port is connected to an 8 port 10/100/1000 switch (#1). It seems like the other wired devices on the switch are working fine. I have another hub/switch (#2) connected to #1. I have a Tivo box that I plugged into #2 and it does not seem to pick up a DHCP address.
For troubleshooting purposes I moved the Tivo connection to #1 and still no DHCP. I reset the master Luma (pulled the power) and it eventually came back online and did offer a DHCP address to the Tivo. I thought that was the trick and so I reconnected Tivo back to #2 and no DHCP. So... I connected back to #1 and still no DHCP. I ran out of time to try the whole reset Luma thing again, but I was wondering if anyone else has seen issues with DHCP and wired devices? It seems like once it sends them out, it does not try again.
It is also very disappointing that there is no visibility to any of the configuration aspects of the Luma settings. Like how long the lease time is, etc.
I guess I might have to spend the weekend using wireshark to see if I can see what is going on, just wondering if anyone else has worked through any DHCP issues with them.
On a side note... very nice site, lots of great information! Thanks!