search

NorthernMan54 / homebridge-alexa

Expose your homebridge controlled devices to Amazon Alexa.
https://www.homebridge.ca
455 stars 68 forks source link

Alexa can't find any devices #14

Closed ghost closed 7 years ago

ghost commented 7 years ago

Hi,

I installed your version of Homebridge on a Raspberry PI 3 model B and configured the ssdp port in the config but Alexa (Echo Dot) can't find any devices and I do have some switches etc. I enabled debug mode and got some lines with errors:

hu, 15 Jun 2017 19:48:08 GMT EventedHTTPServer [::ffff:192.168.0.247] HTTP request: /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT hue unhandled API request NaN /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT EventedHTTPServer [::ffff:192.168.0.247] HTTP Response is finished

I attached the complete log. Any idea why it's not working ?

Thx Robby homebridge.txt

NorthernMan54 commented 7 years ago

I looked at the issue, and I can see where the challenge lies. When I send the devices to Alexa I’m not picking up the name of the device

{ on: false, bri: 0, hue: 0, sat: 0, effect: 'none', ct: 0, alert: 'none', reachable: true }, type: 'Dimmable light', name: '', modelid: 'LWB004', manufacturername: 'HomeWizard', uniqueid: 'cc:22:3d:e3:ce:30:02:08-00', swversion: '66012040’ }

See name being empty in the above. I need to look into how Homewizard is handling names, and why my Alexa interface can’t see them. I may need you to run some more advanced debugging, stay tuned.

On Jun 15, 2017, at 4:19 PM, robbbyc notifications@github.com wrote:

Hi,

I installed your version of Homebridge on a Raspberry PI 3 model B and configured the ssdp port in the config but Alexa can't find any devices and I do have some switches etc. I enabled debug mode and got some lines with errors:

hu, 15 Jun 2017 19:48:08 GMT EventedHTTPServer [::ffff:192.168.0.247] HTTP request: /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT hue unhandled API request NaN /api/pkBovaHrTjmiUwGqH7m6q7eecgD3VXVrR3BPE1qK Thu, 15 Jun 2017 19:48:08 GMT EventedHTTPServer [::ffff:192.168.0.247] HTTP Response is finished

I attached the complete log. Any idea why it's not working ?

Thx Robby homebridge.txt https://github.com/NorthernMan54/homebridge-alexa/files/1078879/homebridge.txt — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/14, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmKHlBhJVwyhcJrpYrmhYV6tCRq7Dks5sEZHIgaJpZM4N7sXO.

NorthernMan54 commented 7 years ago

@robbbyc I have added more debugging, that should show where the problem lies. Please re-install and this time please use this option with DEBUG rather than the usual DEBUG=*. ( It will output less lines ). And have Alexa do a discover devices.

DEBUG=hue

ghost commented 7 years ago

I did an npm update-g https://github.com/NorthernMan54/homebridge but I don't know if this updated homebridge. If not please let me know which commands I need to run.

I ran DEBUG=hue homebridge and got the attached log file. homebridge.txt

NorthernMan54 commented 7 years ago

You ran the command correctly, but it looks like I didn't check in the new code. Let me look into it.

Sent from my iPad

On Jun 18, 2017, at 1:36 PM, robbbyc notifications@github.com wrote:

I did an npm update-g https://github.com/NorthernMan54/homebridge but I don't know if this updated homebridge. If not please let me know which commands I need to run.

I ran DEBUG=hue homebridge and got the attached log file. homebridge.txt

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

NorthernMan54 commented 7 years ago

@robbbyc I see the issue, you had used npm update rather than install. If you use npm install it should install the latest version.

Normally the npm update command would work, but I'm just doing minor tweaks and not updating the version numbers. If I had updated the version numbers npm update would have worked, but I don't want to get out of line with the homebridge version numbers.

ghost commented 7 years ago

This is the debug output with the new version. If you need any additional info just let me know. log.txt

NorthernMan54 commented 7 years ago

