Topic: FOSHKplugin - brief introduction

[3141kd]

1. the ID and key in question is what you find in your account at Wunderground.com - i
https://www.wunderground.com/member/devices
t's NOT your WU account user login credentials !! But the Station-ID and the Station key
they have to be entered without the "[ ]" - if the stationID is "ISAARB3" and the key "abc4711K" then the string looks ...
https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=ISAARB3&PASSWORD=abc4711K@action=updateraw&
2. you have to enter the proper string including the trailing "&" without ""
see https://meshka.eu/Ecowitt/dokuwiki/doku.php?id=start#oftenused
what applies to the Customized server also applies to the FOSHKplugin forward

Thank you very much for the instructions - works perfect now
No [] and no "" and everything is up and running

[galentx]

I updated from an older version of v0.10 (so old it displays no build number in the log) to v0.10 Beta 240921. One of my FWDs is to InfluxDB v2. After the upgrade, I encountered the following error:

Code: [Select]

15.01.2025 23:29:40.277 <ERROR> FWD-00: InfluxDB v2 sending of 193 values to FOSHKplugin@server:8086: The client cannot find organization with name: 'FOSHKplugin' to determine their ID. Are you using token with sufficient permission? (3 tries, queued)
From this exchange https://www.wetterstationsforum.info/viewtopic.php?t=86&start=380#p23759, I learned that an All-Access InfluxDB token might solve the problem. It did, but I am uncomfortable leaving a token with such broad privileges in my configuration file. Has any progress been made in restoring the ability to use a single-bucket read-write token? If not, how can I help?

[olicat]

Hi!

I actually discarded the automatic creation of buckets shortly after installing them in FOSHKplugin because it caused exactly the problems you described. And I still haven't found a way to transfer the required permissions to this bucket.
In the next public beta, the corresponding part will be removed again - the user will have to create the bucket manually again.
Until then, however, you can easily restore the original (and future) state by editing foshkplugin.py:
Change lines 4359 - 4363 (these line numbers only apply to Beta 240921)
from

Code: [Select]

        try:
          buckets_api = client.buckets_api()                   # generate the bucket prophylactically
          buckets_api.create_bucket(bucket_name=dbname)
        except ApiException:                                   # ignore the error message when already existing
          pass
to

Code: [Select]

        #try:
        #  buckets_api = client.buckets_api()                   # generate the bucket prophylactically
        #  buckets_api.create_bucket(bucket_name=dbname)
        #except ApiException:                                   # ignore the error message when already existing
        #  pass

I am in the process of creating a new public beta - but that will take a few more days ...
I apologise for the inconvenience.

Oliver

[galentx]

I am in the process of creating a new public beta - but that will take a few more days ...
I apologise for the inconvenience.

No apology necessary! I'm very grateful for your work and am in no rush at all.

It's interesting that the code causes such problems even fully encapsulated in a try-except block. I'll make the patch and try the read-write token again. Edit: with the patch, the r-w token works again. Perfect for me.

Thank you again for sharing this excellent tool.

-Galen

[galentx]

I have been cleaning up my config and had some new questions. Is it safe to assume that the following parameters are not applicable outside of a Loxone/LoxBerry environment?
LOX_IP
LOX_PORT
LBU_PORT
UDP_ENABLE

[olicat]

Hi!

Is it safe to assume that the following parameters are not applicable outside of a Loxone/LoxBerry environment?

No.

Code: [Select]

LOX_IP =                        # destination-IP or broadcast-address to send data to
LOX_PORT = 12340                # destination-Port - UDP-port to send data to
LBU_PORT = 12341                # local Port - UDP-port to receive UDP-datagrams
UDP_ENABLE = True               # set to False to disable UDP-sending

LOX_IP and LOX_PORT actually relate to the destination for sending all incoming data from the weather station in the FOSHKplugin via UDP.
However, this does not necessarily have to be Loxone - other smart home systems can also be connected via UDP if necessary. And a broadcast address can also be used as the destination address. But you can also set up separate forwards for UDP.

If you want to deactivate the global UDP dispatch, this can be set up via UDP_ENABLE = False without changing the address and port.

However, the LBU_PORT is the local UDP port for controlling FOSHKplugin.
Basically intended as a communication channel between Loxone and FOSHKplugin, this type of communication can of course also be used for other purposes and with other tools. Since the same functions are supported as for control via http, this form of communication is optional.
These functions include restarting FOSHKplugin or the console, initiating the sending of status messages and MinMax values as well as switching FOSHKplugin functions such as debug, leakwarning, co2warning, pushmessages, rebootwarning, customwarning, intervalwarning and others on and off.

