Immediate MQTT publish of cardid via rfid card reader daemon

[Martin-Zentner]

Feature Description

The mqtt-daemon periodically publishes the last read cardid to /phoniebox/attribute/last_card by re-reading a file containing the last cardid. Publishing speed and repetition is limited by the configured interval. To improve speed of MQTT transmission for a newly read cardid, the rfid-reader daemon should publish each cardid to e.g. /phoniebox-fp/attribute/new_card as soon as it is read in.

What functionality would you like to see in your phoniebox?

Usecase: Immediately trigger FHEM commands via RFID cardid on the home automation server. This happens in parallel to local phoniebox processing of the cardid.

How do you envision the feature to work from a users perspective?

Actually I realized the FHEM trigger for any cardid via a NODE-RED flow converting each cardid message into an individual FHEM command, which is then sent from NODE-RED to FHEM via another MQTT topic as soon as the new cardid is published.

That way it is possible to

• define the automation steps in FHEM
• while phoniebox now does the triggering

Converting the cardid payload to FHEM commands is (optionally) done in NODE-RED, which is just nice for visualizing this in NODE-RED dashboards.

The user does just swipe the RFID card on the card reader of the phoniebox. The rest is „instant magic“.

Further information that might help

I pulled some code from the mqtt-daemon and added that in a few blocks to the rfid-reader daemon. So this feature request is already implemented. :-)

Maintenance would be easier, if the mqtt-settings would be moved from the daemons to a central file.

[Martin-Zentner]

#1492

[Martin-Zentner]

Andreas implementation in the MQTT daemon works fine. Thanks.