[BUG] Fix updateDimmerState() for dimmers in startup mode

[johannrichard]

Describe the bug
The following piece of code is triggered when updateDimmerState is called for dimmers when "starting up". In that case, state is null/undefined. The current if/else is a workaround that should be fixed by properly checking whether we want to update a dimmer that's in fact configured as a blind motor.

homebridge-dingz/src/dingzAccessory.ts

Lines 759 to 775 in 16c13f5

	if (state) {
	if (output && output !== 'non_dimmable') {
	newService
	.getCharacteristic(this.platform.Characteristic.Brightness)
	.updateValue(state.value);
	}
	newService
	.getCharacteristic(this.platform.Characteristic.On)
	.updateValue(state.on);
	} else {
	this.platform.log.warn(
	'We have an issue here: state should be non-empty but is undefined.',
	'Continue here, not killing myself anymore.',
	`For the records, device: ${this.device.address} - id: ${id}, index: ${index} and output is: `,
	JSON.stringify(this.dingzStates),
	);
	}

To Reproduce

• Use two dimmers as a blind
• Observe the log

Expected behavior

• No error / plugin-killig