-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Data is not pulled from Yasno correctly #31
Comments
Hey, I am aware of this issue. Yasno now returns two types of schedule on their unofficial API: regular and daily schedule.
This change shouldn't be hard to make, but I don't have much time for that. I will try my best to make necessary changes as soon as possible. |
@denysdovhan it's looks same
and
or you know other api? |
@asp24 @denysdovhan |
@Maxim-Inv in this case it will not help. Data returned inside Nobody likes to parse HTML, but I did not find any XHR request returning "right" schedule |
You should look for |
@denysdovhan Tnhx. I've missed this. Here is right filter for any who will be interested building other implementations curl https://api.yasno.com.ua/api/v1/pages/home/schedule-turn-off-electricity | jq '.components[] | select( .template_name == "electricity-outages-daily-schedule" and ( .available_regions[] | contains("kiev"))) | .dailySchedule.kiev.today.groups' |
@denysdovhan, can we expect an update to this plugin to include |
Yes, you can. I am in the process of integrating a new type of schedules. Work in progress. Can't give you any precise estimates, since I have my day-to-day job anyway. |
Hello @denysdovhan ,
First of all, thank you for this wonderful integration! However, since yesterday, I’ve noticed that the electricity outage plans have been updated on Yasno, but these updates are not reflected in your integration.
Data in HA:
![image](https://private-user-images.githubusercontent.com/116768097/387600861-923c34c2-2937-489d-b387-bfc42e4d365a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyMTgxNDUsIm5iZiI6MTczOTIxNzg0NSwicGF0aCI6Ii8xMTY3NjgwOTcvMzg3NjAwODYxLTkyM2MzNGMyLTI5MzctNDg5ZC1iMzg3LWJmYzQyZTRkMzY1YS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMFQyMDA0MDVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jM2NmZjJhMDcyMmZmZWM2N2ZiODQzYjBmZjk3OTIyOWZhNzkyMzg3ZThjOGZjMzJiZjM4NzMyNGQ1ODQ4MmY3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.NxvMLzTqGctr6HgcCAu05762RrZvVEABBLd_RsKlgY0)
Data at Yasno:
![image](https://private-user-images.githubusercontent.com/116768097/387601304-faa05db3-2d01-4135-9926-972495389c10.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyMTgxNDUsIm5iZiI6MTczOTIxNzg0NSwicGF0aCI6Ii8xMTY3NjgwOTcvMzg3NjAxMzA0LWZhYTA1ZGIzLTJkMDEtNDEzNS05OTI2LTk3MjQ5NTM4OWMxMC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMFQyMDA0MDVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zNzNiYjBjYWQ2Nzk5ZmQzMmVlZTUxM2QwOGExZTY2YzA4MjA1MTRjMTZhMTgxNjA2ODU3NGQyN2ZjMGFjNGMyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.uR7WXjhj3v0iPa7Qk0Bfea5P57oyYzP_J7z78NPZDFQ)
It seems that, for some reason, "possible outages" are still present in your integration, even though Yasno has removed them from their website.
The text was updated successfully, but these errors were encountered: