asantaga
v3.4.18 - Hub V2
Hello, I am having a problem with v3.4.18. When updating, I lose the system, even after a factory reset (uninstall). I have to stay on 3.4.17 and it works. I have tested 3.4.18 several times and I lose communication with the Wiser Gateway (v2 hub). I think this is due to: Changed: Communication to v2 hub now uses https over internal network.
When I go to http://192.168.xx.xx/ on my browser, I get information. {“Error”:“Internal Error”,“StatusCode”:404}
When I go to https://192.168.xx.xx, the page does not load. ERR_CONNECTION_REFUSED
I see that the firmware of your hub is 4.36.33, the current firmware is 4.42.23 I think it should be interesting to update this firmware
I have two hubs with this firmware that work fine
@Sosk91 did you make any progress on this?
I think I have a similar issue. I got a v2 hub a few weeks ago and I'm sure it was working with HA, but I guess I let it update to 3.4.18 and didn't immediately notice a problem... But now the Drayton Wiser Integration for Home Assistant will not connect to the Hub V2.
I'm doing it through the Android apps for ease of copying the secret key. These are my steps:
- In Wiser App, Settings > Account > Apps and Connections >Matter
- Add a new connection
- Allow Matter pairing
- Copy (to copy code)
- In HA App, Settings > Devices & Services
- WiserHeatXXXXXX is discovered, click Add
- IP Address and Port Number already populated, Paste Secret Key, then Submit
- "Time out trying o connect to the Wiser Hub. Check your hub is still online and try again"
- Wiser App still showing "Joining available for 00:11:22" and counting down.
- Trying to go to https://192.168.1.zzz I get a 502 Bad Gateway | nginx page.
Is it possible to go back to 3.4.17?
TIA
Further to mine above...
Managed to install 3.4.17. No difference.
Tried using HA on PC browser (carefully copying the secret key): at the moment the connection attempt fails, the Wiser App displays "Connection Error" in red.
No, my problem has not been resolved. I sent an email to Schneider support to request the update, because it cannot be launched locally... (only on the first connection). They told me that they were requesting a forced update, but nothing has happened since then. I am still on version 3.36.