Other idea: maybe I can just simply write a script that reads the data from MQTT and push it to the weewx database (./archive/weewx.sdb) ? I'd write it in the "archive" table, with dateTime and "outTemp" value. And then, weewx wouldn't even actually see the data is not coming from my WMR200.
Is there any issue to do that? Do I also need to populate archive_day_outTemp ? On Sunday, November 8, 2020 at 6:59:29 PM UTC+1 Invisible Man wrote: > >> - https://github.com/bellrichm/WeeWX-MQTTSubscribe > >That takes data from mqtt and treats it like a sensor in weewx. > > Okay, so it's rather this one I need. > > >weewx has a concept of driver and service. I think you will have to > >pehaps modify the WMR200 driver to behave as if temp is not there, and > >run mqttsubscribe as a service to inject temperature from your Wemo. > > Yes that's the idea. Still use WMR200 driver, but add mqttsubscribe as a > service. > The documentation for MQTTSubscribe gives a short example for the service > (see below). I understand where the Engine part goes. But I am not sure > what "topic1" is ? > > > [MQTTSubscribeService] > host = localhost > payload_type = json > [[topics]] > [[[topic1]]] > [[[topic2]]] > [Engine] > [[Services]] data_services = user.MQTTSubscribe.MQTTSubscribeService > > > On Sunday, November 8, 2020 at 5:53:55 PM UTC+1 Greg Troxel wrote: > >> >> Invisible Man <[email protected]> writes: >> >> > The external temperature of my WMR200 is failing, and it's apparently >> > difficult to find a replacement. So, I'm using a temperature sensor I >> did >> > myself (based on a Wemo + DS18B20 sensor) which sends the temperature >> to a >> > MQTT broker (a Raspberry Pi). >> > >> > I've seen at least 2 different projects to use MQTT with Weewx : >> > >> > - https://github.com/morrowwm/weewxMQTT >> >> That publishes data from weewx to mqtt. >> >> > - https://github.com/bellrichm/WeeWX-MQTTSubscribe >> >> That takes data from mqtt and treats it like a sensor in weewx. >> >> > Is there a preferred way? Also, I am going to have some data coming >> from >> > WMR200 (rain, wind...), and some other coming from MQTT (temperature). >> I >> > don't think weewx supports several drivers, does it ? So it means I'll >> keep >> > using wmr200 driver and use something to insert only temperature from >> MQTT. >> >> weewx has a concept of driver and service. I think you will have to >> pehaps modify the WMR200 driver to behave as if temp is not there, and >> run mqttsubscribe as a service to inject temperature from your Wemo. >> >> This is from a big picture viewpoint not so strange, but it is strange >> in that outside temperature is arguably the primary reading from a >> station, so not having that is very odd. Therefore I would not be >> surprised to find a baked-in assumption about that which needs to be >> overridden. >> > -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/ef6aaf69-796e-41f1-90c3-81bbb0e1f443n%40googlegroups.com.
