homebridge-smartthings 0.4.0+ Other npms versions Status about homebridge-smartthings HOT 27 CLOSED

Status: WORKING. Remote Homekit via iCloud/AppleTV: WORKING. Return from remote: WORKING.
node -v - v5.7.0
npm view homebridge version - 0.2.19
npm view hap-nodejs version - 0.2.5
npm view homebridge-smartthings version - 0.4.3

Mac OS 10.10

Note: I could not get remote homekit to work OR it to work when coming back from the network on Ubuntu. I am running flawlessly off the Mac.

Note 2: All of my random frustrating issues must have been my Airport Extreme. Was having wireless printer weirdness, rebooted the Airport, and all of a sudden it fixed my Homebridge stuff.

from homebridge-smartthings.

Status: Working for past 3 days with no timing tweaks. Today I just got a bunch of errors, although things still seem to be working. At first I was confused at all the random IP addresses (107.20.201.51, 54.243.74.147, 174.129.9.165), but then I realized that they are the IP addresses for the SmartThings website. Errors can be seen here: Errors.txt

"node -v" - v4.2.4
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5
"npm view homebridge-smartthings version" - 0.4.3

Running on Raspberry Pi 2 with latest Raspian OS.

from homebridge-smartthings.

@coolcom are you using the iOS 9.3 Beta i think there is a know issue

from homebridge-smartthings.

I finally have a working setup, sorry for the messages and then deletions, etc. I updated my original comment. Good work @pdlove.

from homebridge-smartthings.

Just crashed today after 10 days would not start back up but then it did and crashed

node -v 4.1.1
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5
"npm view homebridge-smartthings version" - 0.4.3

Running on Raspberry Pi 2 with latest Raspian OS.

from homebridge-smartthings.

"node -v" - v4.2.2
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5
"npm view homebridge-smartthings version" - 0.4.3

Raspberry PI B latest Raspbian

Status: seems to be working, but I see my log early this morning was flooded with this:
Feb 25 03:22:27 raspberrypi homebridge[23338]: error at req: { [Error: getaddrinfo ENOTFOUND graph.api.smartthings.com graph.api.smartthings.com:443] Feb 25 03:22:27 raspberrypi homebridge[23338]: code: 'ENOTFOUND', Feb 25 03:22:27 raspberrypi homebridge[23338]: errno: 'ENOTFOUND', Feb 25 03:22:27 raspberrypi homebridge[23338]: syscall: 'getaddrinfo', Feb 25 03:22:27 raspberrypi homebridge[23338]: hostname: 'graph.api.smartthings.com', Feb 25 03:22:27 raspberrypi homebridge[23338]: host: 'graph.api.smartthings.com', Feb 25 03:22:27 raspberrypi homebridge[23338]: port: '443' }

which eventually ended with this:
Feb 25 04:13:24 raspberrypi homebridge[23338]: error at req: { [Error: connect EHOSTUNREACH 174.129.9.165:443] Feb 25 04:13:24 raspberrypi homebridge[23338]: code: 'EHOSTUNREACH', Feb 25 04:13:24 raspberrypi homebridge[23338]: errno: 'EHOSTUNREACH', Feb 25 04:13:24 raspberrypi homebridge[23338]: syscall: 'connect', Feb 25 04:13:24 raspberrypi homebridge[23338]: address: '174.129.9.165', Feb 25 04:13:24 raspberrypi homebridge[23338]: port: 443 }

and then nine hours later, Homebridge crashed and restarted after this:
Feb 25 17:05:18 raspberrypi homebridge[23338]: /usr/local/lib/node_modules/homebridge-smartthings/index.js:76 Feb 25 17:05:18 raspberrypi homebridge[23338]: } else if (myList.error) { Feb 25 17:05:19 raspberrypi homebridge[23338]: ^ Feb 25 17:05:19 raspberrypi homebridge[23338]: TypeError: Cannot read property 'error' of undefined Feb 25 17:05:19 raspberrypi homebridge[23338]: at /usr/local/lib/node_modules/homebridge-smartthings/index.js:76:30 Feb 25 17:05:19 raspberrypi homebridge[23338]: at /usr/local/lib/node_modules/homebridge-smartthings/lib/smartthingsapi.js:93:13 Feb 25 17:05:19 raspberrypi homebridge[23338]: at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-smartthings/lib/smartthingsapi.js:46:27) Feb 25 17:05:19 raspberrypi homebridge[23338]: at emitNone (events.js:72:20) Feb 25 17:05:19 raspberrypi homebridge[23338]: at IncomingMessage.emit (events.js:166:7) Feb 25 17:05:19 raspberrypi homebridge[23338]: at endReadableNT (_stream_readable.js:905:12) Feb 25 17:05:19 raspberrypi homebridge[23338]: at doNTCallback2 (node.js:441:9) Feb 25 17:05:19 raspberrypi homebridge[23338]: at process._tickCallback (node.js:355:17) Feb 25 17:05:19 raspberrypi systemd[1]: homebridge.service: main process exited, code=exited, status=1/FAILURE Feb 25 17:05:19 raspberrypi systemd[1]: Unit homebridge.service entered failed state.

It restarted with no errors and claims to be running fine, but it not reachable in HomeKit apps. May be due to problems with OpenHab, will troubleshoot more after I get kids in bed

from homebridge-smartthings.

I got homebridge to complete startup by disabling a component of openhab that seemed to be stalling that service, but the HomeKit apps claimed nothing is connected, while the log showed requests for updates of components getting through. Deleting and re-adding the homebridge accessory worked, without any of the more extreme measures (delete persist, flush HomeKit config, etc)

from homebridge-smartthings.

"node -v" - v5.6.0
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5
"npm view homebridge-smartthings version" - 0.4.3

Running in a FreeNAS jail (FreeBSD 9.3), but I originally tried it under Ubuntu 14.04 with the same results as below...

Can add Homebridge and see devices, but a couple show as missing after about 15 minutes, and slowly over time things get worse until nothing responds. I can nuke the persist folder contents, reset HomeKit, and re-add Homebridge and the cycle repeats. I just picked up an ATV3 to try to get remote access to work, but if it's pooping the bed while I'm still at home remote access is moot.

from homebridge-smartthings.

@axemann FWIW, I had zero success with Ubuntu (it was running in a VM). Both 14.04 and 15.10. You would not believe how many different versions of node I tried. I installed it on my Mac, and has been rock solid since. ATV3 remote access works perfectly.

from homebridge-smartthings.

@coolcom I may have to give that a shot if I can ever get OSX running on my ESXi box...

from homebridge-smartthings.

I have it running flawlessly on my raspberry pic under raspbian. I'll install the latest Ubuntu so I can get the problems y'all have.

from homebridge-smartthings.

Mine was running great on my RPi2 (Raspbian) for several days, then konked out yesterday. Not sure if it had something to do with the SmartThings outage or not. A restart didn't work to fix it. I had to remove the persist folder, etc., and re-add Homebridge from scratch...

from homebridge-smartthings.

Everything seems fine this morning, not sure what yesterday's issues were, I'll see how it goes today. My weekend project is to update to OpenHab 2, and if that works I may move that to its internal HomeKit code instead of homebridge, simplifying the issues for the smartthings plugin.

from homebridge-smartthings.

Got home tonight and Homebridge is down, last thing in the log is 7 hours ago:

Feb 26 12:50:30 raspberrypi homebridge[378]: error at req: { [Error: connect ETIMEDOUT 174.129.9.165:443] Feb 26 12:50:30 raspberrypi homebridge[378]: code: 'ETIMEDOUT', Feb 26 12:50:30 raspberrypi homebridge[378]: errno: 'ETIMEDOUT', Feb 26 12:50:30 raspberrypi homebridge[378]: syscall: 'connect', Feb 26 12:50:30 raspberrypi homebridge[378]: address: '174.129.9.165', Feb 26 12:50:30 raspberrypi homebridge[378]: port: 443 }

Restarting Homebridge fixed it, for now.
Given the Amazon AWS IP address, I'm guessing it's related to SmartThings's platform issues, though they claim everything's back to green at status.smartthings.com

What's mainly annoying is that homebridge didn't know it had failed, so systemd didn't restart it.

from homebridge-smartthings.

I had below versions and after upgrading to 0.4.1\0.4.3 I see the devices keep going unreachable and tried and tried and gave up and using 0.3.5 with no issues.
"node -v" - v5.6.0
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5

After seeing that latest version working fine for few of you with node version 4.2.1/4.2.4 I have downgraded node to 4.2.4 and reinstalled Homebridge and homebridge-smartthings again and tried with two different iPhones (9.2.1) it was working fine for some time and then going unreachable, tried many times each time I am changing the homebridge name and deleting the persist folder and re-adding the homebridge and the same issue again and again.

so going back to 0.3.5 for now as that works for me.

from homebridge-smartthings.

@KumarMudedla and all: I just wanted to confirm that I reverted to version 0.3.5 of the plugin and everything seems stable except for device updates, which seem to work at random (at this point).

from homebridge-smartthings.

Status: NOT Working (Works for a few hours but then I loose all devices requires restart of services to bring all devices back)
OS X El Capitan (10.11.3)
"node -v" - v4.2.1
"npm view homebridge version" - 0.2.19
"npm view hap-nodejs version" - 0.2.5
"npm view homebridge-smartthings version" - 0.4.3

HomeKit Device iPhone 6s
iOS 9.3 Beta

from homebridge-smartthings.

Update for me:
It works great for 2 days, but then stops working. If I stop and start homebridge, I get duplicate entries of all my devices in Homekit. So I remove persist, change the name, and re-add. It works for a couple days again.

Where are the log files located that I could perhaps take a look at? I'm on OS X.

from homebridge-smartthings.

