ValueError: not enough values to unpack (expected 3, got 2)

[zabuldon]

We are expecting this issue again:
RouterOS: 6.40

File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/mikrotik.py", line 137, in scan_devices
    self._update_info()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/device_tracker/mikrotik.py", line 159, in _update_info
    device_names = self.client(cmd='/ip/dhcp-server/lease/getall')
  File "/srv/homeassistant/lib/python3.5/site-packages/librouteros/api.py", line 80, in __call__
    return self._readResponse()
  File "/srv/homeassistant/lib/python3.5/site-packages/librouteros/api.py", line 103, in _readResponse
    reply_word, words = self._readSentence()
  File "/srv/homeassistant/lib/python3.5/site-packages/librouteros/api.py", line 89, in _readSentence
    words = dict(self.parseWord(word) for word in words)
  File "/srv/homeassistant/lib/python3.5/site-packages/librouteros/api.py", line 89, in <genexpr>
    words = dict(self.parseWord(word) for word in words)
  File "/srv/homeassistant/lib/python3.5/site-packages/librouteros/api.py", line 34, in parseWord
    _, key, value = word.split('=', 2)
ValueError: not enough values to unpack (expected 3, got 2)

[luqasz]

Can you reproduce this in some way ?

[zabuldon]

I'll try. Need to downgrade fw to do so

[luqasz]

Both issues occur only on 6.41 ?

[zabuldon]

No. Values to unpack on 6.41. Connection error on 6.41

[zabuldon]

Sorry, no values to unpack on 6.40 On 19 Jan 2018 10:00 pm, vortexius@gmail.com wrote: No. Values to unpack on 6.41. Connection error on 6.41

[luqasz]

In 6.41 changelog.
*) dhcpv4-server - strip trailing "\0" in "hostname" if present;
Can you check what are exact leases when this happens ?

[luqasz]

@zabuldon I've fixed a bug in b1caed9. See if you still have any issues. Maybe both will be fixed.

[zabuldon]

@luqasz was it merged to 1.0.5 release?
P.S.
I have ugly internet connection now, so can't review full commit log.

[luqasz]

was it merged to 1.0.5 release?

yes I did

[luqasz]

@zabuldon Any progress on this issue ?

[zabuldon]

Looks like it fixed