I have noticed that when using renderE, regardless of whether it is a domestic or Weatherscan installation, encodE always seems to fail at storing data in automatic mode after the initial run. I have run a local forecast directly after a noninitial encode finishes, and the playlist cues with no data present. Weatherscan behaves the same way, though it is unclear to me if encodE's behavior on WXS is caused by the same issue, or if it is because of the state Weatherscan was found in and the issues that came with it. Despite this behavior, both encodE and main.py claim to be sending and receiving data properly in their respective terminal windows, with encodE claiming to have sent data and main,py claiming to have "remotely set" the received data.
I have noticed that when using renderE, regardless of whether it is a domestic or Weatherscan installation, encodE always seems to fail at storing data in automatic mode after the initial run. I have run a local forecast directly after a noninitial encode finishes, and the playlist cues with no data present. Weatherscan behaves the same way, though it is unclear to me if encodE's behavior on WXS is caused by the same issue, or if it is because of the state Weatherscan was found in and the issues that came with it. Despite this behavior, both encodE and main.py claim to be sending and receiving data properly in their respective terminal windows, with encodE claiming to have sent data and main,py claiming to have "remotely set" the received data.