You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few months ago you helped me to realise that the [[sensor_map]] was not indented correctly and that fixed the problem. Now, somehow I am back at this problem and I'm trying to trouble shoot. Here is the summary:
weewx is running on MacOS and it has been working for about a year, but now it is not working anymore.
when I switch back to 'Simulator', weewx posts to windguru correctly - so we know that weewx is working properly. For now, I have left it set on 'Simulator' to prove that it is working. UPDATE - I turned simulator off because it is posting the wrong data to windguru and confusing people.
when the driver was set to 'WeatherFlowUDP', the weewx log file is here, you can see that weatherflowudp is enabled but no [[sensor_map]] is being loaded.
At the same time, I have triple checked that the 'WeatherFlow' section in weewx.conf and all the indentation seems right, you can see it here
I don't know anything about this driver, but I do know that ConfigObj, the library that reads the configuration file, does not care about indentation. It only cares the level of nesting as indicated by the number of subsection brackets.
If the sensor_map is not even trying to be loaded, could it mean that some other dependency is not working properly? If I remember correctly, an incorrect indentation would still result in weewx loading an empty sensor map at load. I don't even see that in the current log files. I may give up on macOS and put a raspberry pi there just to handle weewx. Much more reliable!
Hi,
A few months ago you helped me to realise that the [[sensor_map]] was not indented correctly and that fixed the problem. Now, somehow I am back at this problem and I'm trying to trouble shoot. Here is the summary:
Please let me know if you have any good ideas?
Originally posted by @foilandwater in #22 (comment)
The text was updated successfully, but these errors were encountered: