Dan

Administrators
  • Content count

    93
  • Joined

  • Last visited

  • Days Won

    3

Dan last won the day on September 19 2016

Dan had the most liked content!

About Dan

  • Rank
    Administrator

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1393 profile views
  1. The newest version of Hobson, 0.10.0, is now publicly available. There are a lot of changes in this release including: Added "Home" and "Away" modes to the hub. Added WebSockets support so web UI updates are immediate rather than delayed by 5 seconds. Added support for long-running, complex plugin and device actions. Added ability to disable tasks. Added support for manually deleting existing devices. Created new plugin for Pushover notification service. The Hobson runtime now persists meta-data about all published devices so plugins can obtain device information even if the device hardware is unavailable (e.g. sleeping nodes). Hub authentication and authorization are now managed by an independent plugin. This allows third parties to create custom plugins to support different identity stores and authorization implementations. Added device tagging API endpoints. Simplified event subscription model for plugins. Improvements to OpenID Connect implementation. Improvements to plugin and device configuration validation. Improvements to device availability tracking and reporting. REST API documentation is now in Swagger format and can be accessed directly from the Hub.
  2. The Hobson Hub listens on port 8182 (HTTP) or 8183 (HTTPS) by default. You could run multiple hub instances and put a load balancer in front of them but that would assume that all hub instances are identical.
  3. You can launch Hobson manually using Java 1.8. The current parameters you need to pass to the "java" command are as follows: java -Dhobson.home="${launcher:sys.launcherDirectory}" -Dhobson.logdir="${launcher:sys.launcherDirectory}/logs" -Dlogback.configurationFile="${launcher:sys.launcherDirectory}/conf/logging.xml" -XX:HeapDumpPath="${launcher:sys.tempDir}" -XX:+HeapDumpOnOutOfMemoryError -Dgosh.args=--nointeractive -Djavax.net.ssl.trustStore="${launcher:sys.launcherDirectory}/conf/jssecacerts" -classpath ${launcher:sys.launcherDirectory}/lib/org.apache.felix.main-4.4.1.jar org.apache.felix.main.Main You'll need to replace ${launcher:sys.launcherDirectory} with the full path to your Hobson install directory and ${launcher:sys.tempDir} with the full path to a temporary directory (varies by OS). If you're running on Windows, you'll also need to change the '/' characters in the paths to '\'.
  4. Hobson should run just fine on Java 1.8 as is. What platform are you trying to run it on?
  5. Hi smartlake, What are you looking to do specifically? Get Hobson running on Java 1.8 or build it from source using Java 1.8?
  6. The upcoming Hobson 0.10.0 has a lot of new features including real-time web socket support, arbitrary plugin & device actions, hooks that allow users to manually add plugin devices and runtime device meta-data persistence. Undoubtedly, with a lot of changes comes a lot of testing. Since a lot of Hobson's recent changes were to support sensor use cases, it made sense to perform testing using sensor devices. The question became what kind of sensors to use? I was turned onto the MySensors project by a Hobson user and have been very impressed with it. I was able to quickly build an Arduino-based sensor gateway and a couple of basic sensors very inexpensively and quickly. Furthermore, I was able to write a MySensors serial controller plugin for Hobson quickly and painlessly which both confirmed that the MySensors ease-of-use claims were true and that the recent slew of Hobson API changes were taking things in the right direction. It's safe to say that Hobson 0.10.0 has taken longer than expected but I think the changes are excellent and will help the platform to grow. Look for it and the Hobson MySensors plugin in the coming weeks.
  7. Hi Giri, Once you pull the source from Github, you should be able to build the library JAR file by running the following command from within the project directory: mvn package This is assuming you have Maven installed and the mvn binary in your path. The JAR will be put into a directory named "target." You should then be able to include the library JAR in an Android project.
  8. Hi Ira, The Hobson server is written in Java so it should be possible to get it running on Android with some modification. I would assume the biggest change would be wrapping everything in some sort of Android service so that it started automatically and ran continuously. Since Hobson is really modular, you could exclude the web-based setup and administration applications in favor of a custom Android UI as well. Android support is not currently on the road map since there hasn't been much demand for it. I would be happy to provide input and assistance if you decide you want to attempt it.
  9. Hmm, I did test the plugin with another user's thermostat before I published the current version. Let's see if trace logging givens any indication of why the HTTP calls are failing. Stop Hobson and add the following line to line 35 of logging.xml in the Hobson install directory's "conf" directory: <logger name="com.whizzosoftware.hobson.venstar" level="TRACE" /> After the change, lines 34-36 should look like this: <logger name="com.whizzosoftware.hobson" level="ERROR" /> <logger name="com.whizzosoftware.hobson.venstar" level="TRACE" /> <logger name="ACTIVITY" level="INFO" additivity="false"> Then start Hobson up and try to control the thermostat. Post the hobson.log file here and I'll take a look.
  10. Apparently, the Venstar plugin didn't make it into the last round of updates. Thanks for pointing it out. I've published the update and you should see it now in the available plugin list using Hobson 0.9.x. You may need to restart the Hobson Hub if you don't.
  11. API

    FYI, I've just released Hobson 0.9.2 which fixes this bug.
  12. While the current focus is on the next major release of Hobson (0.10.0), users have reported a couple of bugs that were worth addressing in the short term. As such, Hobson 0.9.2 is now available. Release Notes - Hobson - Version 0.9.2 ** Bug * [HOBSON-12] - Daylight savings time can cause scheduling problems * [HOBSON-30] - Adding a device passport in the web console gives an error
  13. API

    Hi, That bug was reported and I've already fixed it. I will be releasing 0.9.2 version shortly that includes the fix. In the meantime, you can follow these simple instructions here if you'd like to fix it sooner: Yes, the intent to the device passport mechanism is to allow external hardware (like the ESP8266) to connect to Hobson. Anything that can run a TCP stack and an MQTT client should be able to leverage it. On a side note, the 0.10.0 version of Hobson that is currently in testing will do away with the device passport mechanism in favor of a more generic "add MQTT device" mechanism that will be more flexible and intuitive. Oh, and far as far as the API goes, you can use "local" as both the user ID and hub ID in all API calls. ->Dan
  14. Hi imen, Thanks for reporting the bug. I've tracked it down and fixed it but it will require a new version of the web console plugin. I'm attaching a fix here. If you want to try it out, you'll need to: Stop Hobson if it's running. Delete the file $HOBSON_INSTALL_DIR/bundle/hobson-hub-webconsole-0.9.1.jar. Copy the attached hobson-hub-webconsole-0.9.2-SNAPSHOT.jar to the $HOBSON_INSTALL_DIR/bundle directory. Delete the $HOBSON_INSTALL_DIR/data/cache directory. Start up Hobson. You should then be able to add a device passport. You may need to re-install the MQTT plugin after doing all of this as well. hobson-hub-webconsole-0.9.2-SNAPSHOT.jar
  15. I've fixed the IndexOutOfBoundsException but I believe there's still an issue. The SendData frame that the Z-Stick Gen5 sends that was causing the exception is not one I would expect to see -- I'm still not sure if it's a legitimate frame that WZWave needs to handle or if it's merely a problem of improving error handling (I currently suspect the former). Unfortunately, the Serial API (which is what we're talking about here) has still not been published by the Z-Wave folks so there's no easy place to look for this information. It has to be done the "hard way" by reverse engineering the behavior. I've purchased a Gen5 dongle so I can analyze this in more detail without having to ask you for a bunch more log files. So hopefully more updates soon.