YahueV2 (Yet another Hue app, using Hue API v2)

[Sjakie 156]

Jan,

I blocked my kitchen QA so there will be no intervention for this light.

If I switch on I see:

it start with a brightness of "7" where does this come from?
My order was value 40 see next line.

Please login or register to see this code.

Please login or register to see this code.

 

[jgab 2,647]

1 hour ago, Sjakie said:

Jan,

I blocked my kitchen QA so there will be no intervention for this light.

If I switch on I see:

it start with a brightness of "7" where does this come from?
My order was value 40 see next line.

Please login or register to see this code.

Please login or register to see this code.

 

 

 

When you turn it on

Please login or register to see this code.

it also send the last recorded brightness value.
When you do

Please login or register to see this code.

it just sends the brightness = 40

If we don't pass the brightness when turned on we get the Hue default value (50%?)
Why 7? seems to be a value set when previous? dimmed? I try to make it a bit smarter in v0.2.41.

[Sjakie 156]

Previous setting is better now the light jumps on 100% and goes back to 40%.

I prefer it start on "0" and than it will go up to the number requested.

Most off my brightness settings in scenes are the minimum (1%) to have a smoother start of the light.

I discover the last setting in Hue app was 7% but it show off

Please login or register to see this code.

All my lights when switch off goes in steps:

Full>> normal>> dim>> soft>> candle>> off

100% >> 70% >> 40% >> 10% >> 5% >>off

This I need to replace with dimdelay

Edited May 9 by Sjakie
add scene

[Sjakie 156]

 

What is 429? Device 429 is a wall socket.

Please login or register to see this code.

 

[Sjakie 156]

Jan this does't work anymore:

Please login or register to see this code.

Light starts at last brightness? value 40 and stays on 40.

Can we go back to previous setting where I saw the 7%

[jgab 2,647]

31 minutes ago, Sjakie said:

Jan this does't work anymore:

Please login or register to see this code.

Light starts at last brightness? value 40 and stays on 40.

Can we go back to previous setting where I saw the 7%

Not really...

but there was a race condition. See if v0.2.42 fixes it ? 

[jgab 2,647]

13 hours ago, Sjakie said:

 

What is 429? Device 429 is a wall socket.

Please login or register to see this code.

 

This is an example when you send rapid commands to the bridge, 2 PUT at the same time.
429 is the error code when the bridge denies the request, not the device.
It will throttle the commands, backing off 200ms, 400ms etc
Unfortunately there was another (refresh) trying to run at the same time, and it then got denied by the bridge (when the bridge gets too many requests it gets angry and refuses to accept commands for a short time). Anyway, refresh denied and it retries.
Fixed it to be smarter in v0.2.44

[Sjakie 156]

This is better,

40 was the last brightness value

start at 40 and goes up to 100

but if value = 20

it starts also at 40 and goes back to 20

I think it should start at 1% and due to value setting it will go up.

How to avoid rapid commands?

I only use rooms and zones

 

With Hue app I switch 73 selected lights on >>> no error only:

Please login or register to see this code.

 

Edited May 10 by Sjakie
All selected lights

[jgab 2,647]

21 minutes ago, Sjakie said:

This is better,

40 was the last brightness value

start at 40 and goes up to 100

but if value = 20

it starts also at 40 and goes back to 20

I think it should start at 1% and due to value setting it will go up.

How to avoid rapid commands?

I only use rooms and zones

 

With Hue app I switch 73 selected lights on >>> no error only:

Please login or register to see this code.

 

It's kind of tricky when you want to start from a specific value when you turn on.
You could add a wait between, but then you would see the initial value faded to if you have set transition....

So, setValue (or :value = x) turns on the light if the value > 0, this is according to how light QAs work. This means we can't use that as a way to set a starting dim value without the light turning on.
In v0.2.46 I have added a command QuickApp:setDim(value) that sets the dim value of a Hue light without turning it on.
This means you should be able to do
fibaro.call(id,"setDim",1) -- there is no ER command yet for this
:value = 50

There is also a QuickApp:fadeTo(start, stop,delay) command that does it in one
fibaro.call(id,"fadeTo",1,50,3000) -- turn on and fade from 1 to 50 in 3s

No ER commands for these yet, but I may add in the future. Now just use fibaro.call