Hope this helps,

Oliver

[galentx]

Hope this helps,

Oliver

It does! Thank you for the explanation, Oliver. That all makes perfect sense. I am impressed with how much is packed into this one utility.

[Dead Weather]

Looking for help to forward my data to AmbientWeather.net.
What do I use for forward to url and Station ID?

Thanksl

[olicat]

Hi!

Looking for help to forward my data to AmbientWeather.net.

Have a look here please (Upload to Ambient Weather).
This article may also be of interest: Replacing the console hardware while maintaining an existing database.

Oliver

[Dead Weather]

Thanks!!  That looks like the info I was looking for

Hi!

Looking for help to forward my data to AmbientWeather.net.

Have a look here please (Upload to Ambient Weather).
This article may also be of interest: Replacing the console hardware while maintaining an existing database.

Oliver

[Dead Weather]

So, am I correct that you need to pay to upload to Ambient, even with this plugin?
I was hoping this would allow me to do so, as if I had an Ambient station.

Hi!

Looking for help to forward my data to AmbientWeather.net.

Have a look here please (Upload to Ambient Weather).
This article may also be of interest: Replacing the console hardware while maintaining an existing database.

Oliver

[olicat]

Hi!

So, am I correct that you need to pay to upload to Ambient, even with this plugin?

The operation of the service, the hosting, the databases, the permanent maintenance to keep the service up and running and the constant further development certainly cause considerable costs for Ambient Weather.
In this respect, I believe it is appropriate for Ambient Weather to restrict access to this service to its own stations on the basis of the MAC address.
This means that only stations with the MAC address of an Ambient Weather product are allowed to submit data.
The VW ANET licence is also an Ambient Weather product which enables the use of the weather service.
This means that for a one time payment (no recurring subscription!) you can have any single MAC address authorised for uploading for the rest of your life.

If you have an Ambient Weather weather station, you can have the data sent directly from the console to Ambient Weather.
For all others there is also a possibility with VW ANET and WeatherBridge, WeatherBridgePro, Nano or FOSHKplugin (whereby the latter is free).

Regards, Oliver

[Rover1822]

Hi!

So, am I correct that you need to pay to upload to Ambient, even with this plugin?

The operation of the service, the hosting, the databases, the permanent maintenance to keep the service up and running and the constant further development certainly cause considerable costs for Ambient Weather.
In this respect, I believe it is appropriate for Ambient Weather to restrict access to this service to its own stations on the basis of the MAC address.
This means that only stations with the MAC address of an Ambient Weather product are allowed to submit data.
The VW ANET licence is also an Ambient Weather product which enables the use of the weather service.
This means that for a one time payment (no recurring subscription!) you can have any single MAC address authorised for uploading for the rest of your life.

If you have an Ambient Weather weather station, you can have the data sent directly from the console to Ambient Weather.
For all others there is also a possibility with VW ANET and WeatherBridge, WeatherBridgePro, Nano or FOSHKplugin (whereby the latter is free).

Regards, Oliver

As Oliver mentioned , you can have your data sent directly from your Ambient console (there is no extra cost for this) , you can in addition use the additional custom upload to send data where you want, and use the FOSHKplugin if you so desire.

[Dead Weather]

Thank you both for your replies.

I have an Ecowitt station, thus my interest in this plugin, as I thought it would allow me to upload to ambientweather.net
One interesting tidbit is when I added my Ecowitt sensor MAC addresss to ambientweater.net, it accepted it and showed a green checkmark.

How do I check to see if the plugin is getting data from my station?

[olicat]

Hi!

How do I check to see if the plugin is getting data from my station?

From Installation of FOSHKplugin generic version:

A web browser can be used to check whether FOSHKplugin is running via http://ipaddress:port.
ipaddress is the IP address of the host on which FOSHKplugin is running (see point 3/6 of the installation instructions) and the port is the port on which FOSHKplugin is listening (point 4/6).
If the weather station is sending data, the station's data should be displayed on this page. If a white page is displayed, FOSHKplugin is running, but the weather station has not yet sent any data. If an error is displayed (timeout, page not found), either the specified IP address or port is incorrect or FOSHKplugin is not running at all.

Oliver

[Dead Weather]

Hi Oliver,

If I enter the UDP-port of target system, I get Unable to connect.
If i enter the HTTP-port of LoxBerry, I get a white screen.

Which port should I be using?

Thanks for your help

Hi!

How do I check to see if the plugin is getting data from my station?

