-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "time" of transmission in mqtt #147
Comments
Adding time to the returned message should be a function of the framework managing the response, as time requires significantly more complexity. |
I agree with you but I think I was unclear in my request: The bresser weather station sends with each message the current time as received by the on board DCF receiver. the RTL-SDR provides that information a a separate field and also puts that to mqtt like the temperature and other sensors values. Because I switched from raspberry to esp32 wih openmqtt gateway which uses your modules, I noticed that the time field was suddenly missing :-) is there a chance that you could also send this info? |
The device decoders are a direct copy from the rtl_433 code base, without changes. Take a look at the source to see what the issue is |
my apologies, seems that this issue will be fixed as you said on the platform level. In the current 1.7 version it is mentioned in the release notes: [SYS] Add timestamp for messages by @dkneisz in 1technophile/OpenMQTTGateway#1677 and the feature is to be switched on by editing the User_config.h: |
Current Situation
the current mqtt message lacks a "time" field. with rtl_sdr what field gets delivered.
{"model":"Bresser-7in1","id":1272,"temperature_C":16.6,"humidity":89,"wind_max_m_s":0,"wind_avg_m_s":0,"wind_dir_deg":286,"rain_mm":1026.4,"light_klx":9.308,"light_lux":9308,"uv":0.6,"battery_ok":1,"mic":"CRC","protocol":"Bresser Weather Center 7-in-1","rssi":-79,"duration":40000}
Proposed Change
please add the "time" field to the mqtt mesage
Additional Context
No response
The text was updated successfully, but these errors were encountered: