Something not right?

[Craigw]

Question: Is there a way to save output to a local DB and upload to SEG? Currently something appears jacked up in SEG? Currently this is whats in the API trace, and nothing has uploaded since yesterday.

15 seconds ago
status: Error

service:
http://api.smartenergygroups.com/sites/xxxxxxxxxxxxxxx

Request:
(site c0962aebb077d3d (node GEM ? (e_1 92.55)(p_1 6053)(e_3 4.16)(p_3 248)(e_4 24.96)(p_4 1492)(e_5 3.66)(p_5 217)(e_6 .02)(p_6 1)(e_7 22.93)(p_7 1620)(e_8 .63)(p_8 37)(e_9 .06)(p_9 3)(e_10 .03)(p_10 1)(e_11 .00)(p_11 0)(e_12 .02)(p_12 1)(e_13 4.83)(p_13 288)(e_14 .02)(p_14 0)(e_15 .03)(p_15 1)(e_16 5.90)(p_16 353)(e_17 .03)(p_17 1)(e_18 .02)(p_18 1)(e_19 .04)(p_19 2)(e_20 .14)(p_20 8)(e_21 .13)(p_21 7)(e_22 .01)(p_22 0)(voltage 123.2)))
Response:
(status fail seg_internal)

[Teken]

Question: Is there a way to save output to a local DB and upload to SEG? Currently something appears jacked up in SEG? Currently this is whats in the API trace, and nothing has uploaded since yesterday.

15 seconds ago
status: Error

service:
http://api.smartenergygroups.com/sites/xxxxxxxxxxxxxxx

Request:
(site c0962aebb077d3d (node GEM ? (e_1 92.55)(p_1 6053)(e_3 4.16)(p_3 248)(e_4 24.96)(p_4 1492)(e_5 3.66)(p_5 217)(e_6 .02)(p_6 1)(e_7 22.93)(p_7 1620)(e_8 .63)(p_8 37)(e_9 .06)(p_9 3)(e_10 .03)(p_10 1)(e_11 .00)(p_11 0)(e_12 .02)(p_12 1)(e_13 4.83)(p_13 288)(e_14 .02)(p_14 0)(e_15 .03)(p_15 1)(e_16 5.90)(p_16 353)(e_17 .03)(p_17 1)(e_18 .02)(p_18 1)(e_19 .04)(p_19 2)(e_20 .14)(p_20 8)(e_21 .13)(p_21 7)(e_22 .01)(p_22 0)(voltage 123.2)))
Response:
(status fail seg_internal)

Hello Craig,

The SEG is currently experiencing some site issues. As far as I can tell the service is still ingesting the data but its not updating the users widgets etc.

As a data point more for reference, the Dash Box has the ability to gap fill any missing data not received by the SEG service. This was something I pushed for because these sort of service interruptions were prevalent from time to time.

This is why I purchased the Dash Box (DB) because I wanted to ensure I would have all of data stored somewhere if something else was off line or not available. The DB has been that solution and was one of the best investments I made 2-3 years ago.