You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I am not sure if this is the right place to leave this but I am having an issue with the API. My whole purpose to getting the Sense device was to use the second port to 'meter' a second 200amp connection (both in my one big box). I have confirmed with the Sense team normally the legs are measured as the following:
So I re-wired my clamps by swapping them so that I read:
Leg1 = MainLead1 + MainLead2
Leg2 = AuxLead1 + AuxLead2
The easiest way I did this was watching the sense webapp to show me wattage usage per leg, made quick work of it. Then I pull the data down with a python script (from API) and log Leg1/Leg2 wattage into a MySQL Database, which powers a Grafana Graph. My main area of concern is:
The data returned by the API is no longer indicative of that in the webapp for [ Leg1W , Leg2W ] , [ ... ] and still shows very similar numbers in relation to each other as they did before... Here is an example which was too recent to show all the data (i expected this outcome of 1 -1 but not the numbers). My Leg2 has been under 1000 watts through this entire time but the data does not show this:
What are you trying to use from the API? There's probably a simpler way to do this.
If you use the realtime data structure sense.get_realtime() you can access either the individual channels sense.get_realtime()['channels'] or the aux sense.get_realtime()['aux']['solar']. These will provide you with a list of the current power draw for each of the 4 channels or 2 aux leads.
I am trying to track kWh usage to understand usage for Aux lines vs Main lines. That’s why I was trying to get historical data.
If I did it with real-time data I would have to keep the connection alive and log to a DB every second or find a way to query every second which the api call allows me to do with historical data. I then can add this to my DB which Grafana feeds on.
This will also help me trace where a few unknown devices are looking at when the spikes occur on which leg.
Hi - I am not sure if this is the right place to leave this but I am having an issue with the API. My whole purpose to getting the Sense device was to use the second port to 'meter' a second 200amp connection (both in my one big box). I have confirmed with the Sense team normally the legs are measured as the following:
Leg1 = MainClamp1 + AuxClamp1
Leg2 = MainClamp2 + AuxClamp2
So I re-wired my clamps by swapping them so that I read:
Leg1 = MainLead1 + MainLead2
Leg2 = AuxLead1 + AuxLead2
The easiest way I did this was watching the sense webapp to show me wattage usage per leg, made quick work of it. Then I pull the data down with a python script (from API) and log Leg1/Leg2 wattage into a MySQL Database, which powers a Grafana Graph. My main area of concern is:
The data returned by the API is no longer indicative of that in the webapp for [ Leg1W , Leg2W ] , [ ... ] and still shows very similar numbers in relation to each other as they did before... Here is an example which was too recent to show all the data (i expected this outcome of 1 -1 but not the numbers). My Leg2 has been under 1000 watts through this entire time but the data does not show this:
I did factory reset the sense device when swapping the Leads as I did... Not sure what else may be wrong.
Thanks in advance for any help.
Colton Riffel
The text was updated successfully, but these errors were encountered: