-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Dimming lights using free@home #76
Comments
Hm, that's a really good question... According to the log, Bifrost is simply asked to dim the light in exactly the pattern you describe, and so of course, it does that. Is there any kind of log or debug output available from this "free@home" thing? I'm not familiar with it, but I assume it's some kind of home automation system? |
Yes, Free@Home is a KNX based system from Busch Jaeger (not my choice came with the house, but in general it works). Unfortunately pretty closed down, but I did manage to find a 'debug log' output. See bellow for a snippet. In this snippet you can view the last 3 steps of a dimming action of 3 lamps, 2 controlled by diyhue (6c2b59fffee5d164), 1 by bifrost (bc2411fffe4339bd). The last 3 commands are the commands send (i think) on release, as you can see they are identical to the second to last for diyhue, but for bifrost it is not (100 brightness, the original brightness before dimming). You can also see an error, I think Free@Home is unable to parse the response from bifrost? So, I think what is happening that on release Free@Home sends the last known values for a light (like with a single press, turning a light on). Instead of the last know 'dimming' value this is for the Bifrost controlled light still the original value. Does this somewhat help? Maybe we should start with unknown owner error?
|
@rernst thank you for the detailed logs. This is indeed pretty strange. I think there might be some minor difference between the reply from a hue bridge vs. from bifrost. Your hypothesis that this causes free@home to get confused sounds quite likely. Do you have a chance to join us on discord? I think that might make it easier to perform some tests, that would help determine the cause of this. |
As discussed on discord two new log files:
Setup:
Action: Dimming from full brightness to low. On release of dimmer button the brightness 'jumps' to 100% again for both lights. |
Two more extra log files, with dimming action from 100 down:
Interesting observation, log 1 shows sort of similar behavior, but instead of jumping back to fill brightness the lights jump back 1 step. (from 75 to 101). Log files: |
Back again with 'free@home weirdness'... Using free@home switches I should be able to perform a dimming action by long pressing up/down. This works however the light 'reset' to the brightness before the dimming action after I release the button. If I look at the bifrost log I indeed see API calls that (in this case) decrease brightness with 10% at a time, and a final call setting brightness back to 100%. See attached log file: bifrost_dimmer.log.
Do you have any clue what is happening? I do not see this behavior when controlling the same light using a original Hue bridge and/or DiyHue.
The text was updated successfully, but these errors were encountered: