nethome / nethomeserver Goto Github PK

It would be useful to have a link to the indicated (and found) home item. It is now only shown as "Existing".

Hi,

Build instructions are missing a dependency to at least to NetHome/cybergarage-upnp and /ZWave repositories.

Easy to solve if you can read mvn errors and to google, how ever instructions to build are not clear for beginners (like me).

Please update build instructions.

Hi,

I'm awaiting approval for the forum but I'll post a bug report here for now.

Environment: I'm using a Tellstick Duo on a Raspberry Pi 2. Tellstick is powered by an external USB hub with separate power. Using latest Jessie as OS for rPi and also using the nighly build of OHS.

The problem: Adding a Nexa remote power switch works fine for a while. Then it stops working. Manual remote (the one received with the power switch) works all the time, and also works fine from where the Tellstick is placed.

I removed all items and began blank. Added the remote power switch and noted that is said HouseCode O and Button 8. Tried on/off/toggle and it worked just fine. Then I restarted the daemon using sudo nethome restart command and then the switch was not working. When I looked at the settings of the lamp, it had changed to HouseCode A and Button 8. I was not able to manually save the changes to have the HouseCode set correctly.

Tried to edit the file /etc/opt/nethome/config.xml manually to set the correct values and restarted the daemon. The value is still unchanged on site, but correct in XML.

Noticed that I had Swedish characters in the names that might mess with the XML, so tried removing those. Saved and restarted. Names were updated but the site still showed incorrect HouseCode.

It is not possible to create a new home item if the item name already exists for another home item.

The problem, really, is that error messages are not propagated back to the GUI/Web on errors.

Tried with nightly build HomeManager 2.1-SNAPSHOT-0a0e5 (2016-03-06)

mvn package command will fail if executed (at least on Windows 10) on (atleast) GMT+2 timezone. Temporarily setting to GMT+1 and the build passes these tests.

Environment: Raspberry Pi

Assumptions

New installation of NetHomeServer
Bug: Previously, the /var/run/nethome directory was not created during install.

This has since been fixed

Bug

Upgrade NetHomeServer from nightly build
Bug: The /var/run/nethome directory was not checked for existence while performing an upgrade
Suggested fix is to let upgrade.sh make this check, add to line 26 onwards:

# Verify $PID_ROOT exists (a previous bug!)
if [ ! -d $PID_ROOT ]; then
  echo "Creating missing '$PID_ROOT' directory"
  mkdir -p $PID_ROOT  
fi

Explanation

The check for the running process fails and causes the upgrade to take a long time while killing and restarting the server.

I will make a pull request for this.

Hi NetHome,

I work for Philips Hue Developer Support. In case you were not aware, in a few months time we will be changing the way usernames are created on the bridge (for security reasons). Custom whitelist usernames will no longer be allowed and the bridge randomly generated username must be used instead. Please see below link for more information:
http://www.developers.meethue.com/documentation/important-whitelist-changes

I checked your code and in PhilipsHueBridge.java line 185 (RegisterUser method) you are setting the username. After February 2016 this code won't work so the passing of the user as a parameter and the setting of the "username" in the POST body should be removed here. The randomly generated bridge username is returned in the bridge success response, however it looks like you have this code in place already so hopefully the changes should be minimal for you. Apologies for the inconvenience.

Thanks
Steve