Pimatic v0.9 - destroy function and MQTT

---

If I have in the destroy function unsubscribe from the topic.
And if I not changing the topic and save device, they will be subscribe first and then unsubscibe from the topic, and I have to restart Pimatic to restore functions.

Log of MQTT broker:

1464427662: Received SUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/dht11/temperature (QoS 0)
1464427662: Pimatic 0 mh/gf/lab/esp01/dht11/temperature
1464427662: Sending SUBACK to Pimatic
1464427662: Received SUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/dht11/humidity (QoS 0)
1464427662: Pimatic 0 mh/gf/lab/esp01/dht11/humidity
1464427662: Sending SUBACK to Pimatic
1464427662: Received SUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/system/vcc (QoS 0)
1464427662: Pimatic 0 mh/gf/lab/esp01/system/vcc
1464427662: Sending SUBACK to Pimatic
1464427662: Received UNSUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/dht11/temperature
1464427662: Pimatic mh/gf/lab/esp01/dht11/temperature
1464427662: Received UNSUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/dht11/humidity
1464427662: Pimatic mh/gf/lab/esp01/dht11/humidity
1464427662: Received UNSUBSCRIBE from Pimatic
1464427662:     mh/gf/lab/esp01/system/vcc
1464427662: Pimatic mh/gf/lab/esp01/system/vcc

Should it be reversed?

@wutu said in Pimatic v0.9 - destroy function and MQTT:

And if I not changing the topic and save device, they will be subscribe first and then unsubscibe from the topic, and I have to restart Pimatic to restore functions.

I think this is a bug in pimatic 0.9. I’ll have a look into this asap. As a work-around may be you can defer the subscription a little bit using a timer. I’d start with a smal timeout value then. May be it is enough to the subscription offloaded from the current cycle.

@mwittig
Thank you for the quick reply.
I’ll wait. Do I have to put it on github issue?
It’s one of two things will MQTT module is 100% compatible with PImatic 9. But quite substantial

@wutu Please create an issue for it with a link to this thread! Thanks.

https://github.com/pimatic/pimatic/issues/907

Thanks for reporting, should be fixed in the latest beta.

Thank you.