There is also a rawCmd to send whatever directly to the bridge.
Ex. 

fibaro.call(id, "rawCmd", {

on = {on=true},

dimming = {brightness=50},

dynamics = {duration=3000}

})

 

[jgab 2,647]

The problem with setDim/fadeTo is of course that they only work with Yahue lights.
But if you have a lot of Yahue lights, it can make sense to optimize for that.

[jgab 2,647]

For ER6 you could patch in the commands

Please login or register to see this code.

This would allow you to do
id:setDim = 1

and
id:fadeTo = {1,50,3000}

 

[Sjakie 156]

If I proper under now I should be able to do like in the past?

Please login or register to see this code.

Problem till now was if working with zone brightness 1% all lights are on so I changed it when I step over to YahueV2

Please confirm

[jgab 2,647]

9 minutes ago, Sjakie said:

If I proper under now I should be able to do like in the past?

Please login or register to see this code.

Problem till now was if working with zone brightness 1% all lights are on so I changed it when I step over to YahueV2

Please confirm

fibaro.call(id,"setDim",1) will set the dim value but not turn on if the light is off.

This is strange
bedroomLight:on or bedroomLight:setValue 65

You mean 
bedroomLight:isOn | bedroomLight:value = 65

or?

[Sjakie 156]

Please login or register to see this code.

 

[jgab 2,647]

Wait. I'm thinking about this a bit more.
The setDim and fadeTo is still there, but I made another change.
setValue(0) or :value=0 will set the light immediately to off, and dim value to 0 ignoring the transition.
turnOff or :off will turn off the light using ev. transition value.
This distinction between setValue(0) and turnOff allow us to be more "compatible" between Hue and other fibaro lights.

So now it works like.

 

Call	Slot	Bridge PUT	Transition
setValue(0)	'off'	{on:false, dimming:{brightness:1}}	no
setValue(50)	'PUT'	{on:true, dimming:{brightness:50}, dynamics:...}	yes
turnOff()	'PUT'	{on:false, dynamics:...}	yes
turnOn()	'PUT'	{on:true, dynamics:...}	yes

 

 

 

So, 
:value=0; -- turns off (if on) and primes dim value to 1%
:value=50; -- sets dim to 50% honoring the transition/dynamics.
will fade up from 1% to 50% if transition is set for a Hue light.
For another light (z-wave) it will just turn on the light to 50% (we have no fading there).
For proper fading across hue and z-wave one should use the levelIncrease I guess.

So, yet another release v0.2.47 pushed...!

[jgab 2,647]

39 minutes ago, Sjakie said:

Please login or register to see this code.

 

Yes.

[Sjakie 156]

ok looks much better now. Give me some time to see the general result if it's dark.

Do you have some "smart" solution for:

there are around 20 scenes to follow up and if not stopped repeat

Please login or register to see this code.

So I need to change all lights in:

eethoek.Eethoek_Lampen:value = >0; --to switch on with value "x"

 

eethoek.Eethoek_Lampen:value = 0; -- to switch off instead off eethoek.Eethoek_Lampen:off

 

eethoek.Eethoek_Lampen:isOff is only a cmd from HC3 and is still not synchrome with HC3?

Kitchen light in HC3 isOn & in Hue app off!

 

Why I see in Debug window Yahue (397)

Please login or register to see this code.

 

Edited May 10 by Sjakie
send message

[Sjakie 156]

Jan, congratiolations!!!

Kitchen light is off!! Or value= 0 or other color setting did the trick.

So I am happy I can remove a lot of rules.

 

How to retrieve the present color setting of the Hue light? I want to safe the settings of my kitchen light for later.

 

Edited May 10 by Sjakie

[Sjakie 156]

Jan, this morning no light activated.

Screen full of 429 errors I suspect after switching hal "zone" and bathroom "room" on/ off last night

As mentiod before if I switch on all lights I don't get an error so I don't understand flooding the bridge?

Bridge restarted lights are operational again

Please login or register to see this code.

 

[jgab 2,647]

Ok, I had a bug when I do a backoff for the first 429 when doing a refresh with GET (the last version was a fix for sending commands with PUT). 
In general, it seems that you are running into 429 quite often... so my thinking is that I'm too aggressive with the backing off logic.
In v0.2.49 the retry logic/back-off is a bit more relaxed.