Skip to content
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

Open
km110461 opened this issue May 25, 2024 · 4 comments
Open

Homewizard first Version stopped working after Update #118105

km110461 opened this issue May 25, 2024 · 4 comments

Comments

@km110461
Copy link

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

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

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @DCSBL, mind taking a look at this issue as it has been labeled with an integration (homewizard) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homewizard can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign homewizard Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


homewizard documentation
homewizard source
(message by IssueLinks)

@DCSBL
Copy link
Contributor

DCSBL commented May 26, 2024

@home-assistant rename Homewizard first Version stopped working after Update

@home-assistant home-assistant bot changed the title Homewizzard first Version stopped working after Update Homewizard first Version stopped working after Update May 26, 2024
@DCSBL
Copy link
Contributor

DCSBL commented May 27, 2024

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 curl (in combination with Command line?). It is very unlikely that that stopped working.

Maybe you can ask about your situation here: https://community.home-assistant.io/t/homewizard-intergration/7757

@DCSBL
Copy link
Contributor

DCSBL commented May 27, 2024

@home-assistant unassign homewizard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants