The mqtt was actually a really good suggestion, thanks.
I actually have that going as part of the neowx skin and it didn't occur to
me to watch that.
This makes it a little more interesting, I am seeing values in that stream
that are not in the DB
(i hope this paste works lol)
```json
{
"solar": {
"solarAzimuth": 294.569,
"solarAltitude_degree_angle": -23.6877,
"solarTime": 303.218
},
"lunar": {
"lunarAzimuth": 96.6585,
"lunarAltitude_degree_angle": -12.9247,
"lunarTime": 87.4533
},
"lightning": {
"lightning_disturber_count_count": 0.0,
"lightning_num_count": 0.0,
"lightning_strike_count_count": 0.0
},
"battery": {
"ws80_batt_volt": 3.28
},```
The solarAltitude field in the DB has a whack value of 14.something even
though somehow the correct math is being done.
Now I feel like the double _count_count values might be causing the skin
issues.
But none of the above is actually getting recorded into the db other than
the lightning_num_count. Is it just a matter of adding THESE field names to
the DB ?
Op vrijdag 6 maart 2026 om 20:54:46 UTC+1 schreef Conz:
> I am using the customecowitt driver from WernerKr as well as
> neowx-material from seehase.
> For the driver the lightning values are still being weird, but these seem
> very undocumented as to whats actually in them. And the skins have a hard
> time seeing the values.
> There's also the weewx-skyfield-almanac from roe-dl, which was part of the
> neowx install, of which i'm trying to add the sun azimuth as well as the
> moon altitude/azimuth to the DB. (Sun altitude IS in there and IS getting
> updated) but none of the 3 new values are getting added.
> The documentation basically says 'just add the db fields and it should
> work'
> Right now I actually have all skins disabled and I just want the DB to
> have all the values.
>
> Op vrijdag 6 maart 2026 om 20:13:31 UTC+1 schreef Vince Skahan:
>
>> Which driver and extension(s) and skin(s) specifically ? Some log more
>> verbosely if you set debug > 0 in weewx.conf, and weewx itself typically
>> will emit the LOOP data if you run it standalone rather than as a daemon.
>> Many will log warnings/errors to wherever your weewx logs are set to go to.
>>
>> On Friday, March 6, 2026 at 10:36:18 AM UTC-8 Conz wrote:
>>
>>> This is driving me bonkers, how do I actually print loop packets ?
>>> I have put 'weewx.engine.StdPrint' at the start of everything under
>>> [Engine] [[Services]] but all it is printing is incoming packets from the
>>> driver and what they are being mapped to.
>>> .
>>> But want to see the packets from other extensions as well.
>>> I keep running into issues where database fields for extensions (And
>>> actually the driver too) aren't being filled and I just can't troubleshoot
>>> it properly.
>>> I also want to see what is being sent to the skins for the same reason.
>>>
>>> I was using 5.2 but the 5.3.1 update just came through so that's now
>>> live.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/3948ae6b-c08b-4bf5-b1d8-1ac76ccc12can%40googlegroups.com.