I made some minor tweaks around how Alexa is passed the names, please re-install and try again.

On Jun 20, 2017, at 3:57 PM, robbbyc notifications@github.com wrote:

This is the debug output with the new version. If you need any additional info just let me know. log.txt https://github.com/NorthernMan54/homebridge-alexa/files/1089520/log.txt — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/14#issuecomment-309873076, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmDpb081HAaBPQPE5gQJOADTZEh3Nks5sGCRAgaJpZM4N7sXO.

ghost commented 7 years ago

I updated and everything works fine now. Great work and thx for the great support !

NorthernMan54 commented 7 years ago

Awesome, great news. Please enjoy

On Jun 21, 2017, at 4:20 PM, robbbyc notifications@github.com wrote:

I updated and everything works fine now. Great work and thx for the great support !

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

Krocko commented 7 years ago

I have this problem too. Alexa don´t find my Dyson Fan.

DEBUG log.txt

NorthernMan54 commented 7 years ago

I was looking at the attached log, and I see multiple Dyson devices listed and passed to Alexa. Can you point out which ones are missing? And what does it show in the Alexa app for Smart Home Devices? I’m wondering if Alexa has an issue with the names or is it another issue?

On Jul 17, 2017, at 12:29 PM, Krocko notifications@github.com wrote:

I have this problem too. Alexa don´t find my Dyson Fan.

DEBUG log.txt https://github.com/NorthernMan54/homebridge-alexa/files/1153269/DEBUG.log.txt — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/14#issuecomment-315799953, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmGgdC49wkpJ3C-BWL6bhisVd6bBJks5sO4q7gaJpZM4N7sXO.

Krocko commented 7 years ago

The Dyson is only one device with multiple switches (rotation, speed, auto-mode, night mode).

At first, Alexa only found the rotation switch. After an plugin Update, Alexa only find the night mode switch from this device.

All other devices (the hue lights, the harmony scenes and the sonoff/tasmota) are found from Alexa.

NorthernMan54 commented 7 years ago

As I don't have a Dyson, I'm going to need a lot of help with mapping this to Alexa. So far I have only mapped over switches and bulbs as they directly map to the Alexa interface.

With the Alexa interface, I'm simulating a Philips Hue bulb, and can map on/off and a number aka brightness from 0 to 100. As I control the mapping, I have a lot of flexibility, but on the Alexa side it is scripted against a light bulb.

Aka

Alexa, turn on 'Dyson' Alexa, turn off 'Dyson, Alexa, turn 'Dyson' to 50

And the device names are supplied by the plugin.

From the debug log you supplied early, can you indicate what should be mapped to on/off? And a number if it makes sense.

Tks

On Jul 18, 2017, at 12:36 AM, Krocko notifications@github.com wrote:

The Dyson is only one device with multiple switches (rotation, speed, auto-mode, night mode). At first, Alexa only found the rotation switch. After an plugin Update, Alexa only find the night mode switch.

All other devices (the hue lights, the harmony scenes and the sonoff/tasmota) are found from Alexa.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

Krocko commented 7 years ago

Ok.

This should be a toggle on/off and a "brightness slider":

hue Name Dyson Pure Cool Link 00000040-0000-1000-8000-0026BB765291 +0ms\ hue device response 91 { state: \ { on: false,\ bri: 0,\ hue: 0,\ sat: 0,\ effect: 'none',\ ct: 0,\ alert: 'none',\ reachable: true },\ type: 'Dimmable light',\ name: 'Dyson Pure Cool Link',\ modelid: 'LWB004',\ manufacturername: 'Default-Manufacturer',\ uniqueid: 'cc:22:3d:e3:ce:30:91:18-00',\ swversion: '66012040' } +0ms\

This should be a toggle on/off:

hue Name Auto - Dyson Pure Cool Link 00000049-0000-1000-8000-0026BB765291 +1ms\ hue device response 91 { state: \ { on: false,\ bri: 0,\ hue: 0,\ sat: 0,\ effect: 'none',\ ct: 0,\ alert: 'none',\ reachable: true },\ type: 'Dimmable light',\ name: 'Auto - Dyson Pure Cool Link',\ modelid: 'LWB004',\ manufacturername: 'Default-Manufacturer',\ uniqueid: 'cc:22:3d:e3:ce:30:91:22-00',\ swversion: '66012040' } +0ms\

This should be a toggle on/off:

hue Name Rotation - Dyson Pure Cool Link 00000049-0000-1000-8000-0026BB765291 +6ms\ hue device response 91 { state: \ { on: false,\ bri: 0,\ hue: 0,\ sat: 0,\ effect: 'none',\ ct: 0,\ alert: 'none',\ reachable: true },\ type: 'Dimmable light',\ name: 'Rotation - Dyson Pure Cool Link',\ modelid: 'LWB004',\ manufacturername: 'Default-Manufacturer',\ uniqueid: 'cc:22:3d:e3:ce:30:91:25-00',\ swversion: '66012040' } +0ms\

This should be a toggle on/off:

hue Name Night Mode - Dyson Pure Cool Link 00000049-0000-1000-8000-0026BB765291 +1ms\ hue device response 91 { state: \ { on: false,\ bri: 0,\ hue: 0,\ sat: 0,\ effect: 'none',\ ct: 0,\ alert: 'none',\ reachable: true },\ type: 'Dimmable light',\ name: 'Night Mode - Dyson Pure Cool Link',\ modelid: 'LWB004',\ manufacturername: 'Default-Manufacturer',\ uniqueid: 'cc:22:3d:e3:ce:30:91:28-00',\ swversion: '66012040' } +1ms\

Krocko commented 7 years ago

Hello. Have you any news for me? Or need you more info?

NorthernMan54 commented 7 years ago

Right now I'm trying to figure out why this device doesn't work. If you look in the Alexa app, does the dyson show up. Can you share a screenshot? My current thought is that Alexa doesn't like the names.

Sent from my iPad

On Jul 21, 2017, at 2:45 PM, Krocko notifications@github.com wrote:

Hello. Have you any info for me? Or need you more info?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

Krocko commented 7 years ago

I had renamed the device to Fan temporary, but with the same result.

img_0080

NorthernMan54 commented 7 years ago

After looking at a couple of different things, I'm thinking it might be the device unique ID not being unique enough when it is a Dyson, so I changed the unique ID slightly. Let's see how with goes. Please re-install and try again

Krocko commented 7 years ago

Thanks for your work. But it is the same like before. Only the Night Mode switch is visible.

NorthernMan54 commented 7 years ago

I should have asked this before, which plugin are you using? I presume it is this one? homebridge-dyson-link

To diagnose this further, I'm going to need to create an emulator for the dyson, so I can troubleshoot from my without a lot more trial and error. I'm going to need a few days, so give my until early next week.

Krocko commented 7 years ago

Yes. It is homebridge-dyson-link.

NorthernMan54 commented 7 years ago

Okay, I have found the issue and it should now be working. I also added rotation speed control to the “Fan”. I named mine “Dyson”, and tested the following alexa commands

Alexa, turn on dyson Alexa, turn off dyson Alexa, turn dyson to 50

Even though I don’t have the dyson they appeared to work ;-)

Also, I hope I haven’t broken anything else with this change, fingers crossed.

On Jul 26, 2017, at 12:00 AM, Krocko notifications@github.com wrote:

Yes. It is homebridge-dyson-link.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/14#issuecomment-317940931, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmO_aM6CPaXqs2ABFQVI6l09dxovKks5sRrnIgaJpZM4N7sXO.

Krocko commented 7 years ago

I have tested this.
The Rotation switch only toggles the Rotation. The normal fan switch is missing. I can't turn on the fan. Also Alexa don't find my other devices anymore.

NorthernMan54 commented 7 years ago

Could you send another debug log again, I added more logging of the homebridge and Alexa communications. Tks

On Jul 28, 2017, at 12:03 AM, Krocko notifications@github.com wrote:

I have tested this. The Rotation switch only toggles the Rotation. The normal fan switch is missing. I can't turn on the fan. Also Alexa don't find my other devices anymore.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

Krocko commented 7 years ago

Here it is Homebridge DEBUG log.txt

NorthernMan54 commented 7 years ago

Tks that log helped a lot, please try again.

On Jul 28, 2017, at 4:30 PM, Krocko notifications@github.com wrote:

Here it is Homebridge DEBUG log.txt https://github.com/NorthernMan54/homebridge-alexa/files/1184182/Homebridge.DEBUG.log.txt — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/14#issuecomment-318754727, or mute the thread https://github.com/notifications/unsubscribe-auth/AS5CmBGYlvIq0umFB-ENvTQ7JGvhVG-cks5sSkTtgaJpZM4N7sXO.

Krocko commented 7 years ago

Works now. Thank you for your effort.

Krocko commented 7 years ago

@northernman54 is it possible to hide some devices? Some lights from the original Hue bridge don't work anymore with Alexa if this devices come from Homebridge too.

NorthernMan54 commented 7 years ago

In my setup, I'm running 2 instances of Alexa, one connected to Alexa and one not just for this reason. And in the one not connected to Alexa is where I have the hue plugin running.

In the config, I included the setting as do which enables or disables the Alexa feature. Which enables one installation of Homebridge to be used with multiple instances, and allow the config of each instance to enable or not enable Alexa support as desired.

On Aug 16, 2017, at 3:27 PM, Krocko notifications@github.com wrote:

@NorthernMan54 is it possible to hide some devices? Some lights from the original Hue bridge don't work anymore with Alexa if this devices come from Homebridge too.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

NorthernMan54 commented 7 years ago

I love auto correct

In the second paragraph, the setting ssdp which enables

On Aug 16, 2017, at 4:12 PM, SEAN GRACEY seangracey@yahoo.ca wrote:

In my setup, I'm running 2 instances of Alexa, one connected to Alexa and one not just for this reason. And in the one not connected to Alexa is where I have the hue plugin running.

In the config, I included the setting as do which enables or disables the Alexa feature. Which enables one installation of Homebridge to be used with multiple instances, and allow the config of each instance to enable or not enable Alexa support as desired.

On Aug 16, 2017, at 3:27 PM, Krocko notifications@github.com wrote:

@NorthernMan54 is it possible to hide some devices? Some lights from the original Hue bridge don't work anymore with Alexa if this devices come from Homebridge too.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Krocko commented 7 years ago

Is there a Tutorial to install a second homebridge with different Plugins?

NorthernMan54 commented 7 years ago

I'm not aware of one, but I haven't looked lately. For me, I used the -U homebridge command line option to specify a seperate config directory that holds the config.json for the second instance.

ghost commented 7 years ago

I am having trouble with this too. However, I am not sure if this will work in my case.. which is:

All of my devices (except Nest, which Alexa can already control) are homekit compatible only. My goal is to expose a dummy switch(https://www.npmjs.com/package/homebridge-statefuldummy) that I can then pair with an actual device within homekit. Thus allowing Alexa to control homekit only devices.

Is this possible? Thanks

NorthernMan54 commented 7 years ago

As your going down a new path with that approach, all I can say is give it a try and see what happens. I know that the stateful dummy switch works with with Alexa, so your half way there.

Sent from my iPad

On Oct 15, 2017, at 11:40 PM, brentleeper notifications@github.com wrote:

I am having trouble with this too. However, I am not sure if this will work in my case.. which is:

All of my devices (except Nest, which Alexa can already control) are homekit compatible only. My goal is to expose a dummy switch(https://www.npmjs.com/package/homebridge-statefuldummy) that I can then pair with an actual device within homekit. Thus allowing Alexa to control homekit only devices.

Is this possible? Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.