Closed spxhub closed 1 year ago
Hi :slightly_smiling_face: How many instances of the module are we talking about? Can you share your config? Can you be more specific about "but every now and then"? Once a day? Once a week?
Hey, its like four instances with one profile vbb and three profiles of db. Message occures like every second or third update of a module. So like every 4 minutes or so per module (except for the vbb profile). But I think now it has nothing to do with the number of modules since it occured also with the first db profiled module I added.
But I've just discovered something else: When I disabled two of my three slides of the MMM-Carousel module and only keep the one slide with the MMM-PublicTransportHafas modules then the error seems never to occure. I have to look deeper into this but it seems that it may be related to MMM-Carousel.
Update: I've just quick checked it: It is working with only one slide of MMM-Carousel active. It seems also working with any two slides of MMM-Carousel active (only one of them containing MMM-PublicTransportHafas modules), although it could also just make it less frequent. It definitly breaks with three slides of MMM-Carousel active (with only one of them containing MMM-PublicTransportHafas modules). Also had one occurance now with the vbb profiled module gives the same error with different url of course.
MMM-Carousel has "transitionInterval: 20000" and MMM-PublicTransportHafas has "updateEvery: 120" (3 modules) and 180 for one module. (Just if timing is somehow relevant here)
Next thing I try is to empty out the other two slides and see if that has an effect.
Update2: Even with the two other slides empty (only standard news module active for status) the error occures randomly, even though it feels less frequent.
That's interesting. Can you please share a minimal configuration with which the error occurs?
Well, this is odd! I've tried to revert to the above mentioned setup but couldn't reproduce the error. I've had made some changes outside of MM like activating dtoverlay=vc4-kms-v3d since then. But even reverting that only slows down MM and have some of the MMM-PublicTransportHafas modules stuck at "...loading" for an indefinite amount of time but not giving the error again.
So I close here. Maybe come back if somehow this error reoccures in a reproduceable manner.
Anyhow, thanks for this beautiful module! ;-)
I recently installed multiple instances of the MMM-PublicTransportHafas with different profiles. Everything is working so far, but every now and then one or more of the modules configured with the db-profile throws an error like "request to https://reiseauskunft.bahn.de/bin/mgate.exe?checksum={long hash here} failed, reason: socket hang up". (Never happens with other profiles.) The failing modules have different stationIDs.
Then, after 120sec, it works again (With the next update). Changing the "updateEvery"-parameter to 180sec doesn't help.
Any suggestions?
Thanks!