Ahh, I was under the impression that this command just enables logging for the current session, not that it changes the file. That doesn’t seem clear in the documentation.
Both my Enocean sensors are now working - the ElTako light sensor and the Trio2Sys temperature sensor. The Trio2Sys sensor was a bit fiddly because I had to get it down from an awkward spot to press the button. Thank goodness the teach-in telegram for the ElTako is activated by a magnet.
The new Enocean binding is clearly working much better now.
Incidentally, I noticed that the lux values of the ElTako are different from those in the Zipabox. Turns out the Zipabox is interpreting the values incorrectly. 
So, so far I have:
9 Somfy blinds and awnings
2 Enocean sensors
A 433Mhz temperature sensor
Sonos Connect, Boost and various Play:1s
A Brink Sky 150 ventilation unit via Modbus
The next big target is Z-Wave.
The nice thing is that, so far, I’ve been able to construct the OH system in parallel with the Zipabox. In theory, I should be able to set up the Z-Wave stick as a secondary controller and connect all the Z-Wave devices without disturbing the Zipabox, either. This means I can build my rules up until I’m ready to throw the switch.
Besides Z-Wave, the outstanding devices/services are:
- Nest thermostats & smoke detector - this is the trickiest because of Google’s evil shenanigans with the API. Right now I can access the API to obtain data, although apparently I can no longer renew the access token automatically. But so far I haven’t found a way to alter set temperatures.
- Awair air sensor - I may have to add a binding for this myself.
- Wunderground weather API for those with a personal weather station, which I (sort of) have. Well, I have a sensor or two. It’s different from the old API and (apparently?) not supported in OH.
- WeatherUnlocked weather API. Again, I might have to add a binding myself
- DarkSky weather - I can’t figure out whether this is supported or not.
- AirVisual pollution/weather - same as WeatherUnlocked
Ahh. I spy a DarkSky binding in the new OH.
Check out the Works With Nest - Deprecating on August 31, 2019 - #174 by McFly from some work-arounds that appear to work for now. Beyond that we need to wait for the Works with Google API to be released and then the individual access to that API being enabled.
I was under the impression that the binding was rewritten for the new API. @hilbrand IIRC you worked on something to get those with weather stations working with the new API. Any advice?
Don’t bother. Apple bought them out and they’ve killed support for everything including their API which will close down less than a year from now. As an aside, their little notification in the Android app telling me to “upgrade” in order to continue using DarkSky, meaning of course dropping my phone and buying an iPhone is why, at least for good while, I’ll never be responsible for sending any money Apple’s direction. I don’t care that they shut the service down, but they don’t have to flip us the bird on the way out the door.
1 Like
Grrr. Aeris weather has also gone. It used to be possible to renew the token on a monthly basis, but apparently even that’s been removed.
WeatherUnlocked is probably the best of what’s left.
Not that I know of, so can’t give any advice here. Maybe there is a PR open for other implementations, but I haven’t checked that.
1 Like
The Weather Company (formerly Wunderground) is fully supported in openHAB using the Weather Company binding, if you have an API key…
Do you mean the API for people with personal weather stations? It’s different from the old one.
I’m not sure what you are asking. The Weather Company binding requires an API key, which you cannot get unless you have a personal station and are providing data to TWC. This will not work with the old Wunderground API key.
There are two different APIs. There’s the old one, which included data like temperature and wind speed, and then new one (accessible only if you have personal weather station), which excludes this information. Yes, the API keys are different. When I looked at the Wunderground binding, it appeared to be the old API (and my PWS API key didn’t work). But that was before I upgraded OH. I’ll take a look at it again.
Looks to be the same as before. Using my API key (which I use with https://api.weather.com/v3/wx/forecast/daily/5day?format=json&units=m&apiKey=), I get “unknown” on the bridge thing.
Continuing the account of my first steps… as discussed on this thread:
I managed to get my Aeotec Gen5 Z-Stick set up as a secondary controller, by following this sequence:
- Plug Z-Stick Gen5 into any USB port
- Open Silicon Labs Z-Wave PC Controller v5.39 (getting hold of this can be a bit tricky. It’s discussed elsewhere on this forum. I can try to elaborate if anyone needs to know - if I can remember! Suffice to say that you need to register on their site.)
- Click the gear button (settings). Click the row showing the COM port, then detect, then OK
- Click network management
- Click Select learn mode and NWI (Classic may also work if the Zipabox is close)
- Go to the Zipabox and add device, Z-Wave. Zipabox says “starting exclusion…”. Don’t press anything on the Z-Stick. It will automatically be excluded.
- When Zipabox says “starting inclusion”, go back to Z-Wave PC Controller and go into learning mode again. Now the Zipabox will find the Z-Stick. At this point I got: “Device inclusion completed. Secure inclusion failed”. I didn’t worry about this because I don’t have any security-related devices. Perhaps I should worry more, but for the moment I’m happy to get this far.
- When I tried to connect the Z-Stick to the RPi, initially I got nothing because the extension cable I was using didn’t play well with the Z-Stick. When I connected it to another extension cable, the one I was using for the Enocean transceiver (both are too wide to be plugged directly into the USB sockets), I could see the device with the command: ls /dev/serial/by-id
- As described above, I think, I created a symlink so that would always get a clearly understandable symbolic name for whatever device is connected to the port in question. In my case, the vendor and device IDs are:
idProduct=“0200”
idVendor=“0658”
These can differ according to the version of the Z-Stick, I think. - That done, I added the Z-Stick manually in PaperUI. All I had to do was select the USB port (symbolic link name in this case). And 28 Z-Wave devices popped up.
Next problem: all my Fibaro FGWPE/F-102 wall plugs appear as unrecognised.
Also the Fibaro flood sensors.
The Aeotec sensors,TKB wall sockets and the SIR timer are working.
I decided to try making a binding for the Awair air quality sensor. I downloaded the addons package and found the Foobot binding, which is really similar to the Awair in every respect. I modified it for the Awair and now I need to test it. I’ve spent hours fiddling around with Eclipse and setting up the dependencies, but to no avail so far. I tried following a couple of how-tos on the OpenHab site, but also without success. I’ll carry on next week.
I eventually worked out how to set up the Eclipse environment and eliminated all the reported errors. After more than a month I’ve come back to it with the objective of generating a .jar for testing. After a couple of attempts I managed to get the jar generated by executing this command:
mvn clean install -DskipChecks
on the addon directory (org.openhab.binding.awair). Before doing that you need to clean up the code formatting with:
mvn spotless:apply
Now I have some errors to deal with from the automatic tests.
Fixed the test errors. Now I’m ready to test the addon on my system.
1 Like
Ahh, not quite. I got the 3.00 addon fixed, but not the 2.5x addon, and it’s still giving me problems with dependencies. I’ve just noticed that it’s asking for JRE 1.8, which I don’t have.