Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - LightStatus Dim vs SetDim<Abs/Rel> #17

Closed
PhilWheat opened this issue Feb 7, 2014 · 8 comments
Closed

Question - LightStatus Dim vs SetDim<Abs/Rel> #17

PhilWheat opened this issue Feb 7, 2014 · 8 comments

Comments

@PhilWheat
Copy link

Just checking - has anyone played with the Dim value? It seems odd that it's a UInt on the reporting and an Int on the setting.

I'm digging into it, but thought I'd ask if others have any experience with that value.

@magicmonkey
Copy link
Owner

I've not - the one time I went near it I managed to crash my bulbs such that they needed a reset :-/ The difference in types could be me guessing, I've not network-captured any relevant packets so there's not much to base on.

@PhilWheat
Copy link
Author

OK – sounds like I just need to not worry about those packets for a bit. Since I keep the bulb values in synch with my local objects., I can pretty much do the same functionality with the Light settings packet, so no missing functionality.

Thanks!

From: Kevin Bowman [mailto:[email protected]]
Sent: Saturday, February 8, 2014 5:07 PM
To: magicmonkey/lifxjs
Cc: Philip Wheat
Subject: Re: [lifxjs] Question - LightStatus Dim vs SetDim<Abs/Rel> (#17)

I've not - the one time I went near it I managed to crash my bulbs such that they needed a reset :-/ The difference in types could be me guessing, I've not network-captured any relevant packets so there's not much to base on.


Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-34559411.

@nathanael-k
Copy link

Hey, this is Nathanael from LIFXtend,
I was also just playing with the dim, and my bulb stopped working. Seems similar to what you experienced. How did you get the bulb to work again? I tried the small switch on the bulb and also turning it on and off again fast several times, but it didn't do the trick.

Cheers, Nate

@riverar
Copy link
Contributor

riverar commented Feb 21, 2014

Hmm, just looked -- The updated Android application also has this uint vs int quirk, might be a firmware bug. Perhaps this is to allow for getting light state during a relative dim transition (e.g. -10 = that bulb is decreasing, and has not completed, in dim by 10)...

@nathanael-k
Copy link

Where did you get this information? Is there a dim command implemented in the new android app?

Just a heads up: Two of my bulbs have a failed power supply after trying out the dim command.
So please wait for the new firmware, and if someone could update the information in the command overview to warn people from trashing their bulbs, that would be great (I have no idea how I could do that myself with github, sorry)

@nathanael-k
Copy link

Also for me it would make sense for a relative dim to use int, as you could dim +10 or dim -10, increase or decrease the brightness.

@riverar
Copy link
Contributor

riverar commented Feb 21, 2014

App disassembly. I'll add a note right now. That's pretty scary -- the bulb should have safeguards in place for this. Makes me wonder about the set rail voltage packet types now too...

riverar added a commit to riverar/lifxjs that referenced this issue Feb 21, 2014
@nathanael-k
Copy link

I guess that's one of the kinks that make the api take so long.
Thanks for the note.

2014-02-21 11:05 GMT+01:00 Rafael Rivera [email protected]:

App disassembly. I'll add a note right now. That's pretty scary -- the
bulb should have safeguards in place for this. Makes me wonder about the
set rail voltage packet types now too...

Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-35714419
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants