Turning devices off sets them to minimum dim value

[Scotto811]

Seeking some help, as it's 3AM and my brain is fried. I tried searching but hoping there is a simple solution for my problem.
I use an echo to control my Hue lights, as well as a HS3 controller to bridge my Insteon keypads to all my Hue lights (most lights have their own individual 6 pad for on/off scene control with load controlling disabled). When I use the Insteon keypad to turn lights off, it turns the lights off perfectly, but sets the bri value to the lowest setting. So when I then control the lights from the echo they come on as dim as possible. Is there a standard setting for when the lights are turned off? Also, I don't see a Jowihue action to turn them off, any chance we can get that to simplify things?
I use Jowihue to set numerous scenes and brightness levels so not sure I want to click the "convert all dim devices" and not even sure if that would solve my problem.
Any help is much appreciated folks! Thanks

[w.vuyk]

Scott,

Welcome to this forum

You should be save to convert your JowiHue devices as long you do not have events directly accessing the bright devices. Looking at the events you posted it seems you are using mostly the JowiHue actions, which won't be affected by the conversion at all. So I would even advise you to do it. After that you should be able to control the Hue light by Echo on Homeseer (it enables the dim commands). Challenge is that the Echo is not available in europe, so never could really test it here.

There is no JowiHue action to switch a light off, as you can do this by action on a device. I am trying not to create to many double functionalities in the plugin when things are already available on HS3 level

As for dimming when a device is switched off, this is done because the option for transition is set. When a light is switched of with transition set, it will dim first and then go off. This is functionality on the Philips Hue bridge and I cannot change it. The only way around this is setting the standard transition to 0.

Wim

[Scotto811]

Thanks for the quick response. I worked on this last night and set the transition to 0 but it doesn't resolve the issue. Even though the transition is instant it still sets the bulb to the lowest bri level.

I thought maybe if I change the echo group to just control the Insteon keypads, instead of the Hue devices then maybe that would solve the issue, but the event doesn't trigger unless the Insteon button is manually / physically pressed.
I then thought about setting the bri value after the event has been triggered, but that just turns the light back on, instead of just setting the last known value to an acceptable brightness.

I spoke with some other home automation people here at work (I work for Panasonic) and they discussed similar issues, as the Echo really only turns the Hue bulbs to their last known values (color, bri, etc). So if you trigger a scene, Echo will only turn that light back to what it's previous values are.

I haven't tried clicking the "dreaded" convert all dim devices button yet, but I will try that tonight and hope for the best.

I understand not wanting to double up actions, just wondering if we create an action to turn the bulb completely off, instead of dimming it to a value of 1 as homeseer does. I've head other services do this as well, as maybe the Hue API doesn't allow for a true "off" setting?

If you need access to an Echo, maybe we can get creative I can give you access to my VPN here in CA and you can operate one based off my US account for development (if you want). Let me know and maybe we can work something out. I currently have two Echo and one Dot, as they work so nicely to control things.
Scott-

[mikaluch]

I follow Wim's advice, although I did it before I read it because it seems to me the right way to do it. My first choice is always "control a device". Why go through a plugin if it isn't necessary?

In fact, if you are telling Echo to do something with lights, why have it go through HomeSeer at all? "Alexa, office lights on/off/50%" It doesn't require creating events.

[w.vuyk]

I spoke with some other home automation people here at work (I work for Panasonic) and they discussed similar issues, as the Echo really only turns the Hue bulbs to their last known values (color, bri, etc). So if you trigger a scene, Echo will only turn that light back to what it's previous values are.

Scott-

Scott,

I do not know how the echo is doing its job, if it controlling Hue's directly, it might save the last setting despite the bridge reporting a bright value of 1.

What the the internals of programming done for an Echo are, are unknown to me. All I did with the new release was enabling dim values for it, so if homeseer gets a command passed from the echo, it can pass it to the plugin and get executed. I don't know what I can do from this end?

Wim

[mikaluch]

The way Echo works with lights seems to be variable. If you give it commands while sniffing packets it seems to use both the Hue Bridge and send some commands itself. It only uses HomeSeer for events in my system.

I linked it to the Hue Bridge(s) and set up groups in the Alexa app for the lights I want to control by voice. I poll them every 5 seconds which doesn't seem to be much of a network load so the HomeSeer status remains correct.

[Scotto811]

I follow Wim's advice, although I did it before I read it because it seems to me the right way to do it. My first choice is always "control a device". Why go through a plugin if it isn't necessary?

In fact, if you are telling Echo to do something with lights, why have it go through HomeSeer at all? "Alexa, office lights on/off/50%" It doesn't require creating events.

I don't use homeseer / echo at all. When you control the lights with the physical switches, is when you get the issues.
So if I turn a light off with a physical switch, then command the light back on with Echo, you get a light that's dimmed to it's lowest value.

[mikaluch]

What physical switch are you using? It must dim the light before shutting it off. As Wim said, when you turn a light "on" it returns to the last dim level and color settings it was at before it was shut "off".

[w.vuyk]

I don't use homeseer / echo at all. When you control the lights with the physical switches, is when you get the issues.
So if I turn a light off with a physical switch, then command the light back on with Echo, you get a light that's dimmed to it's lowest value.

Scott,

I am surprised hearing that. The biggest complaint toward Philips at the moment is that, if you use physical switches, the light turns on at a full white and bright status. Users want that the bridge would follow the last setting of the light at least for the colour?

And Philips is argumenting that this cannot be honoured as they 'do need to comply to fire regulations' what means the light has to go to full bright if a wall switch is used in case of fire hazards?
First of all, if an echo controls a light, does it control a physical (zwave?) switch? And if it did, how did you use the last value of a light, without first going to a full bright for at least 2 seconds? The bridge will not allow you?

Wim

[Scotto811]

Sorry everyone, I'm travelling internationally for work at the moment and it was hard to get some time to "nerd out"

A little about my setup;
> I've hardwired all Hue bulbs to constant power so they never lose their last values
> I've used Insteon on the entire house, and using six button controllers as scene controllers only, no load controlling for my Hue lights (photo attached of kitchen cabinet lights)

I tried converting all lights to with the dreaded dim button, and that doesn't help either. I'm guessing the issue is on the Hue side, as it usually is. I'm actually considering buying some Lifx bulbs to see if that's any better / faster / more reliable. Anyone use HS with Lifx bulbs here? I've also heard of some complaints that the hue bridges must be wiped after purchase because my hub is doing some very weird random things with my lights on occasion, has anyone had issues with that?

I'll try to get a video of exactly what I'm talking about later this week when I'm home.