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

suez_water configuration doens't expose sub-provider option #109223

Closed
bvalat opened this issue Jan 31, 2024 · 2 comments
Closed

suez_water configuration doens't expose sub-provider option #109223

bvalat opened this issue Jan 31, 2024 · 2 comments

Comments

@bvalat
Copy link

bvalat commented Jan 31, 2024

The problem

I don't have the option to change provide option exposed by pySuez
See : ooii/pySuez#26
I can't add my seop data which are a sub provider of suez.
I tested directly with pySuez. If i don't add the -P option, it shows "Issue with yesterday data" error.
If i add the url of my sub-provider it works fine (i see data)

pysuez.exe -u user -p Password -c counter_id
Issue with yesterday data
pysuez.exe -u user -p Password -c counter_id -P https://www.seop.fr
{'attribution': 'Data provided by toutsurmoneau.fr', 'thisMonthConsumption': Data, Data...............}

Can you add the option to setup the sub provider URL?

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

suez_water

Link to integration documentation on our website

https://www.home-assistant.io/integrations/suez_water

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

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

Code owner commands

Code owners of suez_water 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 suez_water 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)


suez_water documentation
suez_water source
(message by IssueLinks)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant