vakkotaur: Centaur holding bow - cartoon (mr yuck)


Sometime last year I bought a fancy bluetooth-enabled LED bulb (name: iSuperBlue) that could be controlled from a phone. It's one of those good ideas that doesn't quite work, at least not yet. The idea is neat: An LED bulb that be controlled somewhat remotely by a device you're likely to have with you anyway. The color can be changed. The brightness can be changed. By using the phone's microphone, the light can change with sound for some effect. The light can blink or fade on and be used as a visual alarm clock. And it can do that, sort of.

It's a real rascal to get the bulb and the phone to pair up. If the connection lost, by say, walking away with your phone, it can mean needing to cycle power to the bulb and restart the phone. Not a very friendly remote control setup. If I had only my current in-use phone, the bulb would be pretty much useless - turning it on by the main switch has it cycle through some colors, which might be a nice diagnostic, but is lousy for a "light up this area now" bulb.

Fortunately, I had my old (smart)phone and it can do bluetooth. As long as the power stays on, and the old phone remains parked on my nightstand, the pairing holds. The fade-on is nice, but it's a set speed and the final brightness seems to be less than full or the way to set it is not at all obvious. I'd like to slow the fade on and make it more dawn-like, have it come to full brightness, or at maybe even start red or pinkish and change to white - like real dawn does. That would seem a great, slow, easy on the system aid to waking. Since I currently work nights, the simple expedient of opening the blinds won't provide this.

But with the old phone as a dedicated remote, and giving up on a nicer fade-in, things are workable yet still amiss. Sometimes the light fades on and is simply on, as I wish. And sometimes it blinks or fades brighter and dimmer and brighter and dimmer, cycling - something I do not want. Sure, it might wake me up more effectively, but also more annoyingly (and I have a sound alarm, to be sure, anyway) and once awake I want a steady light. As if that wasn't irksome enough, the app for this thing is not just flaky about bluetooth. The alarm [SNOOZE] [DISMISS] buttons are fine and work as expected. The simple "ON/OFF" button is part button, part dial (dial the brightness). But it's not at all easy to just turn the thing on or off without changing the brightness. And the button is a circle.. and somewhere near that circle, but not exactly matching, is the active ON/OFF area of the screen.

I like LED lighting. I like the idea of this bulb. But no matter how much I like the idea, I do not like the lousy way this one "works." I'm keeping it, as I can get it to sort of do what I want, but will NOT buy another of this make, and I suggest nobody else buy any iSuperBlue either. Wait until someone else does it right.

What needs to be done to do it right? Absolutely required:

1. The bluetooth connection needs to resume/reconnect automatically and reliably.[1]
2. The ON/OFF region of the screen should be the same as, or at least within the ON/OFF image on the screen.
3. The brightness control must be 100% independent of the ON/OFF control.1
4. App features that demand a phone MENU button should be moved - not all have this as hardware, alas.
5. Blink off means blink OFF, and it stays off.

Be nice to have:

6. Control of fade-on speed.
7. Control of initial and final color (and brightness) of fade-on.

I expect someone will get this right, eventually. But it's going be a while before I risk more money on a device like this. I'll want to know the thing will work correctly.




[1] No, I do NOT want a "wifi" controlled bulb. How do I set a proper password or such, at a minimum? And I'm not about to let things be open to the point where some neighbor or drive-by can control MY light(s).

vakkotaur: (computer)


I've been running Linux of one sort or another as my primary ("desktop") operating system for over a decade. While I am not The Ultimate Linux Geek or such, I have at least a fair idea of what I am doing and going back to Windows makes my teeth itch. There has been significant progress in making Linux readily usable for "the general public." While there are distributions like Slackware and Arch which expect the user to be able to pop the hood and adjust things, there are also distributions like Ubuntu and its variants and descendants that are made with the idea that the only time a user ever sees a command line is if s/he really wants to use that. It's a wonderful objective. I'd love to be able to tell people "Just use $DISTRIBUTION and everything will be taken care of." But, alas, I cannot.

The nightmares of years past, often squirrelly audio and dubious video seem to have been vanquished. CoDec issues are either obviated or readily cured with single package of a graphical package manager, if not by a system offered "Download and install these now?" option. And then we come to bluetooth. That thing that pairs up your phone with your headset or such, and after the initial setup it "just works" and you no longer think about it unless you change hardware somewhere. That's how Linux should handle bluetooth, too. Keyword: "should" And yet, that is not the case.

I had been using Xubuntu 12.04 and while bluetooth required a bit of work to install (more than one package, editing of a config file - the sort of thing *buntu tries so hard to not need) after that setup, things worked. A reboot didn't stop that. Things that worked yesterday, would work tomorrow just the same, without any intervention.

And then after I screwed something up (admittedly my own fault) I went to Xubuntu 13.10 and learned things no longer worked that way. The same is still true for Xubuntu 14.04 and therefore Mint 17 as well. The bluetooth package installs nice and easy, graphically, and appears to work. It scans around and finds bluetooth devices. But if I want my headset to work? Nope. Not until I invoke the incantation, "sudo pactl load-module module-bluetooth-discover" which is odd as the system discovers things fine, it just doesn't work with all of them.

Someone, somewhere, updated something. It was meant well. But everyone seems to have rushed to embrace the update which was not yet ready for one of the more popular things to do with bluetooth: transmit and receive audio. The result is that pretty much every distribution I have tried of late has this exact same breakage. For me, it's merely annoying. If it were others of my family it would likely be, "It doesn't work." or "Why can't it do that automatically?" (I've wondered that one myself - it should happen automatically, yet does not.) or simply, "That's stupid" - and I agree. it is stupid. It's this sort of nonsense that impedes things.

Ah, but that's not all, folks. Now if I should take my headset out of range and lose the connection, all that should happen is a lost connection - and an automatically regained connection once I am reliably back in range. Instead what can happen is things stop working altogether and the incantation must be invoked again - which has a curious side-effect of quietly and invisibly breaking something else: Skype looks like it's still connected and working, but is not. And trying to close it doesn't truly end the process. Once more I must resort to the command line and issue "kill -9 <process_number>" Yes, with the -9 option or the unwanted process runs on anyway. Then, and only then, can I restart Skype and be able to actually communicate with it. And just this once, I do not believe it is Microsoft (which now owns & runs Skype) that is screwy. Microsoft is busy breaking it in other ways just now.

The frustrating thing is not simply that it's weirdly broken now, but that it is weirdly broken now when it worked exactly as it should (aside from initial setup being fiddly) earlier. Now, this will almost certainly be resolved in time, but how much? I've already gone through Xubuntu 13.10 and the problem remains in 14.04. And I'm not just picking on *buntu here. PCLinuxOS has the exact same breakage. Korora (a Red Hat derivative), at least the Xfce edition, didn't even seem to have bluetooth that could be made workable at all when I last tried it. Dangit, solved problems should stay solved. This is a reinvented wheel, but while new, it is not yet properly round. Don't ship it unfinished.

Profile

vakkotaur: Centaur holding bow - cartoon (Default)
Vakkotaur

March 2024

S M T W T F S
     12
3 456789
10111213141516
17181920212223
24252627282930
31      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated 3 January 2026 19:30
Powered by Dreamwidth Studios