frontend icon indicating copy to clipboard operation
frontend copied to clipboard

Automation visual editor: Scene activation on Endpoint 0: Trigger shows 'Unknown trigger'

Open RichardHoman opened this issue 3 years ago • 0 comments

Checklist

  • [X] I have updated to the latest available Home Assistant version.
  • [X] I have cleared the cache of my browser.
  • [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

When creating a new, or editing an existing automation which uses a scene activation trigger (Scene activation on Endpoint 0) one of 2 things happen:

*) In an existing automation the trigger field shows 'Unknown trigger'. *) In a new automation there is no option available 'Scene activation on Endpoint 0'

Existing automations show valid yaml and they also still work, including the trigger which is 'unknown'. A new automation can also be created using yaml. This new automation will then work without issues.

I do only experience this with dimmer2 units by Fibaro. When trying to reproduce this with Fibaro RGBW2 modules, 'Scene activation on Endpoint 1/2/3/etc' can be selected without issue in the visual editor.

issue in visual editor valid and wotking yaml

Describe the behavior you expected

I expected the visual editor to still show the 'Scene activation on Endpoint 0' subitem and the slider to select the activation id.

Steps to reproduce the issue

  1. Use a Dimmer2
  2. Verify that 'Scene activation functionality' is enabled in the device settings
  3. Create an automation in the visual editor
  4. Select the correct device
  5. Conclude that 'Scene activation on Endpoint 0' is not available as an option

What version of Home Assistant Core has the issue?

Home Assistant 2022.9.6

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome 105.0.5195.127 (Officiële build) (64-bits)

Which operating system are you using to run this browser?

Windows 10

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

Uncaught (in promise) {code: 'invalid_format', message: "Value 106-43-0-sceneId can't be found on node Node… 'subtype': 'Endpoint 0', 'value': 14}, 'id': 32}"}

ha-automation-trigger-device.ts:17 Uncaught (in promise) 
{code: 'invalid_format', message: "Value 106-43-0-sceneId can't be found on node Node… 'subtype': 'Endpoint 0', 'value': 14}, 'id': 32}"}
value	@	ha-automation-trigger-device.ts:17
await in value (async)		
value	@	ha-automation-trigger-device.ts:17
_$AE	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
w	@	styles.ts:370
r	@	ha-automation-trigger-calendar.ts:15
E	@	typography.js:181
t	@	typography.js:181
render	@	70443fa0.js:1
update	@	70443fa0.js:1
_$AS	@	styles.ts:370
D	@	styles.ts:370
_$AI	@	styles.ts:370
m	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
m	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
S	@	styles.ts:370
update	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
w	@	styles.ts:370
r	@	ha-automation-condition-zone.ts:18
E	@	typography.js:181
t	@	typography.js:181
p	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
A	@	styles.ts:370
_$AI	@	styles.ts:370
m	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
S	@	styles.ts:370
update	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
w	@	styles.ts:370
p	@	ha-automation-trigger-row.ts:85
E	@	typography.js:181
t	@	typography.js:181
p	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
S	@	styles.ts:370
update	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
w	@	styles.ts:370
F	@	ha-automation-picker.ts:406
E	@	typography.js:181
t	@	typography.js:181
p	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
m	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
m	@	styles.ts:370
T	@	styles.ts:370
_$AI	@	styles.ts:370
S	@	styles.ts:370
update	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
set	@	styles.ts:370
value	@	ha-automation-editor.ts:83
await in value (async)		
value	@	ha-automation-editor.ts:83
_$AE	@	styles.ts:370
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
w	@	styles.ts:370
(anonymous)	@	hass-subpage.ts:18
d	@	blueprint-automation-editor.ts:25
E	@	typography.js:181
t	@	typography.js:181
value	@	hass-loading-screen.ts:11
value	@	hass-loading-screen.ts:11
value	@	hass-loading-screen.ts:11
performUpdate	@	styles.ts:370
scheduleUpdate	@	styles.ts:370
_$EC	@	styles.ts:370
await in _$EC (async)		
requestUpdate	@	styles.ts:370
o	@	styles.ts:370
b	@	styles.ts:370
r	@	hass-loading-screen.ts:11
s	@	ha-automation-picker.ts:406
E	@	typography.js:181
t	@	typography.js:181
window.CustomElementRegistry.define	@	typography.js:181
finisher	@	styles.ts:370
runClassFinishers	@	ha-automation-picker.ts:406
(anonymous)	@	ha-automation-picker.ts:406
(anonymous)	@	ha-automation-picker.ts:406
u.a	@	styles.ts:370
50148	@	ha-automation-picker.ts:406
u	@	styles.ts:370

Additional information

No response

RichardHoman avatar Sep 22 '22 21:09 RichardHoman