Flobul
Some stoves have a spare RJ11 connector on the back of it. I wonder, what is the rate of stoves without/with spare RJ11 on the back ? I think, adding...
Thanks for your answer. I tried too, but classes seems not to be exactly the same for esp8266 and esp32. Some code to adapt. When I send all requests in...
Thanks. This is what I had in my mind. ~But I don't think it's possible to make OTA~ Github blocks 302 redirect. Edit: Done with a proxy. So far, here...
Here you go, with OTA up and running.
Ok, done, but not as relevant as I thought. Same for other $uptime, day, hour...
Fixed for me :) thanks
Fixes for my devices. Thanks.
All those sockets are treated via this endpoint and payload: ``` https://smartapi.vesync.com/cloud/v2/deviceManaged/bypassV2 { "appVersion": "VeSync 4.3.40", "phoneBrand": "Jeedom-VeSync", "phoneOS": "Jeedom-VeSync", "traceId": "1733083741506", "acceptLanguage": "fr", "timeZone": "Europe\/Brussels", "accountID": "XXXX", "token": "XXXX",...
Hey. After some digging, I found another way to get all datas from this socket. method 'getProperty' with payload: "powerSwitch_1","realTimeVoltage","realTimePower","electricalEnergy","protectionStatus","voltageUpperThreshold","currentUpperThreshold","scheduleNum","powerSave","powerProtection","powerUpperThreshold","inchings","aways"
getOutletStatus is not used for this socket on the app to maintain status. Got lucky it worked here, but values are slightly different from this other way => But getProperty...