Will do. Any particular command etc you want me to use?
wow, that was quick! I’m really looking forward to use your latest additions.
I have no IDE set up yet and I’m on stable 2.3, so I guess I can’t use it yet, but I’ll see to that when I have a bit more time at hand.
No, nothing special.
Yes, that is right. You need at least OH2.4.M5 milestone.
No issues to report so far.
Dropping this into my addons folder doesn’t trigger anything visible. It just won’t start or even resolve the binding. Karaf console shows nothing related to hue binding.
What I’ve tried is:
- Remove the current snapshot hue binding installed through paperui->addons
- Copy test version to addons folder
- Restart oh multiple times with and without cleaning cache
- Updated oh to latest snapshot build #1422
One weirdness that I observed was when I removed or installed the current version few other bindings got restarted. Those bindings were astro, network and systeminfo bindings. Also dashboard and all uis got restarted.
Next I tried to revert back and install current snapshot. It worked just fine and it discovered my hue bridge.
So my question is: How to properly debug this?
Which OS do you use?
Did you install the
Did you try to clear the cache?
OS is Debian 9 and I have cleaned the cache.
Have not installed openhab-addons. What does it exactly contain? Is it something that is needed when manually installing bindings?
It contains all add-ons. No, I guess you do not want it.
When you choose to install an add-on, openHAB will download it from the internet on request. If you plan on disconnecting your machine from the internet, then you will want to also install the add-ons package (See https://www.openhab.org/docs/installation/linux.html#apt-based-systems).
Is it possible for you to provide me a DEBUG log? Thanks.
Please specify from where do you want debug logs? org.eclipse.smarthome.binding.hue maybe?
There’s nothing in the logs. Not even complaints about missing requirements. Nothing.
Stupidest mistake in a long time. Didn’t unzip the package but just removed .zip extension by renaming.
(Latest test bindings I’ve used used this technic for uploading bindings. Was it so that github doesn’t accept .jar files?)
After some testing all seems to work. Configured everything using .thing file.
What is the function of “sensor status” under bindigns configuration parameters? Is it really a indicator and if so, shouldn’t it be as own channel? Or can you somehow turn the sensor off this way? Seems a bit weird when also dimmer switch has this option.
Okay, I am glad you got it working.
The answer is:
|on||bool||Turns the sensor on/off. When off, state changes of the sensor are not reflected in the sensor resource. Default is “true”|
You can activate and deactivate a sensor via this configuration. Currently this feature is not working in the provided test version.
Great Work Christoph,
on openHAB 2.4.0 Build #1421 running with openHABian on a PI and after deactivating the Hue Binding in PaperUI and restarting OH with your test-binding in the addon-folder my 5 Hue-Sensors works as expected
Would be very awesome to have everything that still works in Apple’s HomeKit also works in EclipseSmartHome and/or openHAB!
Of course. As I am no Apple user I am afraid you have to help me in this case. Which features do you mean?
See my earlier post:
Now theres this recent post describing similar behaviour. UIs starting and stopping when you install or remove the hue binding? Anyhow for me the hue binding has worked properly all the time. I’m running Zulu java if it matters. Is this something to dig deeper?
IMHO it is, but I do not think that it is related to the Hue binding itself. It is more or less related to the install / uninstall process of a binding.
Uninstalled the Hue binding, cleared cache, unzipped and installed the latest test version 0.10.0 onto Milestone 6 of OpenHAB 2.4.0.
FWIW for now: Nothing happens at all. No clue or indication whatsoever of a new binding (addon) installed.
Note: I’ve got a handful of dimmer switches and 12 motion sensors (still expanding).
Sincerely thanks and appreciation for your contribution!
Sry for my stupid question: I do not quite understand if it is working now or not. Did you get your sensor running with the new binding version?
Sorry my mistake. No it is not working.
Is there a special log file or debug setting that I can turn on? I sincerely want to help out.