using the baby stop stop_id=PLAZA:2 it works fine. using a mother stop worked last week, but i noticed yesterday it stopped working.
(the realtime departures seem to still be working for both mother and baby stops.)
please re-enable the old scheduled times functionality for the mother stops.

this is actually a step in the opposite direction of something i was itching to request:

GetDeparturesByStop, GetStopTimesByStop, and GetRoutesByStop should all allow a semi-colon separated list of stop_id's.
there are certain stops where you guys failed to collect the baby stops underneath one mother stop namely:
LSE LSG LSGS, IU IUE, CHEMLS KRANNERT, GDWNCB GDWNMRL, RACEWASH1 RACEWASH2, RNDLFCLMBA CLMBARNDLF, UNIRNDLF RNDLFUNI.

IT and PLAZA both allow full viewing of all the realtime (and up until yesterday the scheduled) times for all of their collected baby stops in one list, but the above stops are uncollected and in fact it would be furthermore more useful if multiple stop_id's were allowed then one could get the times for four nearby (mother) stops in one single request.

both the time requests already specify the stop_id for each time given so this feature wouldn't affect the data format, but the route data format doesn't include which stop it services so that would need to be added (see my upcoming request on additional info)

UNIWLNT WLNTUNI, RNDLFCLMBA CLMBARNDLF, WLNTMN MNWLNT
instead of combining CLMBARNDLF with RNDLFCLMBA,
CLMBARNDLF:1 was completely deleted, 1/100N still go there on the NE corner


would a semi-colon separated list of stop_id's (instead of just one) for GetDeparturesByStop, GetStopTimesByStop, and GetRoutesByStop
be something you guys would consider enabling?

i directly responded to your request.

you asked if i knew of any other stops that were not combined, so i listed them just as i did above.
and i pointed out that specific stop instead of combining that stop with the one across the street,
you guys deleted a stop, despite the fact it is still used.