4 Commits

Author	SHA1	Message	Date
Nick O'Leary	6b3010f95b	Guard against null client in MQTT nodes ... Fixes #130 There was a timing window where a client could connect to a broker just as new flows were deployed that would cause the on-connect callback to be called after client has been set to null. This caused an NPE. The fix is to check client isn't null in the event handler.	2014-01-13 11:27:09 +00:00
Nicholas O'Leary	4475e74187	Overlapping mqtt subs get duplicate messages	2013-12-06 14:19:21 +00:00
Nicholas O'Leary	7040aaa179	Add clientid/username/password to MQTT nodes ... Alternative implementation, closes #42 The username/password as not stored in the main flow file for security reasons; they are stored in the adjacent credentials file. This does mean an extra step to importing an MQTT node, as the user has to manually edit it to re-add username and password if needed.	2013-11-25 22:50:08 +00:00
Nicholas O'Leary	48dabffefc	Move all nodes into core subdirectory ... This makes it easier to distinguish core nodes from those added later	2013-11-14 15:52:19 +00:00