Moved from PI to Win10 Aruba device_tracker stopped working

Configuration
1

Looked through path settings, adjusted and fixed, still no go.
Anyone understand this one?
Worked like a charm on the pi-distro.

device_tracker:

  • platform: aruba
    host: 10.7.0.101
    username: admin
    password: XXXXXX

16-11-13 14:06:07 homeassistant.components.device_tracker: Error setting up platform aruba
Traceback (most recent call last):
File “C:\Users\einar\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\device_tracker_init_.py”, line 136, in setup_platform
scanner = platform.get_scanner(hass, {DOMAIN: p_config})
File “C:\Users\einar\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\device_tracker\aruba.py”, line 40, in get_scanner
scanner = ArubaDeviceScanner(config[DOMAIN])
File “C:\Users\einar\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\device_tracker\aruba.py”, line 59, in init
data = self.get_aruba_data()
File “C:\Users\einar\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\device_tracker\aruba.py”, line 97, in get_aruba_data
ssh = pexpect.spawn(connect.format(self.username, self.host))
AttributeError: module ‘pexpect’ has no attribute ‘spawn’
16-11-13 14:06:10 homeassistant.core: Error inside async loop: Exception in callback _ProactorReadPipeTransport._loop_reading(<_OverlappedF…\xa0\x02\x00’>)
16-11-13 14:06:10 homeassistant.core: Error inside async loop: Exception in callback _ProactorReadPipeTransport._loop_reading(<_OverlappedF…\xa0\x02\x00’>)
16-11-13 14:06:11 homeassistant.components.recorder: Ended unfinished session (id=53 from 2016-11-13 13:02:09.887275)
16-11-13 14:06:11 homeassistant.components.recorder: Found unfinished sessions

Best regards
Snowy

2

I’ve never used this but the docs state that you have to have telnet enabled on your router.

3

Thanks for you reply.
I have opened for telnet, and no sign of stopping this in the FW.
Did boot up the raspberry pi to check in the firewall log.
And DOH!!! its using ssh.
So the documentation says telnet but it uses ssh.
Next step is to find a compatible ssh client that the python script will like to use.

Next step is ready for investigation :slight_smile: