Closed mathieu-mp closed 2 years ago
I assume is it linked to parallel updates of status at integration level
Solved by #27
This issue persists
Happened to me today on version 0.1.1. Also on climate entity. I wasn't doing anything special, just moving the preset temperature, to get current_temp update. The error was there for several updates of preset_temp and then it went away and it worked again without problem
I was running tshark today and when this exception started to pop up, there were no packets being sent to device at all
same problem... update from commit 2b69d0c to larest release... before the update it worked perfectly!
OK, thank you for your feedback. I'll work on it. Compare changes on homeassistant-intex-spa: https://github.com/mathieu-mp/homeassistant-intex-spa/compare/2b69d0c...0.1.1 Compare changes on intex-spa: https://github.com/mathieu-mp/intex-spa/compare/0.7.2...0.8.2
I tried to drop/discard packets from hassio to spa silently, but it works ok, spa becomes unavailable. It does not hang like in this issue
I got response with "result" = "timeout", never saw it before. Low level library seems to work ok, it tries again
$ python3 intex_spa_get_status.py
DEBUG:asyncio:Using selector: EpollSelector
WARNING:intex_spa.intex_spa:Initializing IntexSpa instance
DEBUG:intex_spa.intex_spa:'status' intent: Handling new intent...
DEBUG:intex_spa.intex_spa:'status' intent: a spa query is needed
DEBUG:intex_spa.intex_spa:'status' intent: new spa query
INFO:intex_spa.intex_spa_network_layer:Not connected to the spa
DEBUG:intex_spa.intex_spa_network_layer:Opening TCP connection with the spa at 192.168.23.123:8990 with asyncio
INFO:intex_spa.intex_spa_network_layer:TCP connection established with the spa
DEBUG:intex_spa.intex_spa_network_layer:Sending bytes to the spa: b'{"data": "8888060FEE0F01DA", "sid": "16593429608232", "type": 1}'
DEBUG:intex_spa.intex_spa_network_layer:Receiving bytes from the spa: b'{"sid":"16593429608232","data":"","result":"timeout","type":2}\n'
WARNING:intex_spa.intex_spa:Exception raised during spa querying
DEBUG:intex_spa.intex_spa:'status' intent: new spa query
DEBUG:intex_spa.intex_spa_network_layer:Sending bytes to the spa: b'{"data": "8888060FEE0F01DA", "sid": "16593429671316", "type": 1}'
DEBUG:intex_spa.intex_spa_network_layer:Receiving bytes from the spa: b'{"sid":"16593429671316","data":"FFFF110F010300170000000081808020000022","result":"ok","type":2}\n'
DEBUG:intex_spa.intex_spa_status:Spa status: '{'power': True, 'filter': True, 'heater': False, 'jets': False, 'bubbles': False, 'sanitizer': False, 'unit': '°C', 'current_temp': 23, 'preset_temp': 32}'
DEBUG:intex_spa.intex_spa:'status' intent: new status is rendered
{'power': True, 'filter': True, 'heater': False, 'jets': False, 'bubbles': False, 'sanitizer': False, 'unit': '°C', 'current_temp': 23, 'preset_temp': 32}
Maybe , you should check, that "result" = "ok", before trying to work with data?
Maybe , you should check, that "result" = "ok", before trying to work with data?
Well, this assert raises an AssertionError exception which triggers a retry.
This is the same retry you saw on your previous message:
I got response with "result" = "timeout", never saw it before. Low level library seems to work ok, it tries again
Thank you all for your feedbacks ! I still haven't found the time to solve this (and while I didn't spend much time on it, I still have no clue).
Maybe , you should check, that "result" = "ok", before trying to work with data?
Well, this assert raises an AssertionError exception which triggers a retry.
Makes sense, i should really learn something about this stuff (assert, try ,catch ... ), thanks for explanation
This is the same retry you saw on your previous message:
I got response with "result" = "timeout", never saw it before. Low level library seems to work ok, it tries again
Yeah, i noticed the retry in test code and thought it does not propagate up to home assistant integration code, but it does not make sense
Thank you all for your feedbacks ! I still haven't found the time to solve this (and while I didn't spend much time on it, I still have no clue).
You are welcome, it must be something stuck somewhere ;)