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
I came here from a different smart home system which wasn't working for my use case.
Many things need to be transferred to mqtt. So I found https://github.com/embyt/enocean-mqtt which is using your library to publish to mqtt.
If this wrong here let me know and I'll open an issue over at https://github.com/embyt/enocean-mqtt.
Now to the actual problem I see here.:
I use an DSZ14 (A15-12-01) electricity meter which has two readings. Current meter reading and current power consumption.
Both are published to MR and according to DT it is either the meter reading or power consumption.
If you ask me it would make much more sense to publish MR with the current meter reading if DT is 0 and publish PC with the current power consumption if DT is 1.
Then DT would not need to be published at all anymore.
The way it is right now with both values published to the same topic (MR) makes kind of difficult to process the data afterwards.
The text was updated successfully, but these errors were encountered:
Hi,
I came here from a different smart home system which wasn't working for my use case.
Many things need to be transferred to mqtt. So I found https://github.com/embyt/enocean-mqtt which is using your library to publish to mqtt.
If this wrong here let me know and I'll open an issue over at https://github.com/embyt/enocean-mqtt.
Now to the actual problem I see here.:
I use an DSZ14 (A15-12-01) electricity meter which has two readings. Current meter reading and current power consumption.
Both are published to MR and according to DT it is either the meter reading or power consumption.
If you ask me it would make much more sense to publish MR with the current meter reading if DT is 0 and publish PC with the current power consumption if DT is 1.
Then DT would not need to be published at all anymore.
The way it is right now with both values published to the same topic (MR) makes kind of difficult to process the data afterwards.
The text was updated successfully, but these errors were encountered: