Closed danielbrunt57 closed 2 years ago
Sorry I was busy on neviweb130. I'll check if it is possible to increase time-out wait time. But I think it is set in HA. Let me check what I can do. Maybe I can resend the request if I find that DVCCOMMTO message. Note that you posted that issue in sinope-gt125, direct connection to GT125, and it should go in sinope-1, connection via Neviweb
go to https://github.com/claudegel/sinope-1/tree/timeout and copy file climate.py into your custom-components/neviweb/ dir and restart HA when Neviweb reply with DVCCOMMTO, HA should retry to data update. Let me know if it work
Another thing you can try is to re-pair your miwi devices starting with the one closest to the GT125 and going farther. The neviweb device try to connect directly to the GT125 but they also can use another miwi devices as a relay. If your slow device was added first then it cannot goes via another miwi device to contact or receive something from the GT125. I don't think it is a too short timeout delay but just the device that do not receive the request fro Neviweb. My patch will just resend the request another time.
Thanks. I'll try repairing them this weekend...
Try my patch also. resend update request could help to get the device data also
Is there a way to increase the response wait time?
In Neviweb app, it does report but is very slow. It also does update to changes from HA but it does take it's sweet time! I will see if I can relocate the hub but that won't be easy. They are in opposite corners of the townhouse and on different floors (main level vs upstairs).