From Installation of FOSHKplugin generic version:

A web browser can be used to check whether FOSHKplugin is running via http://ipaddress:port.
ipaddress is the IP address of the host on which FOSHKplugin is running (see point 3/6 of the installation instructions) and the port is the port on which FOSHKplugin is listening (point 4/6).
If the weather station is sending data, the station's data should be displayed on this page. If a white page is displayed, FOSHKplugin is running, but the weather station has not yet sent any data. If an error is displayed (timeout, page not found), either the specified IP address or port is incorrect or FOSHKplugin is not running at all.

Oliver

[olicat]

Hi!

If i enter the HTTP-port of LoxBerry, I get a white screen.

So FOSHKplugin is up and running and awaits data from the console.
The port to use with a web browser is the LBH_PORT.

You should recheck the settings for the custom server on your console (e.g. with WSView Plus):

 [ You are not allowed to view attachments ]

Oliver

[Dead Weather]

Got it fixed, thanks!

So the custom server had http:// ahead of the ip address.
Once I removed this, the plugin started receiving data.

So the plugin is getting data.
For forwarding, what Station ID should I be using?
The MAC address?  The Ambient api key? 
I assume Forward password is just my ambientweather.net password?

I see a passkey in the station data being sent to the plugin.
Is that an Ecowitt passkey?

Hi!

If i enter the HTTP-port of LoxBerry, I get a white screen.

So FOSHKplugin is up and running and awaits data from the console.
The port to use with a web browser is the LBH_PORT.

You should recheck the settings for the custom server on your console (e.g. with WSView Plus):

 [ You are not allowed to view attachments ]

Oliver

[Dead Weather]

Question about multiple forwards and the config file.

In the foshkplugin directory there is foshkplugin.conf and foshkplugin.conf.orig.
If I edit and save the .conf file, the changes do not stick.  Am I supposed to edit the .orig file?

Also, what settings do I add to forward to openweathermap.org?

Thanks in advance

[olicat]

Hi!

In the foshkplugin directory there is foshkplugin.conf and foshkplugin.conf.orig.
If I edit and save the .conf file, the changes do not stick.  Am I supposed to edit the .orig file?

The changes to foshkplugin.conf should be made when FOSHKplugin is not running. So please stop the programme or service first.
The foshkplugin.conf.orig file contains the original contents of the delivery status of the file for documentation purposes. - Changes in this file have no influence on the programme behaviour.

Also, what settings do I add to forward to openweathermap.org?

OpenWeatherMap as a destination is currently not (yet) supported.
So far, I haven't seen any need for it. But maybe I just haven't looked well enough yet? Why should this service be supported?

Oliver

[Dead Weather]

Hi Oliver,

Thanks for clarifying the file system.

I regards to Open Weather, there is no particular reason.  I ran across them and saw they offer ad-free weather so figured it would be nice to add my data.  No biggie.

Thanks for all your help

Hi!

In the foshkplugin directory there is foshkplugin.conf and foshkplugin.conf.orig.
If I edit and save the .conf file, the changes do not stick.  Am I supposed to edit the .orig file?

The changes to foshkplugin.conf should be made when FOSHKplugin is not running. So please stop the programme or service first.
The foshkplugin.conf.orig file contains the original contents of the delivery status of the file for documentation purposes. - Changes in this file have no influence on the programme behaviour.

Also, what settings do I add to forward to openweathermap.org?

OpenWeatherMap as a destination is currently not (yet) supported.
So far, I haven't seen any need for it. But maybe I just haven't looked well enough yet? Why should this service be supported?

Oliver

[Dead Weather]

Hi Oliver,

First, just wanted to say thanks for this software. 
Works exactly as promised.

Now I am ready to add some more forwards.
\is there a guide on how to add more forwards?

Thanks in advance

[olicat]

Hi!

is there a guide on how to add more forwards?

You can find examples and recipes for (almost) all forwards on this page.

Oliver

[Dead Weather]

Thanks for the links.
Do I just post one into my config file?

Hi!

is there a guide on how to add more forwards?

You can find examples and recipes for (almost) all forwards on this page.

Oliver

[olicat]

Hi!

Do I just post one into my config file?

Of course, all these examples must be adapted to your requirements. You will therefore have to change any user names, passwords and, if necessary, destinations.
Otherwise, however, it is copy/paste.
For most destinations, however, you must first set up a corresponding account with the weather service provider in order to obtain the access data. For local services (such as InfluxDB or MQTT), the necessary conditions must also be created beforehand.
Where would you also like to send to?

Oliver