Plugin causes Homebridge v1.3.0 beta to crash about homebridge-bigassfans

[Supereg]

The problem is this line

homebridge-bigAssFans/index.js

Lines 180 to 184 in 4807275

	thisChar.emit('change', {
	oldValue:thisChar.value,
	newValue:getOutputMapping(newValue),
	context:null });
	}

.

A plugin MUST NOT fire the change event manually. This is NOT public API.
For such scenarios where you want to push an updated value to HomeKit, use characteristic.updateValue(...).

[jmissig]

I saw the same issue, thanks for reporting

[mlamoure]

The problem is this line

homebridge-bigAssFans/index.js

Lines 180 to 184 in 4807275

	thisChar.emit('change', {
	oldValue:thisChar.value,
	newValue:getOutputMapping(newValue),
	context:null });
	}

.
A plugin MUST NOT fire the change event manually. This is NOT public API.
For such scenarios where you want to push an updated value to HomeKit, use characteristic.updateValue(...).

Understand the plugin is calling a private event here. Is there a way to mitigate where this does not cause a crash of Homebridge, or has the private event changed since prior to 1.3 and now the crash is because it's being called incorrectly despite never being intended to being called by a plugin in the first place?

Does anyone know if this plugin is actively maintained? I see a number of outstanding PR's for the motion sensor and no recent commits.

[Supereg]

[...] has the private event changed since prior to 1.3 and now the crash is because it's being called incorrectly despite never being intended to being called by a plugin in the first place?

That is exactly what is happening. I see if I may be able to mitigate that.

EDIT: Indeed latest beta should not crash anymore, as of this.

However the plugin MUST still change that, as emitting a change event does not properly persist the value in the characteristic cache.

[mlamoure]

@Supereg confirmed beta 41 does not crash. thank you.