-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Homewizard first Version stopped working after Update #118105
Comments
Hey there @DCSBL, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) homewizard documentation |
@home-assistant rename Homewizard first Version stopped working after Update |
I think it is better to ask about this issue on Discord or the Home Assistant forum, as your issue is about the (12 year old) HomeWizard hub, not "HomeWizard Energy". I do not think your issues is caused by the update, as it simply used Maybe you can ask about your situation here: https://community.home-assistant.io/t/homewizard-intergration/7757 |
@home-assistant unassign homewizard |
The problem
After Update Homeassistant Core from 2023.11.3 to another Version, Homewizzard stopped to work.
This is an working example:
vswitch1:
command_on: curl "http://192.168.248.25:80/PW/sw/dim/1/8"
command_off: curl "http://192.168.248.25:80/PW/sw/1/off"
command_state: curl "http://192.168.248.25:80/PW/get-status"
value_template: '{{ value_json.response.switches[1].status=="on" }}'
friendly_name: Carport
What can i do?
What version of Home Assistant Core has the issue?
any newer version after 2023.11.3
What was the last working version of Home Assistant Core?
2023.11.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Homewizzard
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: