EventGhost

While I'm at it: There's something strange about the "outside" report that I've made. I have put in Stua (living room) just to have another graph in it here, and as you can see the one outside stops to early in both 14 and 7 day report, while it goes (probably) all the way in the two day report. And the data is there, as the 2 day report shows. Can that be something with the handling of the ├©?

Oh, and when creating a report with "Utetemperatur ved d├©ra" as part of it I get "d\xf8ra".

Great, thanks!
Btw we did a bit of simultaneous posting there. I hope you see the one I put above your latest post.

Can that be something with the handling of the ├©?

No, has nothing to do with that. The thing is that 'Stua' has many more data points and when I generate the graph, I start each graph from the first available point. So when you combine data sources like that both graphs will start at the same date & time. This is actually wrong, they should instead end at the same. I have no solution for the moment, a first thought is that I should check which one has most, then add 'zeros' in the beginning to the shortest to make them equal...but it will get complex, I think.

I get "d\xf8ra"

Yeah, is because EG in itself is not handling unicode in all places. EG takes the first parameter as default name for the action. I can change that for instance to report title but it will have the effect that you will have to recreate your report actions (maybe not too much effort?)

1. I see! Kind of weird because I thought they came in pretty much on every send. But I am going to replace that sensor outside with another soon anyway. I don't see that on any other graphs, as far as I can see.

2. Nah, I only have two reports so far. So thanks, please do that.

So, new version uploaded

You have to delete the old report actions (only those creating reports, the rest is ok)

I think I covered all

- supports Fineoffset & Oregon events from ONH (not tested...)
- added field to set report title and heading
- using report title as part of action name

Thanks! I have put them in (just to be sure I took all the py files) and started EG, and I'll let it run over night. Tomorrow I'll try it out, when there should be some data gathered by the NHS setup. Have a great evening in the not so far East!

I have made a new version of the CreateComboHtml.py

The target was to handle multiple data sources with different data ranges. As example, start and/or end for data points might be different. When combining those in the same chart I do the following processing
- checking which data source starts first (this becomes the starting point for the diagram)
- checking which data source ends closest to today (this becomes the end point for the diagram)
- for each data source, checking and adding zero value data points in the beginning if needed to position the graph correctly in the diagram
- filling out eventual gaps in the data sources

Please check and see if you like it (keep a copy of the old if you like to go back). A sample looks like below

Best regards

Beautiful! Love it! Check out this one, with the outdoors temp, where the one that was out so long because of the wrong source format comes in:
This looks great, doesn't it? Thanks!

Yes, very good!

It is interesting to see how well aligned they became, even due to the earlier break. Also interesting to see (and expected I guess) is that the actual outdoor temperature is slightly higher outside of your main house entrance door than under your hytte

Cool, really like it myself

There might be some bugs we find later but at least the main functionality seems there

Best regards, Walter

Yeah, I agree. This is really ready for prime time, I think. Great job, man! And yes, it's always a bit cooler under the acbin, but that's because the temp sensor by the door is higher up, and above a wooden deck, while the one under the cabin is half a meter above the ground. I use them both because the one by the door is about what it "feels like" outside, while the other one is needed to turn on the heat in the water line that goes under the cabin and to the well.

Of course if I should nitpick, there's the "Temperature" just above the graph itself. I'd like that to be configurable as well. Yeah, I guess I'm greedy...

Btw on my system it takes 30 seconds and up to a minute from clicking to edit a report action and until it shows. Is that because the database is large?

"Temperature" just above the graph itself. I'd like that to be configurable as well

I'll have a look on this

Is that because the database is large?

I think so yes, it has room for improvements. Currently I think I read all your databases when you go editing, this might be possible to avoid, we only need the table names I think

Nice, boss!

I made a new version with improved performance when editing settings for reports. The old implementation was 'not the best from optimization point of view', now with the new version you should get a better experience

Regarding the other thing , "Temperature" just above the graph itself. I'd like that to be configurable as well, I simply removed that. I don't think we really need it? It took away a lot of space...

Best regards

Well, the load time was a lot better! Around 10 seconds! But the "Temperature" was still there. And worse: The two graphs with different starting times (ute) were totally unsyncronized again. Both started at the same point, and didn't stop at the same point.

Edit: is it possible you uploaded the correct init, but the wrong combo?

I am using a Google drive for the files, maybe they where not fully synchronized. I just tested now, using a new copy from the Google drive and it is working fine for me...
Could you try to copy the file again?