We are aware that some apps are able to retrieve usage data when Loop can't, particularly for gas. There are different ways to request data, and while Loop's should be most effective, it may not work reliably in some circumstances.
Loop uses on demand requests for recent data every 2-3 hours. Meters should respond with data within ~30 seconds - it will take a few hours longer for the data to appear in the app due to the frequency and timing of Loop's data processing.
Some apps use scheduled requests to obtain usage data. The app subscribes to the meter which sends data to its subscribers once per day. The requests are scheduled to run on the meter at some time on day 1. The DCC (smart meter network) has to deliver the data back to the subscriber sometime on day 2, meaning data could be up to 48 hours out of date.
So Loop's approach should be far more effective, but there are a few potential issues:
- On demand requests for third party users (like Loop) may not work. Third parties use a different communication protocol to suppliers. When installing meters, suppliers should test all messages/protocols, but may only test for their own purposes.
- Suppliers don't have access to data available before a switch of supplier. So the ability for a third party to retrieve up to 13 months of historic data stored on a meter may never be tested.
- The northern smart meter network (roughly north of the M62) uses long range radio rather than the 2.5-3G used in the South. This means data capacity is limited and congestion can be an issue, particularly in urban areas.
..so fewer scheduled requests sometimes work more reliably than more on demand requests..
We are planning to support a combination of scheduled requests as well as on demand requests in 2024.