Fuel Streams not showing at all

#1

1) Give a description of the problem
Cannot get any Fuel Streams to appear in dashboard

2) What is the expected behavior?
When either (ZWAVE) Thermostat Temp/Operating State/Operating Mode change, log to Fuel Stream “Thermostat”

3) What is happening/not happening?
I can see each event being registered in the Piston viewer and logs, but no Fuel Streams appear when clicking on “View fuel streams (beta)”

I have tried using the same piston to register light on/off events with the same result. Events register. No Fuel Streams.
I have tried defining a custom variable name and then including the “optional” data source on the physical device. No Fuel Streams.

Data sharing was enabled in my ST Webcore settings.
I’ve cleared and rebuilt the cache.

I’ve tried in Chrome, Chrome Mobile, Firefox, Microsoft Edge.

I feel like I’ve gone as far as I can go trying to solve on my own. I submit myself to the mercy of the Webcore Masters!

4) Post a Green Snapshot of the pistonimage

download
download.png1178×500 54.6 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:30 PM: info ╔ Event processed successfully (132ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:30 PM: trace ║╔ Execution stage complete. (33ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:30 PM: trace ║║ Executed virtual command writeToFuelStream (1ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:30 PM: trace ║║ Executed virtual command writeToFuelStream (1ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:30 PM: trace ║║ Executed virtual command writeToFuelStream (2ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:29 PM: debug ║║ Cancelling statement #2's schedules... 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:29 PM: trace ║╚ Execution stage started 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:29 PM: trace ║ Runtime (37398 bytes) successfully initialized in 45ms (v0.2.101.20171227) (94ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:29 PM: debug ║ RunTime Analysis CS > 16ms > PS > 45ms > PE > 34ms > CE 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:29 PM: info ╚ Received event [Thermostat].thermostatMode = heat with a delay of 83ms 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: info ╔ Event processed successfully (144ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║╔ Execution stage complete. (48ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║║ Executed virtual command writeToFuelStream (1ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║║ Executed virtual command writeToFuelStream (1ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║║ Executed virtual command writeToFuelStream (20ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: debug ║║ Cancelling statement #2's schedules... 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║╚ Execution stage started 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: trace ║ Runtime (37398 bytes) successfully initialized in 43ms (v0.2.101.20171227) (92ms) 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: debug ║ RunTime Analysis CS > 18ms > PS > 43ms > PE > 31ms > CE 437c118a-4faf-49e5-b2c6-d2e026f720aa 6:23:18 PM: info ╚ Received event [Thermostat].thermostatMode = off with a delay of 81ms

#2

You corrupted it by writing strings to the stream. Fuel Streams are only for numbers (integer/decimals).

You will have to write to a new fuel stream

#3

I’ll give it a try right now.

I started by only polling the temperature and still had the same issue though. BRB.

#4

Ok, I rebuilt the Piston from blank and only requested the “temperature” value to be written to a different fuel stream name.

It’s pretty late here, but I’ll check back in the morning.

Thanks for the response.

download
download.png1178×460 70.8 KB

#5

My fuel streams have disappeared after upgrading my webcore yesterday.

#6

The fuel stream did not show up right away, but it showed up this morning! :slight_smile:

It looks like me using this Honeywell ZWAVE Thermostat may not be a good solution for temp monitoring.

It appears to only update when I manually open the ST app and refresh the temperature. (SEE ATTACHED PHOTO)

Unless someone knows how to get this to update more frequently? Maybe buying a dedicated temp sensor would be more appropriate?

EDIT: I changed the Piston last night to poll every 5 minutes instead of on a received event. It’s back to posting only when “Temperature” value changes.

Capture
Capture.JPG1670×420 26.2 KB

#7

Still down?

#8

OK,

Now that I have some data posting, I’m trying to get the thermostat to actually update it’s temp value.

Back to every 5 minutes:

Refresh (Saw on another thermostat piston)
Wait 1 minute (Just because zwave)
Post to fuel stream.

Fingers crossed.

download (1)
download (1).png1178×479 44.3 KB

#9

Glad you are making some progress

#10

It worked! My first data point with a natural temp change just came in without having to manually refresh the temp in ST app!

Thanks for the help c1arkbar! (My last posted piston is valid and now functional.)

Capture
Capture.JPG1297×410 24.9 KB

#11

Great news!! Glad you got it