@McSorley I considered making it flash and make noises if the train was on time, but it’s such an edge case that I didn’t think it was worth the effort! :)

I’ve finally had a chance to go back and have a look at the API response and I’ve tweaked the code. The new layout shows the destination, planned departure, (estimated departure) and a colour coded late/early/on time status.

I’ve NOT gone and looked at the realtimetrains API - I got sidetracked by MQTT notifications in Magic Mirror instead.

Now includes the platform and a slightly better layout.

@cyberphox Personally I use more than just Z-Wave to control my house. Experience has taught me that the Veralite becomes increasingly unstable when you ask it to deal with too many other plugins or technologies. It’s also costly to implement pure Z-Wave and has gaps in offerings available in the UK.

So I use the Vera to control the Z-wave and let other technologies control their own portfolios. Using OpenHAB I can install the connectors (bindings) that correspond to the different technologies (Z-Wave, BTLE, Hue, Sonos, RFX, Plex, Xiaomi, Weather, Honeywell Heating, Harmony, Onkyo amps etc etc) and then integrate them all together through a single interface.

A Z-Wave door sensor probably costs around £30 in the UK for 1. I got 3 Xiaomi door sensors and the controller hub for £35. Adding temp/humidity sensors at £6 each is also a cheap alternative.

This means I can then write cross technology rules to control the house: If external temperature goes above a certain temperature, set the house heating to eco mode. At bedtime, boost the kids bedroom temperatures, turn on their hues and various fairy lights… and then turn it all off again at lights out. I can integrate presence detection across multiple detectors (Z-Wavre PIR, RFX PIR, BTLE, Wi-Fi) and adjust things accordingly.

You can do the same stuff with Home Assistant. Both platforms have a learning curve (OpenHAB more so), but personally I find it gives me much more options.

@callum8004 copy and paste the same module config with the information for the other station

 {
    module: 		'MMM-UKNationalRail',
    position: 		'bottom_left',
    header:			'Walsall Live Departures',	
    config: 
 		{
 		stationCode: 	'WSL',	
 		app_id: 			'fe0f5d14', 
 		app_key: 		'7de7aa1439665fef7ad6eb151190a6a1', 
 		maxResults: 		3, 
 		showOrigin: 		false,
 		calling_at:		'BHM',
 		showPlatform:	true,
 		}
 },
 {
    module: 		'MMM-UKNationalRail',
    position: 		'bottom_left',
    header:		'Another Station Departures',		
    config: 
 		{
 		stationCode: 	'BSC',	
 		app_id: 			'fe0f5d14'
 		app_key: 		'7de7aa1439665fef7ad6eb151190a6a1', 
 		maxResults: 		3, 
 		showOrigin: 		false,
 		calling_at:		'BHM',
 		showPlatform:	true,
 		}
 },

@callum8004 You have to add a separate set of configs for each station that you want to track.

I added a tweak that I came across while building a different module that means you can now specify multiple device categories. BUT, I’ve not mapped these extra categories to different states.

Basically you can now say show me the Dimmable lights & Switchable lights [2,3] in the new veraCategories part of the config, but it doesn’t differentiate between ON/OFF or a percentage value in between for the dimmable lights.

It also means that you can end up with very long lists of items that take up big chunks of the mirror!

The README in the repo lists the categories.

YMMV.

@cyberphox Personally I use more than just Z-Wave to control my house. Experience has taught me that the Veralite becomes increasingly unstable when you ask it to deal with too many other plugins or technologies. It’s also costly to implement pure Z-Wave and has gaps in offerings available in the UK.

So I use the Vera to control the Z-wave and let other technologies control their own portfolios. Using OpenHAB I can install the connectors (bindings) that correspond to the different technologies (Z-Wave, BTLE, Hue, Sonos, RFX, Plex, Xiaomi, Weather, Honeywell Heating, Harmony, Onkyo amps etc etc) and then integrate them all together through a single interface.

A Z-Wave door sensor probably costs around £30 in the UK for 1. I got 3 Xiaomi door sensors and the controller hub for £35. Adding temp/humidity sensors at £6 each is also a cheap alternative.

This means I can then write cross technology rules to control the house: If external temperature goes above a certain temperature, set the house heating to eco mode. At bedtime, boost the kids bedroom temperatures, turn on their hues and various fairy lights… and then turn it all off again at lights out. I can integrate presence detection across multiple detectors (Z-Wavre PIR, RFX PIR, BTLE, Wi-Fi) and adjust things accordingly.

You can do the same stuff with Home Assistant. Both platforms have a learning curve (OpenHAB more so), but personally I find it gives me much more options.

Simple concept module is here, but it is only a concept/prototype, I’m not planning on taking it any further at this point. If anyone else wants to, they can fork the repo and do with it as they please.

Currently only displays Category 3 (Switchable Light) devices. No other options.

Looking at the possibilities of this, it’s NOT complicated to get the information back from a Veralite.

My ‘simple’ setup lists 12 rooms, 65 devices, 1 scene and 9 categories.

The complexity lies in either displaying it in a meaningful way or providing a configuration capability that allows a users to specify their needs.

• Do we group by room or category? Both? Nested how?
• Are all rooms required?
• Are all categories required?
• Are all devices required?

Personally I control my Vera via OpenHAB and others use Home Assistant. Have you considered those as options and then linking them to the Mirror via their existing modules?

Information on Simple UI based on HTTP requests is here - http://wiki.micasaverde.com/index.php/UI_Simple

@randomnoise Glad you got the answer from Transport API.

I had a quick look at the code, but not having a Pi/Mirror available to run soak tests I’ve not been able to fully test it.

I’ll drop the edits.

N

I suggest your best bet is to log an issue with TransportAPI as they might be able to identify if the issue lies with them or with the info coming through from the train operator.

@yawns Explains why my email had the key and the post was XXXXXX.

Thought I was losing it!