Devices Not loading #21
Comments
|
Can you share your config.json/screenshot it what comes up in the config GUI? You may have it set to hide devices by default.
…Sent from my iPhone
On May 27, 2020, at 4:35 AM, dmxwidget ***@***.***> wrote:
Homebridge: Version 1.1.1-beta.3
homebridge-isy v0.5.0-rc7
homebridge-config-ui-x v4.20.0
I've been fighting with this for a couple days now...I was able to get the Home app to connect to homebridge and then once I added the isy plugin, it would fail to connect/not display devices. BUT I was able to see my lights and such in the Homebridge UI.
Today, I started over with a fresh config. Added Homebridge to my home. I was able to see it. Then, I added a Dummy Switch, and that appears fine. I add the ISY plugin, but I am not able to see any of my Isy devices. The dummy switch keeps working just fine.
Any thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
|
|
Can you try reverting to homebridge 1.1.0? I’m not sure without the issue is with the beta version this point, but it appears to be a problem.
… On May 27, 2020, at 12:46 PM, dmxwidget ***@***.***> wrote:
<https://user-images.githubusercontent.com/66004653/83048676-97cd7700-a00f-11ea-9cf6-cff55b6f652c.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5XAFLQKAUH5Z5XBLVDFEDRTU7UVANCNFSM4NL5FY3Q>.
|
|
Updated. No change on my end...Same issues. |
|
What does it show in your log? Also perhaps you can share your cachedAccessories.json file from homebridge?
…Sent from my iPhone
On May 27, 2020, at 1:29 PM, dmxwidget ***@***.***> wrote:
Updated. No change on my end...Same issues.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Let me know if this works? |
|
I'm having the same issue. I can see all of the device messages in my UX but no accessories. |
|
Okay - thanks - that’s very helpful. Can you share your ISYNodesDump.json?
… On May 28, 2020, at 10:40 AM, Joe Rork ***@***.***> wrote:
I'm having the same issue. I can see all of the device messages in my UX but no accessories. [5/28/2020, 10:21:08 AM] [isy-nodejs] Error initializing ISY: {} [5/28/2020, 10:21:08 AM] [isy-nodejs] Connecting to: ws://192.168.1.21/rest/subscribe <ws://192.168.1.21/rest/subscribe> [5/28/2020, 10:21:08 AM] [ISY] Accessories to configure: 0 [5/28/2020, 10:21:08 AM] [ISY] ISY has 81 devices and 28 scenes [5/28/2020, 10:21:08 AM] [ISY] Device Kitchen-Familyroom-Dining undefined is not supported yet. [5/28/2020, 10:21:08 AM] [ISY] Device Kitchen-Familyroom-Dining undefined is not supported yet. [5/28/2020, 10:21:08 AM] [ISY] Device Kitchen-Familyroom-Dining undefined is not supported yet.
|
|
Please see the github invite I just sent to you |
|
Here's mine as well |
|
@pradeepmouli Any update on this? |
|
I’m having the same problem and have been trying to figure out what my problem is all week. The older version homebridge-isy-js identifies my zwave devices fine but the homebridge isy only identifies my scenes and one moisture sensor. I’m attaching screen shot of where the error begins. Any help would be much appreciated. |
|
I had the same issue and after a quick look at the code, I discovered that port 80/443 are essentially hardcoded. I was running my ISY on a non-standard port and getting this error. This plugin needs to add a port field to the config (which the old version allowed for and that's why it worked) but in the meantime, make sure you're running on port 80. If I get some free time, I'll put a PR together if @pradeepmouli wants. Similarly, if you're running on port 443 and you don't have a valid cert (or you're using the one installed on the ISY), then you're also kind of screwed as there is no rejectUnauthorized option in the config either. That's probably more of an edge case though. EDIT: Here's the configuration area I'm talking about (http/https port)...
|
|
Thanks - I should have caught that - PR would be appreciated.
…Sent from my iPhone
On Sep 16, 2020, at 10:46 AM, Chad Hobson ***@***.***> wrote:
@dmxwidget @Mandaur1
I had the same issue and after a quick look at the code, I discovered that port 80/443 are essentially hardcoded. I was running my ISY on a non-standard port and getting this error.
This plugin needs to add a port field to the config (which the old version allowed for and that's why it worked) but in the meantime, make sure you're running on port 80. If I get some free time, I'll put a PR together if @pradeepmouli wants.
Similarly, if you're running on port 443 and you don't have a valid cert (or you're using the one installed on the ISY), then you're also kind of screwed as there is no rejectUnauthorized option in the config either. That's probably more of an edge case though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
actually, as a work around, you should be able to include the port number in the address e.g. 192.168.1.190:xxx your config file. |
|
also, @Mandaur1 - for your issue, it looks like the problem is that you have no variables defined - also a bug which I need to remedy, but if you add at least 1 variable of each type to your isy, the issue should go away. |
|
Thank you very much to both of you! The error was resolved by adding variables of each type to my isy. So now I can see every device in the log. Almost all of my devices are Z-wave. They just don't want to cooperate showing up in my accessories tab. Log says they are unsupported. I have tried all sorts of combinations in the config file. the only accessories that will show up are my scenes that are tied to my Z-wave switches and they work. What am I doing wrong. If I use the unsupported version of homebridge-isy-js, they do show up in my accessories tab. I am using 192.168.1.45:80. |
|
Haven’t added back support yet - I would suggest having the z-wave devices run off the old plugin (ignore everything based on name etc.) , and the other devices run off this one (ignore everything where family
= zwave). You’ll be able to configure things this way because the plugins do have different names (homebridge-Isy-js vs. homebridge-isy).
…Sent from my iPhone
On Sep 16, 2020, at 10:48 PM, Mandaur1 ***@***.***> wrote:
Thank you very much to both of you! The error was resolved by adding variables of each type to my isy. So now I can see every device in the log. Almost all of my devices are Z-wave. They just don't want to cooperate showing up in my accessories tab. Log says they are unsupported. I have tried all sorts of combinations in the config file. the only accessories that will show up are my scenes that are tied to my Z-wave switches and they work. What am I doing wrong. If I use the unsupported version of homebridge-isy-js, they do show up in my accessories tab. I am using 192.168.1.45:80.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I’ll just configure the Homebridge the way you suggested. Thank you very much. |
|
I am still struggling to see anything in my devices tab. I have a default config and the device traffic shows up in the logs. I have had random moments of time here and there for months and I keep thinking there is a setting or a step that I'm missing but I find none. The only other plug-in was for cameras and that works great. |
Homebridge: Version 1.1.1-beta.3
homebridge-isy v0.5.0-rc7
homebridge-config-ui-x v4.20.0
I've been fighting with this for a couple days now...I was able to get the Home app to connect to homebridge and then once I added the isy plugin, it would fail to connect/not display devices. BUT I was able to see my lights and such in the Homebridge UI.
Today, I started over with a fresh config. Added Homebridge to my home. I was able to see it. Then, I added a Dummy Switch, and that appears fine. I add the ISY plugin, but I am not able to see any of my Isy devices. The dummy switch keeps working just fine.
Any thoughts?
The text was updated successfully, but these errors were encountered: