If your MM is using the default Weather module with the EnvCanada provider or the 3rd-party MMM-EnvCanada module, there are some upcoming changes announced by Environment Canada that might impact your MM config in some very specific cases. Change #1: A handful of siteCode values are changing and will require a minor config.js update. The changes are: [image: 1787241030225-93478fa2-ea77-4395-8fd8-267f5ff89d2c-image.jpeg] Change#2: A handful of siteCode locations are being relocated to new locations within 5km of the original. This is unlikely to require config.js updates but the changes have been highlighted as FYI. They are: [image: 1787241175345-6cea715c-9c9d-46fb-9026-6127db9bb855-image.jpeg] These Env Canada changes will come into effect as of Oct 6, 2026 are being done to align with other Canadian government databases. I suspect they will impact a very small number of module users (if any).

@crazylegs I helped fix this code (and the Psc lib) long ago cause of the underlying library connecting to the mic in node_helper this.ps = new Psc({ setId: this.name, verbose: true, microphone: this.config.microphone }); is where it connects to the mic and lmtool is the thing I think is in python

@sdetweil @karsten13 Thank you both so much for your guidance! It is much appreciated and I believe I understand what I need to do.

@karsten13 Thanks for highlighting this! I did a quick-and-dirty test in my code using this proxy and I’m now able to pull back the data from the EnvCanada provider! I will likely need to override the default fetchData function since it expects to JSON.parse the Provider data. This is not quite what I need since EnvCanada just provides an XML document to parse (JSON.parse fails…). But now I can at least start playing around some more.