Closed x-dast closed 2 years ago
The services for the NEW integration have different domain, names and parameters. Please checks the doc for more info.
set_device_value
is definitly the service that should not be used.
Use climate.set_preset_mode instead with e.g. Profile 2
as preset_mode
Always prefer platform specific HA services over set_device_value
.
The "homematic.set_device_value" is automatically used by the automation. I can't change this in the visual editor.
The "homematic.set_device_value" is automatically used by the automation. I can't change this in the visual editor.
I don't think so. Please post a screenshot. Looks like you use a blueprint for the old integration, and that won't work here.
I didn't use a Blueprint, but I changed the existing automation, not created a new one. So I need to create a new automation for this to work?
Edit the existing or create a new one it's your choice, but read the docs the services are different.
I have read the docs. But does not solve my problem. With a new automation it works. Editing an existing one triggers the described problem. So now I have to recreate all heating automations. I thought it would work without having to recreate all the automations.
Sorry this is not a support forum for home assistant.
With a new automation it works
So closing this ticket, because this is not an issue with this integration.
custom_component version (if applicable): 1.28.3
known last working custom_component version (if applicable): 1.28.3
Home Assistant version (if applicable): 2022.10.5
CCU version:
Problem-relevant configuration:
Do you use tls? no Do you use callback? no Do you use username and password? yes Which interfaces do you use (hmip/bidcos/wired)? hmip
Describe the bug Since I switched to integration via HACS (Homematic(IP) Local) I get an error when changing the profile for radiator thermostat. "The automation "xyz" has an action that calls an unknown service: homematic.set_device_value."
In configuration.yaml I have removed the old integration. HA uses "homematic.", but in the documentation it says "homematicip_local.". Do I have to adjust anything else? In the developer tools "homematicip_local." is correctly available. But the automation does not seem to use that.
Screenshots (if applicable)
CCU firewall
integrations view
device view
enity view
automation view
Relevant HA log entries (full log) Logger: homeassistant.components.automation.schicht_umschalten_auf_fruhschicht Source: helpers/script.py:409 Integration: Automatisierung (documentation, issues) First occurred: 09:21:23 (1 occurrences) Last logged: 09:21:23
Schicht umschalten auf Frühschicht: Error executing script. Service not found for call_service at pos 2: Unable to find service homematic.set_device_value
Expected behavior Change settings for radiator thermostat via automations.
Additional context If I change the profile directly via the entity card, it works flawlessly.