HABridge sometimes executes both "on" and "dim" command #923
Comments
|
Yes, this will occur when the ha-bridge receives a call that as both on and dim in the hue api request. If you do not want this to behave this way, select the on first dim in the device edit tab. |
|
Did this answer your question? |
|
I can try it for testing. |
|
Set the device to "On First Dim" and that will do what you want. |
|
No, I can't get the old behaviour back! I use HA Bridge only as a bridge for Alexa, I don't need and don't want to have it any logic off its own, like on/off state. I have built quite some logic around this in FHEM, e.g. if I say "Alexa, turn Sat Receiver to 50%", it turns my Enigma-Receiver on and puts it to standby after some time. Otherwise I can't use this receiver with Kodi. All the logic is done in FHEM, not in HA Bridge! Also, I like to point out that it would be much better to implement new options as optional and not to be enabled by default on an existing installation. Now I have to manually update 124 HA Bridge devices! |
|
I do have a question: What system is calling the ha-bridge where you get this behavior? Alsom the payload would contain both an "on" and a "bri" command to get the behavior you are having. |
|
I don't understand your question. I am using various Echos to call HA Bridge? This behaviour is produced by every Echo I use (Show, Echo Dot, Echo). I don't understand the second sentence? |
|
turn on debug for the HueMulator class and post your log |
|
On it. |
|
This is the log for: on, then off, then 50%.
|
|
On with first dim = False.
|
|
This is the new behavior as expected as it sends the on, to turn the device on and then sends the dim. I would have to add a new setting to treat the request containing both to only execute the dim portion. |
|
YES, PLEASE. THIS IS NEEDED!!!! |
|
Is this new Alexa behaviour to send "on then dim" or is this just HA Bridge internal. |
|
Also, I'd like to offer my support in testing with RCs if you implement this feature. |
|
It may be both, I remember in the beginning that Alexa was only sending the dim portion when I tested. And I see now that you are getting the on and dim together. The ha-bridge was changed in 5.0.0 to send both as other systems needed the on to be sent before the dim command would take effect. |
|
Yes, I understand that some Systems might Need it. It would be very much appreciated if you add the Checkbox as described above to just execute Can you implement this? |
|
Will put this in the enhancement list |
|
@bwssytems I would like this feature too, some of my X10 devices remember their state internally just like @heikoh81 blinds. An ON command, instead of DIM command, would only turn them on at their memory state. Thanks! |
|
Is there some Progress on this issue? |
|
Nope, taking a breather.... maybe in a couple of weeks |
|
I'd like to expand on this. I like @audiofreak9 use X10. Devices that remember there last state if dimmed down to 100% think they're on. The option to send a off prior to dim would be beneficial in cases like this. |
|
I'll take a look at this, was trying to be more efficient in operating on what the command sent would achieve. |
|
I think I will add another flag that will override using on when there is a dim present. This will be overridden by onFirstDim if checked. |
|
This would be very nice. |
|
@heikoh81 Go test the new release candidate as it is in there..... |
|
Hello, I habe the same Issue with Shelly 2. After the update from 5.2.1 to 5.2.2RC3 the error is gone. |
|
Sorry to warm this up - but i have this error again. The options "On when Dim is present" and "On with First Dim" are both off - but i tried all combinations, nothing worked. Can someone guide me to the right direction? Many thanks! |
|
What version of ha-bridge are you using? |
|
Hi, its 5.3.0 |
|
Please turn on debug for the Huemulator class in the log section and then execute the command and post the log please. |
|
Hi, this is the log. I tried to dim the device "Deckenleuchte" to 30%:
|
|
I'm seeing the same issues with Echo Dot V2's, 5.3.0, and "On when Dim is present" and "On with First Dim" are both off. Edit: It appears the Echo's are sending two different requests. First "On" and then another with the bri command. If I tell alexa to turn the bar on I only see a single request (on:true) with no bri value, or second PUT with the bri setting. I wonder if there is a different way the emulator can respond to Alexa to make it not do this? Alternatively a somewhat hacky workaround seems to simply wait ~1 second and see if a brightness event comes in before doing anything.
|
|
any real solution to this? I want only dim to fire, regardless of what alexa thinks the device state is. "OnFirstDim" works to send only dim if alexa thinks the device is already on, but if the device state is off and a dim command is received, it still sends the ON command before the dim. |
|
That is a different twist on that setting. If bright request present with on, only send dim. This would be an enhancement. |
Would be nice if it could be found in the next version |
|
Hi, this is exactly what i am looking for! Would be great if you could implement that!
…--
Von meinem iPhone aus gesendet
Am 28.12.2019 um 17:17 schrieb BWS Systems <[email protected]>:
That is a different twist on that setting. If bright request present with on, only send dim. This would be an enhancement.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#923?email_source=notifications&email_token=ALXEXBGET3CEN7LT3W2GP6TQ2532JA5CNFSM4EVMF6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYM42A#issuecomment-569429608>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALXEXBHGCURFRRBR33EF37TQ2532JANCNFSM4EVMF6QQ>.
|
|
Please open a new issue with the description of what we want to do. I can then make that an enhancement as this issue is for a different request. Thanks |
|
Done: #1171 (comment) |
Hi,
with 5.2.0 RC23 and 5.2.0 Final I noticed that sometimes, not always, HABridge executes both the on AND the dim command.
I just do simple URL Calls with HA Bridge. I noticed double log entries in my FHEM system when using Alexa and started investigating.
I narrowed it down to HA Bridge devices that both have a on command and a dim command.
I'm not sure if the problem is with Alexa or HA Bridge, though.
This is what fhem is logging:
2018-03-14_17:37:02 AlexaSonnenschutzWohnzimmerTuer on 2018-03-14_17:37:03 AlexaSonnenschutzWohnzimmerTuer 100 2018-03-14_17:37:23 AlexaSonnenschutzWohnzimmerTuer on 2018-03-14_17:37:42 AlexaLichtSchlafzimmerBett off 2018-03-14_18:22:34 AlexaLichtStudio on 2018-03-14_18:22:34 AlexaLichtStudio 100 2018-03-14_18:40:51 AlexaKamerasInnen off 2018-03-14_18:41:38 AlexaDreamboxStudio on 2018-03-14_18:41:38 AlexaDreamboxStudio 50 2018-03-14_18:43:49 AlexaFernsehenEssecke on 2018-03-14_18:49:32 AlexaLichtCouch on 2018-03-14_18:49:32 AlexaLichtCouch 100 2018-03-14_18:53:55 AlexaLichtCouch off 2018-03-14_20:23:41 AlexaFernsehenEssecke off 2018-03-14_20:24:26 AlexaHeizstrahler on 2018-03-14_20:24:26 AlexaHeizstrahler 100 2018-03-14_20:25:17 AlexaLichtStudio offAs you can see, some time entries are double; on and the dim command for 100 percent.
Sample entry for Heizstrahler:
Type = HTTP Device
Target Item = http:https://192.168.178.230:58083/fhem?cmd=set%20AlexaHeizstrahler%20on
HTTP Verb = Get
Content Type = Text/HTML
Dim Item:
http:https://192.168.178.230:58083/fhem?cmd=set%20AlexaHeizstrahler%20${intensity.percent}
Greetings from Germany,
Heiko
The text was updated successfully, but these errors were encountered: