Add vehicle_id and monitored flag to data for each departure.

This adds two more attributes for each departure, to allow extraction by anyone
interested in monitoring these.

Issue #8

README.md

@@ -38,7 +38,7 @@ If your stop is busy with multiple routes, you can filter by route and/or destin
 Each stop will create a sensor in Home Assistant, which will return the next departure time as its status.
 
 It will also return attributes for departure time, service, service
-name, destination name, stop id for the destination, and status.  The
+name, destination name, stop id for the destination, status and more.  The
 duplication of departure time in the attributes makes more sense when
 there is more than one result being returned.
 

custom_components/metlink/sensor.py

@@ -40,12 +40,14 @@
     ATTR_DESTINATION,
     ATTR_DESTINATION_ID,
     ATTR_EXPECTED,
+    ATTR_MONITORED,
     ATTR_NAME,
     ATTR_OPERATOR,
     ATTR_SERVICE,
     ATTR_STATUS,
     ATTR_STOP,
     ATTR_STOP_NAME,
+    ATTR_VEHICLE,
     ATTRIBUTION,
     CONF_DEST,
     CONF_NUM_DEPARTURES,
@@ -269,6 +271,9 @@ async def async_update(self):
                 self.attrs[ATTR_DELAY + suffix] = int(
                     parse_duration(departure[ATTR_DELAY]) / timedelta(minutes=1)
                 )
+                self.attrs[ATTR_MONITORED + suffix] = departure[ATTR_MONITORED]
+                self.attrs[ATTR_VEHICLE + suffix] = departure[ATTR_VEHICLE]
+
             self._available = True
             # Clear out the unused slots
             for i in range(num, self.num_departures):