Topic: FOSHKplugin - brief introduction

[olicat]

Hi!

I now have a first implementation of the custom push notifications in internal test mode.
Is this documentation understandable so far (open the topic custom push notifications (from v0.10))?
Are there any open questions or requests?
My current config looks like that:

Code: [Select]

[Pushover]
PO_ENABLE = True
PO_TOKEN = mytoken
PO_URL =
PO_USER = myuser
PO_CUSTOMWARNING = True
PO_CUSTOM = @tempc <= 2.5,Current temperature (@value°C) is equal or below 2.5°C!,False,
PO_CUSTOM1 = @tempc <= 3.5,Current temperature (@value°C) is equal or below 3.5°C!,False,
PO_CUSTOM5 = @tempf <= 32,Current temperature (@value°F) is equal or below 32°F!,False,
PO_CUSTOM18 = @sunshine > 0,There's sunshine now (@value)!,True,3600
PO_CUSTOM50 = @stationtype != GW1000A_V1.7.4,Update detected\, former version was v1.7.4 - now it's @value!

A special note on this:

lightning < 10miles

The consoles remember the distance of the last lightning permanently - the value is sent again with EVERY data transmission. Even over months ...
I have no idea yet how to build in a special treatment. In addition, FOSHKplugin actually has its own thunderstorm warning - so this custom rule should not be necessary.

Oliver

[thunder.ky]

Hi Oli,

I now have a first implementation of the custom push notifications in internal test mode.
Is this documentation understandable so far (open the topic custom push notifications (from v0.10))?
Are there any open questions or requests?

Wow, this is fantastic. This looks great. I've taken a look at the documentation and it is understandable and clear.

Code: [Select]

PO_CUSTOM = @tempc <= 2.5,Current temperature (@value°C) is equal or below 2.5°C!,False,
PO_CUSTOM1 = @tempc <= 3.5,Current temperature (@value°C) is equal or below 3.5°C!,False,
PO_CUSTOM5 = @tempf <= 32,Current temperature (@value°F) is equal or below 32°F!,False,
PO_CUSTOM18 = @sunshine > 0,There's sunshine now (@value)!,True,3600
PO_CUSTOM50 = @stationtype != GW1000A_V1.7.4,Update detected\, former version was v1.7.4 - now it's @value!


Code: [Select]

PO_CUSTOMn = @key [<,<=,==,>,>=,<>,!=] value,message text,activation,hold time.

In the above configuration. What happens when you leave out the activation & hold time from the configuration?

A special note on this:

lightning < 10miles

The consoles remember the distance of the last lightning permanently - the value is sent again with EVERY data transmission. Even over months ...
I have no idea yet how to build in a special treatment. In addition, FOSHKplugin actually has its own thunderstorm warning - so this custom rule should not be necessary.

Totally understood. The current implementation works well as it is.

Does the v0.10 version that you've allowed me to test have this functionality?

Thanks for your continued work,
Arthur

[olicat]

Hi!

What happens when you leave out the activation & hold time from the configuration?

Perhaps I should describe this in more detail in the recipe?
Whereas more text usually tends to put users off. In any case, defaults are used when the corresponding information is missing:

Code: [Select]

The fields message text, activation and hold time are optional and are provided with the default values if not specified:

message text: "condition "condition" is given!" (condition corresponds to the comparison formula - for example @rainin > 0.55)
activation: True (thus this rule can also be deactivated with False if required)
hold time: 3600 (this corresponds to 1 hour)
Only the condition MUST be specified. But otherwise it doesn't make any sense.

Does the v0.10 version that you've allowed me to test have this functionality?

Not yet.
First of all, I want to test this myself for a while. I would be happy to make this pre-beta available to you (and other interested parties) again in the near future.

Oliver

[KC5JIM]

Hi!

What happens when you leave out the activation & hold time from the configuration?

Perhaps I should describe this in more detail in the recipe?
Whereas more text usually tends to put users off. In any case, defaults are used when the corresponding information is missing:

Code: [Select]

The fields message text, activation and hold time are optional and are provided with the default values if not specified:

message text: "condition "condition" is given!" (condition corresponds to the comparison formula - for example @rainin > 0.55)
activation: True (thus this rule can also be deactivated with False if required)
hold time: 3600 (this corresponds to 1 hour)
Only the condition MUST be specified. But otherwise it doesn't make any sense.

Does the v0.10 version that you've allowed me to test have this functionality?

Not yet.
First of all, I want to test this myself for a while. I would be happy to make this pre-beta available to you (and other interested parties) again in the near future.

Oliver

I'll be happy to test when you are ready.

[thunder.ky]

Perhaps I should describe this in more detail in the recipe?
Whereas more text usually tends to put users off. In any case, defaults are used when the corresponding information is missing:

I don't think you need to add more detail, it was my fault that I overlooked this section in the documentation. 

Code: [Select]

The fields message text, activation and hold time are optional and are provided with the default values if not specified:

message text: "condition "condition" is given!" (condition corresponds to the comparison formula - for example @rainin > 0.55)
activation: True (thus this rule can also be deactivated with False if required)
hold time: 3600 (this corresponds to 1 hour)

Only the condition MUST be specified. But otherwise it doesn't make any sense.

First of all, I want to test this myself for a while. I would be happy to make this pre-beta available to you (and other interested parties) again in the near future.

Understood, thank you.

I look forward to help continue testing.

[olicat]

Hi!

You both should have received a PM. Happy testing!

Oliver

[thunder.ky]

You both should have received a PM. Happy testing!

Got the PM, and have it installed! Looks great so far; no installation issues. Custom notifications set up, tested and working.

[KC5JIM]

Got it installed and have 3 notifications setup. Anxiously waiting...

[KC5JIM]

Notifications triggered and worked perfectly.

[thunder.ky]

Confirming that notifications are working as expected. Very intuitive to set up once I read the documentation fully. 

[olicat]

Hi!

Thank you both for the feedback.
I now have a minor problem with the encoding (special characters when Perl and Python work together) in the LoxBerry version. This is still holding me back from a public beta. But hopefully I will get that fixed very soon.

I'm also tinkering with a sticker/banner solution - possibly for FOSHKplugin. Would something like that be interesting for you?
I see you both use a sticker for your weather data. What is important to you? What would you like to see there?
Here is a demo:

 [ You are not allowed to view attachments ]

Size, background, logo, font size, font type and of course the inscription and content can be adjusted by the user. All keys (both metric and US system) of FOSHKplugin are supported.
The generated image can be stored locally in the file system or remotely via http or FTP.

Oliver

[thunder.ky]

Thank you both for the feedback.

Happy to assist, and appreciate you allowing me to help out.

I now have a minor problem with the encoding (special characters when Perl and Python work together) in the LoxBerry version. This is still holding me back from a public beta. But hopefully I will get that fixed very soon.

 

I'm also tinkering with a sticker/banner solution - possibly for FOSHKplugin. Would something like that be interesting for you?
I see you both use a sticker for your weather data. What is important to you? What would you like to see there?
Here is a demo:

[attachment id=1 msg=457150]

Size, background, logo, font size, font type and of course the inscription and content can be adjusted by the user. All keys (both metric and US system) of FOSHKplugin are supported.
The generated PNG can be stored locally in the file system or remotely via http or FTP.

Ooh, nice. I like the idea of the banner. I'm just using the WeatherCloud banner (it is not very flexible) because I don't have an alternative. So this looks like a really nice option with a lot of helpful content options. 

[olicat]

... regarding banner & sticker ...

This is now running here in test mode. A few examples to illustrate the possibilities can be found here.
I'll write a few lines of documentation now - maybe it will come with v0.10.
Interested?

Oliver

[KC5JIM]

... regarding banner & sticker ...

This is now running here in test mode. A few examples to illustrate the possibilities can be found here.
I'll write a few lines of documentation now - maybe it will come with v0.10.
Interested?

Oliver

Definitely interested. Looks great!

[olicat]

Hi!

Looks great!

Thanks.
The design itself has nothing to do with the way FOSHKplugin works - it only sets the corresponding data at the given coordinates. The basis is always suitable colour/font combinations and, if necessary, background images and superimposed logos. This can be a bit of work until you have moved all the values to the right positions or found suitable background images and logos. A practised handling of graphics programmes (and of course a good eye for design) is very helpful.
But maybe it doesn't always have to be so elaborate. And perhaps there would also be users who would share the corresponding banner definition with others. Perhaps we could also have a competition - but unfortunately I wouldn't have anything as a prize.

Especially for you: a sticker (very) inspired by your Meteotemplate sticker.

Here is the corresponding banner definition to see how it works:

Code: [Select]

[Banner]

image_name = banner-mt.png                                     # filename
image_width = 800
image_height = 170
image_background = space.jpg            # from https://pixabay.com/photos/astronomy-bright-constellation-dark-1867616/
dtime_format = "%b %d %Y, %I:%M %p"

header_font_name = verdana.ttf
header_font_color = white
header_font_size = 22
header_1 = 10,80,Hohen Neuendorf PWS\, Germany,,,,,,,,

line_font_name = verdana.ttf
line_font_color = white
line_font_size = 28
#line_1 = y, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni
line_1 = 50,,,120,tempf,,,,260,humidity,,,,360,baromrelin,,,,510,windspeedmph,,,,640,dailyrainin,,

special_font_name = verdanab.ttf
special_font_color = white
special_font_size = 10
special_1 = 90,140,TODAY,,,,255,TODAY,,,,395,3H,,,,505,MAX TODAY,,,,665,M/Y,,,,
special_2 = 10,660,$datetime,,,,
special_3 = 155,280,https://foshkplugin.phantasoft.de,,,
special_4 = 155,620,FOSHKplugin v0.10,,,

#logo_1 = y,x,name
logo_1 = 3,3,FEWtransKreis.png
logo_2 = 100,3,weather_station_generic.png
logo_3 = 100,730,foshkplugin.png

footer_font_name = verdana.ttf
footer_font_color = white
footer_font_size = 16
#footer_1 = y, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni, key_pos,key,val_pos,value,uni
footer_1 = 108,,,110,tempf_min, / ,,,165,tempf_max,,,,250,humidity_min, / ,,,290,humidity_max,,,,390,ptrend3,,,,515,windgustmph_max,,,,620,monthlyrainin, / ,,,690,yearlyrainin,,
footer_2 = 130,140,°F,,,,270,%,,,,385,inHg,,,,520,mph,,,,670,in,,,,

In any case, the possibilities are already quite extensive in their current state. But there are still a number of limitations.
Hence my original question: what does this function actually have to be able to do? What do you expect as a user?
And:
Is this kind of banner definition too complex?

Oliver

[KC5JIM]

I don't think it's too complex at all.

[olicat]

Hi!

I have now put the first instructions for creating banners on the server: Creation of banners and stickers (from v0.10).
I am curious to see if it is understandable so far.
If you are interested, please contact me for a beta test of this new function.
What is possible with it can best be seen here.

Anyone with ideas for banners or stickers is welcome to share them. I'll see if it's feasible right now.

Oliver

[KC5JIM]

I'll definitely beta test this for you.

[olicat]

Hi!

To the beta testers:
You can update FOSHKplugin to the current developer build in the usual way I described in the last PM. The file name is still unchanged.

The biggest difference to the last internal beta is the support of banners and stickers - described here.
I would be happy if people would test again - especially the banner feature is still so new for me that I can't judge yet whether the documentation and the code are suitable for the general public.

Updated examples of banners and stickers can be found here.
Happy testing!

Oliver

[thunder.ky]

Hi Oli,

To the beta testers:
You can update FOSHKplugin to the current developer build in the usual way I described in the last PM. The file name is still unchanged.

Just getting the opportunity to update and test the banners.

The biggest difference to the last internal beta is the support of banners and stickers - described here.
I would be happy if people would test again - especially the banner feature is still so new for me that I can't judge yet whether the documentation and the code are suitable for the general public.

Updated examples of banners and stickers can be found here.

Will provide feedback after getting things set up.

Thanks,
Arthur

[KC5JIM]

Banner is working perfectly!

[olicat]

Hi!

Thanks for the feedback!
Oh yes, for your attention. Today I added a new feature that can integrate logos into the banner based on the data. Depending on the input data, you can now display a "sun" or a "rain" logo. Or, if a value is exceeded, a red logo can be used instead of the normal green one. Or use logos with arrows.
I have illustrated this in the documentation with an example.

Oliver

[thunder.ky]

The new banner feature is working great! My creation is now on my profile!

[olicat]

Hi!

I have now added two last (?) enhancements to the banner & sticker creation:

• It is now possible to create an output image with round corners without graphics processing. It is irrelevant whether a real background image or "only" a colour is used. The radius of the rounding can also be configured.
• Now existing timestamps (such as last lightning or all min/max times) can be displayed as formatted time in the banner. The output format can be defined for each font definition - it is therefore also possible to output date and time in different lines.

In addition, a frame of any thickness and colour can now be generated for all banners and stickers.

Examples:




The version for internal beta testers is available on the server.
The public beta test will start soon.

Regards, Oliver

[olicat]

Hi!

Does anyone have a need for custom output formats or embedding weather station values into their own documents (text files, web pages)?
FOSHKplugin can replace tags like [[@tempf]] in files with the corresponding value (tempf in this case) and upload these files to a server via FTP, for example.

The TAGFILE function is almost finished and may be included in the next release. The documentation is still in an early stage - but should already give information about the possibilities and the configuration.
A demo page also exists to show the possibilities.

Anyone who would like to test it in advance: please PM.

Oliver