SWITCH should be part of topic

Iture / RFLinkGateway

MQTT Support for RFLink Gateway (http://www.nemcon.nl/blog2) project

36 stars 33 forks source link

SWITCH should be part of topic #4

Open hcsaustrup opened 7 years ago

hcsaustrup commented 7 years ago

I'm a total newbie here, but wouldn't it make sense if the switch ID was part of the topic? Currently I'm getting two messages for every button I push on my lighting/doorbell remote:

Client mosqsub/13932-wolverine received PUBLISH (d0, q0, r0, m0, '/data/RFLINK/Kaku/41/R/SWITCH', ... (1 bytes)) 0 Client mosqsub/13932-wolverine received PUBLISH (d0, q0, r0, m0, '/data/RFLINK/Kaku/41/R/CMD', ... (3 bytes)) OFF

cephos commented 6 years ago

Had the same Problem and quickly fixed it. Should be implemented with the Following Pull request: https://github.com/Iture/RFLinkGateway/pull/7 As long it's not merged you can clone my forked repo (Was my first and only change so far from Iture-master): https://github.com/cephos/RFLinkGateway Still two messages are published but the CMD-Message with the Switch-ID in the topic.