This is the last error I see in my error logs:
Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 381dd3b1-eb0c-438f-8fd9-aa0d239e6fbd
at Bridge.Accessory.addBridgedAccessory (/Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/A$
at Server. (/Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge/lib/server.js:231:24)
at /Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at /Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge-smartthings/index.js:104:4
at /Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge-smartthings/index.js:81:5
at /Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge-smartthings/lib/smartthingsapi.js:93:13
at IncomingMessage. (/Users/huynguyen/.nvm/versions/node/v4.2.1/lib/node_modules/homebridge-smartthings/lib/smartthingsapi.js:46:2$
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:903:12)
events.js:141
throw er; // Unhandled 'error' event
^

Error: read ETIMEDOUT
at exports._errnoException (util.js:874:11)
at TCP.onread (net.js:544:26)
events.js:141

Now I have homebridge running as a launchDaemon and it's set to reload if it crashes, maybe when it tries to reload it's causing problems which is why I see this error. @coolcom since i'm using a launchDaemon i tell it where to output the errors, not sure where it goes by default. Before I was using @pdlove plugin and I was using the legacy plugin this was the method I used to keep the service alive and worked well for me for a few weeks on end. But maybe with this version I need to find a different way to relaunch the services when it does crash, or figure out why it's crashing in the first place. I'm going to disable options for the launchDaemon to restart and see what errors I get from there.

from homebridge-smartthings.

Note: I am not using launchDaemon and haven't really needed as I don't have any issues with it crashing and stopping. I just have issues with the Homekit not recognizing/reaching any of my devices.

from homebridge-smartthings.

Status: NOT working. Works for a little while after removing persist directory and restarting homebridge, removing home from HomeKit app and re-adding Homebridge accessory. After ~1hr, homebridge and all subordinate accessories go poof (i.e., no longer appear in any HomeKit app).

Things that do not work to recover:

• Restarting homebridge
• reboot rpi
• remove persist directory & restart homebridge
• remove persist directory & reboot rpi
• change bridge username in config.json & restart homebridge
• change bridge username in config.json & reboot pi

To get my homebridge devices back, I do ALL of the following:

• restart router (Apple Time Capsule ~2012)
• stop homebridge
• remove persist
• change bridge username in config.json
• start homebridge
• re-add homebridge accessory to HomeKit
• re-populate rooms with "new" homebridge devices

rpi 2 model B
Ubuntu 15.10 (GNU/Linux 4.1.15-v7+ armv7l) (Ubuntu MATE 15.10)
"node -v" - v5.7.0
"npm view homebridge version" - 0.3.0
"npm view hap-nodejs version" - 0.2.6
"npm view homebridge-smartthings version" - 0.4.3
"npm view homebridge-liftmaster version" - 0.1.2
"npm view homebridge-harmonyhub version" - 0.1.1
"avahi-daemon --version" - 0.6.31

HomeKit device iPhone 6 plus
iOS version 9.2.1

Note, homebridge-smartthings is not my only home bridge plugin, and ALL my accessories under homebridge are affected, not just the home bridge-smartthings ones. Therefore, is this (well, my variant, at least) a homebridge-smartthings issue, or really a homebridge issue?

I've gotten my devices added back again, and I'll check the log for errors if/when my homebridge setup flatlines again.

from homebridge-smartthings.

I still think this is insane because I've been running fine for 2 weeks now without restarting.
I'll be updating tonight with much better error trapping.

from homebridge-smartthings.

It's more insane than you might imagine.

When I'm running homebridge, I've noticed that my wireless network gets flattened periodically, requiring a restart of my router (Apple Time Capsule from 2012 or so). Then my Apple devices start "counting" - adding a serial number after the device name.

I've seen this same behavior with OS X Yosemite when Apple had switched out mdnsresponder for disvoveryd to handle Bonjour. As of OS X 10.10.4, Apple switched back to mdnsresponder.

I suspect that avahi is the culprit here, causing this situation to reappear, however homebridge isn't able to "count up" a new device name after the network is restarted. This would explain why those running homebridge on OS X don't see the problem.

Since you don't see this problem on raspbian, I'm curious what our respective versions of avahi-daemon are. I'm not at home to check right this moment, but I'll report what I find. If there's no version difference, maybe a config difference?

Worst case, I rebuild my pi with raspbian.

(update: I added avahi version to my previous comment)

Kevin Shuk
[email protected]

On Mar 6, 2016, at 8:49 AM, pdlove [email protected] wrote:

I still think this is insane because I've been running fine for 2 weeks now without restarting.
I'll be updating tonight with much better error trapping.

—
Reply to this email directly or view it on GitHub.

from homebridge-smartthings.

I'm running on OS X and it's not stable at all. All my devices from the plugin disappear after a couple hours or less. My homebridge-netatmo plugin seems fine tho and I can see those devices still. When the failure occurs it's seems my smartthings plugin and HarmonyHub plugin seem to cause those devices to disappear. If i restart homebridge everything works again...

from homebridge-smartthings.

Correction even my netatmo devices fail but they stay in HomeKit they just don't respond. Smarttings and HarmonyHub devices disappear completely. Until I restart

from homebridge-smartthings.

I'm on OS X, it runs flawless for ~36 hours, and then all the devices disappear from Homekit. There are only a few timeout errors, and those timestamps (installed homebridge--log via npm for timestamps) indicate that after the error occurred, I was able to verify everything working. It has since stopped working (all disappeared), and there have been no timedout or other errors after the previous mentioned.

That might be confusing...

Last error I see was yesterday afternoon. Yesterday evening it was working fine (AFTER the timeout). This morning, all devices are gone and not working.

from homebridge-smartthings.

I'm moving all discussion to issue #58. I was able to iron out one major issue last night an just released that as 0.4.6.

from homebridge-smartthings.