You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Homey MQTT Client to push data scraped form my weather station (Renkforce) to Homey. I use my Synology NAS as MQTT server.
Basically everything is working as it should, were it not for the fact that on a daily basis the MQTT Client on Homey crashes. Disabling and then enabling the app restarts the app and the problem is temporarily solved.
From a php script on my Synology every 5 minutes I scrape aproximately 16 variables from the weather station and I publish each variabele to my MQTT server. Could it be that this is too much for the Client app to work in a stable manner?
The error message given by the app (by clicking the red triangle with exclamation mark on the crashed app in Homey Desktop):
Stack trace:
No stack trace available
Exit code: null
Exit signal: SIGKILL
and also
Stack trace:
No stack trace available
Exit code: null
Exit signal: SIGABRT
The mem use fluctuates strongly, but is on the average quite high compared to other apps (f.e. over 60MB is not an unusual sight). After Homey itself, it's structurally the most memory consuming app.
I could rewrite my php script to send the raw data from my weather station via a json post (and the http app) directly to Homey, but generally I like the fact that I can use the data published via MQTT with other subscribed devices as well.
Any solutions?
Thanks in advance,
Gert-Jan.
The text was updated successfully, but these errors were encountered:
I switched to the other Mosquitto app for Homey ("MQTT Client"), and disabled the crashing app. The other app is working fine for several days in a row.
Case closed, as far as I'm concerned.
I use Homey MQTT Client to push data scraped form my weather station (Renkforce) to Homey. I use my Synology NAS as MQTT server.
Basically everything is working as it should, were it not for the fact that on a daily basis the MQTT Client on Homey crashes. Disabling and then enabling the app restarts the app and the problem is temporarily solved.
From a php script on my Synology every 5 minutes I scrape aproximately 16 variables from the weather station and I publish each variabele to my MQTT server. Could it be that this is too much for the Client app to work in a stable manner?
The error message given by the app (by clicking the red triangle with exclamation mark on the crashed app in Homey Desktop):
Stack trace:
No stack trace available
Exit code: null
Exit signal: SIGKILL
and also
Stack trace:
No stack trace available
Exit code: null
Exit signal: SIGABRT
The mem use fluctuates strongly, but is on the average quite high compared to other apps (f.e. over 60MB is not an unusual sight). After Homey itself, it's structurally the most memory consuming app.
I could rewrite my php script to send the raw data from my weather station via a json post (and the http app) directly to Homey, but generally I like the fact that I can use the data published via MQTT with other subscribed devices as well.
Any solutions?
Thanks in advance,
Gert-Jan.
The text was updated successfully, but these errors were encountered: