RedShift isn't working for somereason

Bug Report

I have redshift plugged into my iw3/config as I show below, but the temperature stays 4500K I even manually put in my geo location and it stays 4500K.

redshift.location="ipinfo"

redshift.location="manual" redshift.lat="50" redshift.lon="-114" \

Affected module: redshift Version used: latest-git

I have redshift plugged into my iw3/config as I show above, but the temperature stays 4500K I even manually put in my geo location and it stays 4500K.

How to reproduce

put the above in your bar and it might go to 5000K momentarily, but then it will drop to a very blue color. if you type in a terminal redshift -l 50:-100 it will turn red, but not with the bar version and when you do it in the console it doesn’t change the bars number at all.

[RobCod]

Ahhh okay, I thought it actually pushed the settings to Redshift. I noticed last night that it set it to 4300k (14% nighttime) last night at like 11pm ish so I think it might be working in that regard, but maybe adding a max out option for people that want a lower temperature depth would be good.

Do you know of any place I can read into more on pushing that to a daemon to control it from the bar?

If you want to, I think I could add a parameter that changes the behaviour to actually also start redshift.

If its not too much extra work, that would probably be a good feature, I thought thats how it worked by how the documentation explained it haha

[tobi-wan-kenobi]

@RobCod If you add “redshift.adjust=true” to your parameters, bumblebee-status should now update the color temperature every time the module is updated (by default, once every 10s).

Hope it works for you & fixes your problem!