core: Can't fetch Ebox data

Home Assistant release with the issue:

0.99.3

Last working Home Assistant release (if known): Not known

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on RPI4

Component/platform:

https://www.home-assistant.io/components/ebox/

Description of problem: Can’t seem to retreive the informations .

2019-09-26 21:01:47 ERROR (MainThread) [homeassistant.components.ebox.sensor] Error on receive last EBox data: Can not find limit span

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

- platform: ebox
  username: !secret ebox_username
  password: !secret ebox_password
  name: "Ebox"
  monitored_variables:
    - download
    - upload
    - total
    - balance
    - usage

Traceback (if applicable):

Additional information:

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 27

Most upvoted comments

OK so I managed to get the integration working by copying client.py as stated above. If someone else bumps into this issue, here’s how to fix it.

To do so when running HassOS on RPi:

Install the Portainer add-on.
Un-hide the homeassistant container in the add-on Settings.
Access the container console and browse to /usr/local/lib/python3.8/site-packages/pyebox
Download and replace the file with curl https://raw.githubusercontent.com/titilambert/pyebox/bd38d484db772851916f7d5363f454119eda31bd/pyebox/client.py --output client.py
Restart Home Assistant

jeepotvin on Aug 24, 2020

Go to titilamber’s github and save all three files here: https://github.com/titilambert/pyebox/tree/master/pyebox

Then in home assistant, create a folder named “pyebox” located under the config folder. Under the pyebox folder, paste all three previous files.

You should have something like this:

config
   |-> pyebox
         |-> __init__.py
         |-> __main__.py
         |-> client.py

Reboot, and home assistant will take thoses files instead of the regular ones.

julienlarivee on Sep 14, 2021

Thanks a lot @julienlarivee !!! Sa marche !

sansillusion on Sep 15, 2021

Thanks Julien for sharing, it is working great! The big advantage here over the previously suggested method is that it should survive the next Home Assistant release as the files are hosted in the config folder instead of somewhere in the container.

I still don’t get how come it can’t be permanently fixed though.

jeepotvin on Sep 15, 2021

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] on Apr 27, 2021

Thank you @jeepotvin . Managed to make it work temporarely with your instructions. Hope this can be fixed permanently.

julienlarivee on Aug 24, 2020