-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive - unknown service - scene.turn.on #644
Comments
I've tried to reproduce this issue, but I'm not able to. Could you provide me the automation that causes the problems? (in YAML format). ../Frenck |
Hi Frenck
These are my automations. I cannot get my head around what should be the problem.
alias: lys_Spejlys - normal efter unavailable
description: >-
Sætter automatisk spejllyset til scene "normal" efter strømafbrydelse. Det
sikrer at lyset har en "STANDARD" indstilling at falde tilbage til, i stedet
for at hænge fast i den seneste manuelt indstillede farveindstilling.
trigger:
- platform: state
entity_id:
- light.spejllys_badevaerelset
from: unavailable
condition: []
action:
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
mode: single
alias: Lys_spisetue -lav lux - tænd hyggelys
description: ""
trigger:
- type: illuminance
platform: device
device_id: 362cdda60a305ac730ad72e7393cb713
entity_id: sensor.motion_tvstuen_illuminance_lux
domain: sensor
below: 45
condition:
- condition: and
conditions:
- condition: time
after: "12:00"
before: "21:30"
- condition: state
entity_id: input_boolean.middagslur
state: "off"
action:
- scene: scene.hyggelys_spisestue
- scene: scene.hyggelys_kokken
mode: single
alias: "Lys_Tvstue -lav lux + bevægelse - tænd hyggelys "
description: ""
trigger:
- platform: state
entity_id:
- binary_sensor.motion_tvstuen_occupancy
to: "on"
condition:
- condition: and
conditions:
- condition: numeric_state
entity_id: sensor.motion_tvstuen_illuminance_lux
below: 30
- condition: state
entity_id: light.fjer_tvstue
state: "off"
- condition: state
entity_id: light.alt_lys_i_spisestuen
state: "on"
- condition: state
entity_id: input_boolean.middagslur
state: "off"
action:
- scene: scene.hyggelys_tvstue
mode: single
alias: Lys_Stuerne - TAP - BRIGHT
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_4
discovery_id: 0x0000000000435640 action_press_4
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.rengoring
mode: single
alias: Lys_Spisestuen - TAP - Hyggelys Spisestuen
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_2
discovery_id: 0x0000000000435640 action_press_2
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.hyggelys_spisestue
mode: single
alias: Lys_TVstuen - TAP - Hyggelys TVstuen
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_3
discovery_id: 0x0000000000435640 action_press_3
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.hyggelys_tvstue
mode: single
Thank you for looking into it.
And a HUGE thanks for ALL your work with HOME ASSISTANT. I am a huge fan and a happy user of Nabu Casa – not because I need to, but because I WANT TO.
Kind regards
Christian
Fra: Franck Nijhof ***@***.***>
Sendt: 23. marts 2024 10:15
Til: frenck/spook ***@***.***>
Cc: Hoekeren ***@***.***>; Author ***@***.***>
Emne: Re: [frenck/spook] False positive - unknown service - scene.turn.on (Issue #644)
I've tried to reproduce this issue, but I'm not able to.
Could you provide me the automation that causes the problems? (in YAML format).
../Frenck
—
Reply to this email directly, view it on GitHub <#644 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH5WE2VRQAMIYW6CYUWOZRLYZVBX3AVCNFSM6AAAAABD6ME2QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGQZDCNJQHA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AH5WE2TLZBSWUUHT345CPLTYZVBX3A5CNFSM6AAAAABD6ME2QCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTYGATII.gif> Message ID: ***@***.*** ***@***.***> >
|
@Hoekeren Can you please not use email to respond to GitHub? It will mess up your responses (and thus also your automation). Instead, go to the GitHub web interface and paste your automation in a Markdown fenced codeblock so it retains formatting. ../Frenck |
alias: Lys_TVstuen - TAP - Hyggelys TVstuen
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_3
discovery_id: 0x0000000000435640 action_press_3
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.hyggelys_tvstue
mode: single
alias: Lys_Spisestuen - TAP - Hyggelys Spisestuen
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_2
discovery_id: 0x0000000000435640 action_press_2
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.hyggelys_spisestue
mode: single
alias: Lys_Stuerne - TAP - BRIGHT
description: ""
trigger:
- platform: device
domain: mqtt
device_id: 4ee1c152e824313fabb41da5936f3ac1
type: action
subtype: press_4
discovery_id: 0x0000000000435640 action_press_4
condition: []
action:
- service: scene.turn_on
data: {}
target:
entity_id: scene.rengoring
mode: single
alias: "Lys_Tvstue -lav lux + bevægelse - tænd hyggelys "
description: ""
trigger:
- platform: state
entity_id:
- binary_sensor.motion_tvstuen_occupancy
to: "on"
condition:
- condition: and
conditions:
- condition: numeric_state
entity_id: sensor.motion_tvstuen_illuminance_lux
below: 30
- condition: state
entity_id: light.fjer_tvstue
state: "off"
- condition: state
entity_id: light.alt_lys_i_spisestuen
state: "on"
- condition: state
entity_id: input_boolean.middagslur
state: "off"
action:
- scene: scene.hyggelys_tvstue
mode: single
alias: Lys_spisetue -lav lux - tænd hyggelys
description: ""
trigger:
- type: illuminance
platform: device
device_id: 362cdda60a305ac730ad72e7393cb713
entity_id: sensor.motion_tvstuen_illuminance_lux
domain: sensor
below: 45
condition:
- condition: and
conditions:
- condition: time
after: "12:00"
before: "21:30"
- condition: state
entity_id: input_boolean.middagslur
state: "off"
action:
- scene: scene.hyggelys_spisestue
- scene: scene.hyggelys_kokken
mode: single
alias: lys_Spejlys - normal efter unavailable
description: >-
Sætter automatisk spejllyset til scene "normal" efter strømafbrydelse. Det
sikrer at lyset har en "STANDARD" indstilling at falde tilbage til, i stedet
for at hænge fast i den seneste manuelt indstillede farveindstilling.
trigger:
- platform: state
entity_id:
- light.spejllys_badevaerelset
from: unavailable
condition: []
action:
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- service: scene.turn_on
metadata: {}
target:
entity_id: scene.spejllys_normal
mode: single |
I have the same problem with automations that use For me this doesn't happen every reboot, upon reboot the "missing" integration/service could be another, or there could be no necessary repairs detected... it's random.. |
Not really related to this issue. But which integration would provide that sensor? As you mention only an add-on? |
The same problem is for With
There is no integration that can be added in setting->integration, sensor is created by addon readme with explain... |
That is not how Home Assistant is supposed to work. If something needs to be integrated, an integration should be used. Otherwise, it will cause issues (not just Spook). This is not an issue on this end. That would be a: No-fix answer from this end. ../Frenck |
Ok, noted 👍🏻 For the unknown service error, do I turn on debug mode for spook and attach here the logs next time it happens? |
I also get this with a few services that exist when I check them Here's one that uses logbook.log (it's a blueprint)
Here's the blueprint config:
|
What version of Spook are you using?
2.2.2
What version of Home Assistant are you using?
2024.2.1
The problem
The automation "lys_Spejlys - normal efter unavailable" (automation.lys_spejlys_normal_efter_unavailable) has an action that calls an unknown service: scene.turn_on.
This error prevents the automation from running correctly. Maybe this service is no longer available, or perhaps a typo caused it.
To fix this error, edit the automation and remove the action that calls this service.
Click on SUBMIT below to confirm you have fixed this automation.
i am getting the false positiv on all automations containing scene.turn.on
Anything in the logs? Paste it here!
No response
The text was updated successfully, but these errors were encountered: