andrew_bond jd I've just added a tariff section to my Node-RED flow and (for my current flatrate deal) it returns the tariff start date, the standing charge and the unit charge. The API document points you to the end point "https://api.glowmarkt.com/api/v0-1/resource/YOUR-RESOURCEID/tariff" to return this information. I'd expect it to return a start date for dual tariff and the start times for each rate, if that's what you are on. The API documentation also suggests that Hildebrand/glowmarkt store your data in UTC and it could be this that is causing confusion. Their document also says:
All the data we store is saved in UTC (Coordinated Universal Time), regardless of the timezone it was collected in. For the API to correctly return the data for the period you request you must supply the offset in minutes between the timezone you require and UTC. As an example if you wish to request data in BST (British Summer Time, UTC+1) you should specify an offset of -60. EST (East Coast N America) would be +300.
This suggests to me that the meter might be charging you the right rate for the right time period, but it's the glowmarkt data that is introducing confusion. I guess if you put the oven on just after the hour and finish your baking just before the half-hour is up, you could probably work out what's happening from the downloaded data. I think this might be a feature of glowmarkt rather than EdF.
I've also noticed that within the payload returned by the tariff call, there is a currentRates.rate object. If this changes at the appropriate time, you could query this value just after the changeover to check that it had happened before setting your EV/House battery to charge and stop when it changes back. This would mean that any issues around synchronising of times/timezones wouldn't be an issue. I can't test this as I'm on a flat rate tariff but it would be interesting to know.