-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon does not succeed in pulling data from ConEd #16
Comments
Seeing exact same thing, with "coned.meter.MeterError: Error requesting meter data" and "Failed to connect to the bus: Failed to connect to socket" Params: |
Seems my UUID and meter number were off on that run, but that is now solved, as i managed to get at least 1 successful read... The good message: {'startTime': '2022-02-06T17:45:00-05:00', 'endTime': '2022-02-06T18:00:00-05:00', 'value': 0.225, 'uom': 'KWH'} The bad [0206/201020.174838:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Traceback (most recent call last): |
hi, I have the same error. Below is the entire error log. Did anyone found out how to solve it? File "/usr/local/lib/python3.7/dist-packages/pyppeteer/execution_context.py", line 238, in _rewriteError |
I have tried many different things to make this addon work, and every time it eventually spits out:
Error requesting meter data
.After installation, the addon also always starts by saying:
Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
.If there is something broken about the interface between the python code and the ConEd system, I hope it can be fixed, however I do not have the technical knowledge required to rebuild it. My issue is very similar to the issue mentioned ~24 days prior to this post.
The text was updated successfully, but these errors were encountered: