Closed Andes1984 closed 4 months ago
WOLF Smartset dev team here. We have the instruction of not working for unofficial products, but we wanted to let you know the following. Due to extreme high amounts of login requests we had to take action and disable today your currently used method. If you try again please use the OAuth flow and reuse your tokens like the official products.
WOLF Smartset dev team here. We have the instruction of not working for unofficial products, but we wanted to let you know the following. Due to extreme high amounts of login requests we had to take action and disable today your currently used method. If you try again please use the OAuth flow and reuse your tokens like the official product
WOLF Smartset dev team here. We have the instruction of not working for unofficial products, but we wanted to let you know the following. Due to extreme high amounts of login requests we had to take action and disable today your currently used method. If you try again please use the OAuth flow and reuse your tokens like the official products.
Can someone tell me what this means? Which token?
WOLF Smartset dev team here. We have the instruction of not working for unofficial products, but we wanted to let you know the following. Due to extreme high amounts of login requests we had to take action and disable today your currently used method. If you try again please use the OAuth flow and reuse your tokens like the official products.
Ping @adamkrol93
Wer kennt sich mit sowas aus? Ein wenig Hilfe von Wolf dev team würde warscheinlich helfen.
Wer kennt sich mit sowas aus? Ein wenig Hilfe von Wolf dev team würde warscheinlich helfen.
The most important information was given from the wolf dev team (@WOLF-Smartset, thanks for joining the discussion and give us the insights and explanations for the current issues). If the owner of the integration or some else wants to keep the integration alive, I'm sure they know what's to do as oAuth is a standard protocol
I think @adamkrol93 is not active anymore. So this integration will be dead.
No won't be dead! The integration has already been fixed! But changes have been made in the Home Assistant development branch. I think in a few days or weeks these changes will be applied to the Home Assistant release.
Sounds good :) So we can use this integration again. I'm actually not 100% happy with the ism7 mqtt addon because I got no updates for cgb-2
Hi Suddenly i Can Not Connect to Wolf smartset via iOS App. It saß Portal is Not Connected. I have Isabels Wolf smartset device in HA also tue ism7mqtt add on. Any ideas how to get iOS App working again?
can we change from cloud login to local login with IP adress.
Also doesn't work any more if I try to connect from my network, neither with the IOS-app nor with any browser (Firefox, Edge, Chrome. Also tested with my MacMini, no response.
From outside (company workplace) I'm getting the website correctly, also if I disable WLAN on my mobile (IOS).
From inside via wget the problem gets more clear.
--2024-03-25 10:37:18-- https://www.wolf-smartset.com/idsrv/.well-known/openid-configuration Resolving www.wolf-smartset.com (www.wolf-smartset.com)... 151.106.68.214 Connecting to www.wolf-smartset.com (www.wolf-smartset.com)|151.106.68.214|:443... connected. HTTP request sent, awaiting response... 429 Too Many Requests 2024-03-25 10:37:18 ERROR 429: Too Many Requests.
Wolf is blocking my IP for too many requests, so is there any point in the code where we can reconfigure the time interval requests to Wolf are performed?
Regards Uwe
if i login to my wolf heat pump air water with local IP adress i must use de password on the sticker on the Wolf link module and not the password from the cloud.
so i can read all parameters with IP adress local i can make screenshots if im home.
i preffer to use in home assistant the local ip and not the cloud.
if i login to my wolf heat pump air water with local IP adress i must use de password on the sticker on the Wolf link module and not the password from the cloud.
so i can read all parameters with IP adress local i can make screenshots if im home.
i preffer to use in home assistant the local ip and not the cloud.
Does your heat pump provide the ism8 interface? At least in my case with ism7 interface, there are no details and parameters shown via the direct web interface. Only general network topics like connection status and LAN/WLAN configuration are available.
if i login to my wolf heat pump air water with local IP adress i must use de password on the sticker on the Wolf link module and not the password from the cloud. so i can read all parameters with IP adress local i can make screenshots if im home. i preffer to use in home assistant the local ip and not the cloud.
Does your heat pump provide the ism8 interface? At least in my case with ism7 interface, there are no details and parameters shown via the direct web interface. Only general network topics like connection status and LAN/WLAN configuration are available.
My heat pump use the ism7 and you are correct if you use a computer and go to the ip adress you can only see the Only general network topics like connection status and LAN/WLAN configuration are available. if you use the app you can open the installation on ip adress then you see heat pump!
My heat pump use the ism7 and you are correct if you use a computer and go to the ip adress you can only see the Only general network topics like connection status and LAN/WLAN configuration are available. if you use the app you can open the installation on ip adress then you see heat pump!
It seems that if you have configured to use the heatpump via the cloud interface, it is not possible to access it via the app in parallel locally. Or I just don't find the right settings.
Theres no web interface available at least for the ism7. You can wait for a fix and use the cloud integration or you go with the offline integration mentioned in this thread some days ago.
If you just want to have a local connect to your ism7 you can use the official pc smart application
https://www.wolf-heiztechnik.at/Downloads/Software-L%C3%B6sungen
PC app will not run on newer pc's . Will be blocked by windiws.
PC app will not run on newer pc's . Will be blocked by windiws.
You can bypass this by running CMD as admin and just put the full path. For example C:\Users\tim\Desktop\wolf.exe
I think @adamkrol93 is not active anymore. So this integration will be dead.
No won't be dead! The integration has already been fixed! But changes have been made in the Home Assistant development branch. I think in a few days or weeks these changes will be applied to the Home Assistant release.
As I am not an expert on pull requests and if they have been pulled or not: Can anyone confirm that this integration is working again as supposed with and athentication has changed to oauth?
Ich kann bestätigen, dass es leider nicht funktioniert.
Nope, doesn't work, updates to HA 2024.4.0
2024-04-05 16:16:24.885 ERROR (MainThread) [homeassistant.components.wolflink] Error fetching wolflink data: Invalid authentication during update
Yep, same @ my end. Still not working :-(
Hi, what I have to do for install the fix? I've already use the command pip install and the name of the package.tar.gz but the issue persist. What's the correct way for resolv the issue? Thanks
@Andes1984 Can you confirm your issue is fixed with the latest 2024.5 release. If yes can you close this issue?
Hi! I confirm that the issue has been fixed!
Thank you
Il giorno gio 2 mag 2024 alle ore 17:37 mtielen @.***> ha scritto:
@Andes1984 https://github.com/Andes1984 Can you confirm your issue is fixed with the latest 2024.5 release. If yes can you close this issue?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104595#issuecomment-2090827082, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHG633I7GWNYB4H2QPANFDZAJMSDAVCNFSM6AAAAAA74G4R52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQHAZDOMBYGI . You are receiving this because you commented.Message ID: @.***>
I can neither confirm nor deny since I do not use the integration any longer. I switched to ism7mqtt.
vindiesel891 @.***> schrieb am Do., 2. Mai 2024, 19:11:
Hi! I confirm that the issue has been fixed!
Thank you
Il giorno gio 2 mag 2024 alle ore 17:37 mtielen @.***> ha scritto:
@Andes1984 https://github.com/Andes1984 Can you confirm your issue is fixed with the latest 2024.5 release. If yes can you close this issue?
— Reply to this email directly, view it on GitHub < https://github.com/home-assistant/core/issues/104595#issuecomment-2090827082>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AGHG633I7GWNYB4H2QPANFDZAJMSDAVCNFSM6AAAAAA74G4R52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQHAZDOMBYGI>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104595#issuecomment-2091092242, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSNYTWGZ32YASN7JEXE2O3ZAJXTRAVCNFSM6AAAAAA74G4R52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGA4TEMRUGI . You are receiving this because you were mentioned.Message ID: @.***>
I can neither confirm nor deny since I do not use the integration any longer. I switched to ism7mqtt. vindiesel891 @.> schrieb am Do., 2. Mai 2024, 19:11: … Hi! I confirm that the issue has been fixed! Thank you Il giorno gio 2 mag 2024 alle ore 17:37 mtielen @.> ha scritto: > @Andes1984 https://github.com/Andes1984 Can you confirm your issue is > fixed with the latest 2024.5 release. If yes can you close this issue? > > — > Reply to this email directly, view it on GitHub > < #104595 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AGHG633I7GWNYB4H2QPANFDZAJMSDAVCNFSM6AAAAAA74G4R52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQHAZDOMBYGI> > . > You are receiving this because you commented.Message ID: > @.> > — Reply to this email directly, view it on GitHub <#104595 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSNYTWGZ32YASN7JEXE2O3ZAJXTRAVCNFSM6AAAAAA74G4R52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGA4TEMRUGI . You are receiving this because you were mentioned.Message ID: @.>
@Andes1984 Can you pls close the issue as it's no longer an issue? Thanks!
The problem
I've been using the integration since September without any issues. Starting about 1 week ago, the sensors are getting unavailable more and more often during the day, coming back to normal without me changing or restarting anything.
I have a Wolf CHA-10, communicating through a ISM7 (Wolf Link Home) which is connected via WiFi. The network connection is stable all the time (checking with a watchdog).
During the unavailable times:
Having the debug mode of the integration activated, these log entries occur when the sensors become unavailable:
2023-11-27 15:53:56.946 ERROR (MainThread) [homeassistant.components.wolflink] Error fetching wolflink data: Error communicating with API:
And sometimes after a few minutes:
2023-11-27 15:57:17.721 DEBUG (MainThread) [homeassistant.components.wolflink] Finished fetching wolflink data in 6.713 seconds (success: False)
What version of Home Assistant Core has the issue?
core-2023.9.2
What was the last working version of Home Assistant Core?
core-2023.9.2
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Wolf SmartSet Service
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wolflink
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