Topic: HP2553 FW 1.8.5 custom server issue with FOSHKplugin

[falkunmalti]

Hi
Since I updated my console firmware to 1.8.5, I cannot connect to my CumulusMX or PWT.  I don't think I made any changes that would cause this to happen.  Looking at the snd log, it looks like the plugin starts up but there is no data flowing.  CMX connects fine if I stop the plugin.  I have not tried reverting to the old firmware yet but thought I would try this first.

This is the last entry in the log.

14.08.2022 11:17:34.722 <OK> firmware update check activated with interval 86400 - to disable set UPD_CHECK = False in config

[olicat]

Hi!

I think FOSHKplugin has started properly and is expecting data. Does the weather station send the data to FOSHKplugin? Does data arrive in the rawlog of FOSHKplugin?
What are the settings for the custom server on the console?

Oliver

[falkunmalti]

Hi

I agree that the plugin seems to be starting up ok.  But there is no data in the raw or snd logs.  The settings of the custom server are:  Enable, same as Ecowiff, 192.168.1.10, port 8998 Interval 16 seconds and path /data/report/.  The interval is the same as in the settings for CMX.

This is the last entry in the raw log 14.08.2022 11:17:34.682 <OK> FOSHKplugin v0.09 started.
This is the last entry in the snd log 14.08.2022 11:17:34.682 <OK> FOSHKplugin v0.09 started

The relevant portion of my conf file follows:
[Config]
LOX_IP = none
LOX_PORT = 12340
LB_IP = 192.168.1.9
LBU_PORT = 12340
LBH_PORT = 8080
LOX_TIME = False
USE_METRIC = True
IGNORE_EMPTY = True
UDP_ENABLE = False
UDP_IGNORE =
UDP_MAXLEN =
UDP_STATRESEND = 0
LANGUAGE = DE
AUTH_PWD =
DEF_SID =
REBOOT_ENABLE = False
RESTART_ENABLE = False
SVC_NAME = foshkplugin

[Weatherstation]
WS_IP = 192.168.1.164
WS_PORT = 45000
WS_INTERVAL = 60
WS90_CONVERT = True

[Export]
EVAL_VALUES = True
ADD_ITEMS =
OUT_TEMP =
OUT_HUM =
OUT_TIME = False
FIX_LIGHTNING = True
UDP_MINMAX = True
URL_REPAIR = True

[Forward]
FWD_ENABLE = True
FWD_CMT = PWT
FWD_URL = http://192.168.1.199:8572/
FWD_INTERVAL = 16
FWD_IGNORE = rfdata
FWD_TYPE = RAWEW
FWD_SID =
FWD_PWD =
FWD_STATUS = False
FWD_MQTTCYCLE = 0
FWD_EXEC =

[Forward-1]
FWD_ENABLE = True
FWD_CMT = CumulusMX
FWD_URL = http://192.168.1.10:8998/station/ecowitt
FWD_INTERVAL = 5
FWD_IGNORE = rfdata
FWD_TYPE = RAWEW
FWD_SID =
FWD_PWD =
FWD_STATUS = False
FWD_MQTTCYCLE = 0
FWD_EXEC =

[olicat]

Hi!

With the current settings for the custom server of your weather station, it sends the data directly to CMX.
This means that FOSHKplugin cannot receive the data at all and therefore cannot forward it to PWT or CMX.
The destination of your weather station should be FOSHKplugin!
Please note the processing route:
weatherstation --> FOSHKplugin --> PWT/CMX (and any other forward target)

In the settings for the custom server, enter the IP address of the host on which FOSHKplugin is running and the port on which FOSHKplugin expects the data - according to your config file 8080.

Oliver

[falkunmalti]

Hi Oliver

All seems to be working well now, both CMX and PWT,  as is my understanding of the process!  Thank you very much.

[falkunmalti]

Hi Olicat

I discovered a problem yesterday when my plugin stopped updating my data.  I first checked whether the plugin was working, which it was but data was not flowing through and neither CMX nor PWT were updating.  I checked the settings on the custom server and therein lay the problem.  All on its own, the console had disabled my custom server and when I reenabled it the settings were all wrong.  As soon as I fixed all the settings, everything started working again.

This have been experiencing this ever since I updated the firmware to 1.8.5 and each time I check the custom server, it was disabled.  Ecowitt has not released a firmware update so what do you suggest I do?  This has happened two or three times since the firmware update and before that it was rock solid.

Thanks.
 

[olicat]

Hi!

How do you check these settings? On the console itself or using a software app? Which app?
The older WS View app is known to break the custom server settings in some cases. Please try the newer WSView Plus app.
Otherwise, this is probably more of an issue for Ecowitt if the behaviour can be narrowed down to WS View and firmware v1.8.5. FOSHKplugin does not touch these settings after initial configuration.

Oliver

[falkunmalti]

I checked the settings on the console after I noticed that CMX and PWT were not updating. I then fixed the settings on the console (which is a bit of a pain).  So no I did not try to check the settings using WSView Plus.  Could it possibly be a bug in the firmware?  I did have some trouble installing the 1.8.5 firmware initially when  the settings did not seem to stick and I had to reenter the settings.  I will post to Ecowitt and see what they say.

[olicat]

Hi!

I also use the HP2551C (among others) with the latest firmware v1.8.5 and FOSHKplugin. So far, however, I have not seen any abnormalities. I haven't heard any complaints from other sources either.
In this respect, it seems to be more of a local problem for you. Are you using (or testing) other software that may want to influence/modify the custom server settings?

To be informed as quickly as possible, I recommend configuring the push notifications of FOSHKplugin via Pushover. Then you would be informed after 3 (standard) missed data transmissions from the console.

Oliver

[falkunmalti]

The only software I use is CMX and I just noticed that it does have an option to set the Ecowitt gateway automatically and I had that option checked.  However if I uncheck that option, it does not give me an option to enter the settings manually.  Anyway I will install pushover and uncheck that option and see what happens.  I will keep an eye on this now. LOL

 

[falkunmalti]

Oliver

I downloaded Pushover but cannot find the plugin on its list of enabled apps.  Is there something special or am I looking at the wrong thing?  I notice there is a pushover enable feature in the config file but there must be something else......

[olicat]

Hi!

Have a look into the receipts section on the FOSHKplugin page under "get push notifications for critical status changes on the smartphone/tablet".

Oliver

[Gyvate]

CMX does the configuration (if you choose to have it done via CMX) only once at setup and writes the info into Cumulus.ini
I suggest you switch off the setup support and do everything manually.
Check your Cumulus.ini file if it contains the setup information for the custom server - if so, delete the entries 
But don't delete the API key and App key if you want to use the backfill feature 

[falkunmalti]

Gyvate

I am not aware of the backfill feature but it sounds interesting.  Could you please elaborate?