Alexa Skill - Dublicate Error about homebridge-yeelighter HOT 9 CLOSED

@cellcortex Is it feasible to have the second light service name ( background ) add some text to the name so that the homebridge-alexa plugin can differentiate between the two? At the present time as the names are duplicate, the second one is not passed too Alexa.

NorthernMan54/homebridge-alexa#336

from homebridge-yeelighter.

I should be able to add an option to have added to the config.

from homebridge-yeelighter.

Tks, much appreciated

from homebridge-yeelighter.

Hey @cellcortex , did you managed to fix that? Or can you point us on how to fix it manually?
Thanks in advance.

from homebridge-yeelighter.

Didn't get to it. If you want to take a shot, I'm happy to accept a PR. You would need to create 2 accessories for those lights instead of one.

from homebridge-yeelighter.

Hi, have similar issues with duplicates and the Alexa plugin.

Also, if you have 2 identical lights, in my case they are both detected as color4, they will both show in Homekit but when using the Alexa Hombridge Skill, only one light will detect, and it fails to operate due to the duplication of the detected name.

Below is what comes up in Homebridge and its passing the "Model" through to the Alexa Skill plugin, not the "Name", as I change the name, but it still detects as color4, I have also tried to change the ID but that only changes the "Serial Number"

Lightbulb
On false
Brightness 5%
Color Temperature 370
Hue 282
Saturation 100%
Manufacturer Yeelighter
Model color4
Name color4
Serial Number 0x000010101018dc9f
Firmware Revision 27
Homebridge Instance IP 127.0.0.1
Homebridge Instance Port 51100
Homebridge Instance Username 0E:69:8E:D8:4E:21
aid 12
iid 8

from homebridge-yeelighter.

@cellcortex Recently identified is that the Configured Name characteristic will receive set events when an accessory name is changed in the Home app. And if you could add the characteristic, I can read the values in the homebridge-alexa plugin.

Change is something like this

this.services[uniq_id].service.getCharacteristic(this.Characteristic.ConfiguredName)
              .on('set', setConfiguredName.bind(this.services[uniq_id]));

function setConfiguredName(this: tasmotaSwitchService | tasmotaLightService | tasmotaFanService | tasmotaSensorService | tasmotaBinarySensorService, value, callback: CharacteristicSetCallback) {
  // debug('this', this.service.displayName);
  // this.platform.log.debug('setConfiguredName', value, this.service.displayName);
  this.service.displayName = value;
  this.service.setCharacteristic(this.platform.Characteristic.Name, this.service.displayName);
  this.platform.api.updatePlatformAccessories([this.accessory]);
  callback();
}

from homebridge-yeelighter.

Would be really happy if this gets fixed because I do some dynamics brightness adjustments trough NodeRed and this currently does not work for a second device called „Ceiling Light“.
NorthernMan54/node-red-contrib-homebridge-automation#30 (comment)

from homebridge-yeelighter.

@cellcortex Tks

from homebridge-yeelighter.