Bug fix of QUIGG protocol: learning mode, id range 0...4095
pilight version 4.0
Merge remote-tracking branch 'upstream/development' into my_quigg
Quigg protocol values and logic optimized
Final 2nd release quigg switch protocol
Quigg protocol V2 integration of change request
Removal of defines from quigg_switch.h
Several fixes especially in the uuid adhoc feature
fixed: initializer-string for array of chars is too long

Removed unnecessary NULL-Byte at end of string.
Merge pull request #97 from sweetpi/patch-1

fixed: initializer-string for array of chars is too long
Added pilight-flash program to allow manual firmware flashing
Merge branch 'development' of https://github.com/pilight/pilight into development
Fix for in program protocol for ending scripts
Several improvements and fixes

- Updated mongoose again to test the new version.
- Fixed bug in which config get's wrecked on reboot.
- Removed one hardware linked list.
- Some cosmetical updates.
Added support for conrad weather stations and a fix in the arctech_old protocol
Added support for the eHome protocol
Small bugfix in conrad weather protocol and in cmake compiling
Improved process finder
Merge remote-tracking branch 'upstream/development' into my_quigg

Conflicts:
	libs/protocols/quigg_switch.c
This commit makes receiving more stable

Some protocols pretty much use the same structure. However, mostly,
they are also different in a significant way. Previously, pilight
incoorporated the conflicts structure. This meant that the first
matching protocol processed the pulses and the protocols it conflict
with were dependent on this processing. The trouble began when
the first protocol processed the pulses differently from the
conflicting protocols and thereby the conflicting protocols stopped
working. This for example happened with the silvercrest / mumbi /
arctech_old protocol. pilight will now call all protocols separatly
so each of them can process the pulses independently.

To make sure the speed of receiving isn't affected by this change,
a thread safe queue has been introduced between the pulse receiving
and protocol parsing function.

The receiving thread has also got a higher CPU priority so whatever
the Raspberry Pi is doing doesn't affect pilight functionality.

On the side note. A small bug in the coords2tz function was fixed
in which the longitude and latitude where swapped.