-
Notifications
You must be signed in to change notification settings - Fork 104
VacBot.*_status never gets set #57
Comments
The outer element should contain the inner elements. When debugging did you keep stepping forward to see what happens in It would be best if you set your sucks log level to DEBUG and post the full console output when trying to run your script. |
Here's what I'm running: `vacbot = ConnectVac() _LOGGER.debug("Charge Status:[" + str(vacbot.charge_status) + "]") sleep(5) _LOGGER.debug("Charge Status:[" + str(vacbot.charge_status) + "]") `DEBUG:root:Switching to shorter UID XXX DEBUG:sleekxmpp.xmlstream.xmlstream:Event triggered: ssl_cert |
Same here - I added a debug line in my module and printed the responses below - seems they don't have the td attribute, just an empty id="" so this line 462 is causing it to just return.
|
I've been able to use the sucks library to start and stop my Ecovacs N79s. However, I can't get it to accurately to report status on anything.
I'm using the Cmdswitch2-Ecovacs script: https://github.com/EtienneMD/Cmdswitch2-Ecovacs to integrate with Homebridge.
Running the script through the debugger, I can see the request to get charge status:
DEBUG:sucks:Sending command <iq id="XXX" to="XXX" from="XXX" type="set"><query xmlns="com:ctl"><ctl td="GetChargeState" /></query></iq> DEBUG:sleekxmpp.xmlstream.xmlstream:SEND: <iq id="XXX" to="XXX" from="XXX" type="set"><query xmlns="com:ctl"><ctl td="GetChargeState" /></query></iq> DEBUG:sleekxmpp.xmlstream.xmlstream:RECV: <iq to="XXX" type="result" id="XXX" from="XXX" /> DEBUG:sleekxmpp.xmlstream.xmlstream:RECV: <iq to="XXX" type="set" id="25665" from="XXX"><query xmlns="com:ctl"><ctl id="" ret="ok" errno=""><charge type="SlotCharging" /></ctl></query></iq>
I see the response is sending the correct answer, but inside EcoVacsXMPP._handl_ctl(), the message.getpayload() call only returns the outer element and none of the
<charge>
element that actually contains the information. I'm guessing this is why the status information isn't being set.I don't know enough about SleekXMPP to get to the next step. I'm hoping you can shed some light as to where to look to solve the problem.
The text was updated successfully, but these errors were encountered: