Hi Thedude
Wow that was quick
Here it Is:
1:
Stock Tasmota:
complexity to deploy: low
Protocols supported: limited
MQTT data : single alphanumeric data field
Use case: if your devices are supported with the stock protocols.
note: You'll have to use VSP associations to distinguish devices but once done its fine. (Or elevate? Not familiar with the option) Not sure if Digoo is supported here as I migrated to Portisch right away.
Tasmota + Portisch
complexity to deploy: average
Protocols supported: extended
MQTT data : same as above
use case: if you have unsupported devices with stock Tasmota.
OpenMQTTgateway + Pilight
complexity to deploy: advanced
Protocols supported: lots
MQTT data : parsed / decoded data (ex: state-open, battery:1, temperature:25)
Use case: devices with multiple data fields, better data handling.
2: OMG is an alternative binary/flash (see 3rd option in #1 above) you either use Tasmota OR OMG. ( Or both like I do. Adds some redundancy, and I've seen some devices supported on one but not the other and vice versa. If you only maintain one bridge i suggest sticking with only one brand of devices to ensure compatibility. Probably sonoff would be your best bet)
3: data is the payload. On a motion sensor you will get a dîfferent payload for each signal but they are unique to each device. For instance "D7586E" will be received every time motion is detected, for another motion sensor it could be E6545B. And for a door/window sensor with open/closed signals you will get 2 unique codes.
4: I have 2 units outdoors and they are doing fine
. If not directly exposed to rain I keep as is
. Otherwise I just add a strip of white electrical tape on the seam. I'd be surprised if they fail. Had X10 in the same locations for years and they never failed. I wouldn't take a chance with a 100$ device but for 10$ its not a big deal.... Another advantage. I actually keep a hot spare just in case
Hope this helps. Cheers.
Wow that was quick
Here it Is:
1:
Stock Tasmota:
complexity to deploy: low
Protocols supported: limited
MQTT data : single alphanumeric data field
Use case: if your devices are supported with the stock protocols.
note: You'll have to use VSP associations to distinguish devices but once done its fine. (Or elevate? Not familiar with the option) Not sure if Digoo is supported here as I migrated to Portisch right away.
Tasmota + Portisch
complexity to deploy: average
Protocols supported: extended
MQTT data : same as above
use case: if you have unsupported devices with stock Tasmota.
OpenMQTTgateway + Pilight
complexity to deploy: advanced
Protocols supported: lots
MQTT data : parsed / decoded data (ex: state-open, battery:1, temperature:25)
Use case: devices with multiple data fields, better data handling.
2: OMG is an alternative binary/flash (see 3rd option in #1 above) you either use Tasmota OR OMG. ( Or both like I do. Adds some redundancy, and I've seen some devices supported on one but not the other and vice versa. If you only maintain one bridge i suggest sticking with only one brand of devices to ensure compatibility. Probably sonoff would be your best bet)
3: data is the payload. On a motion sensor you will get a dîfferent payload for each signal but they are unique to each device. For instance "D7586E" will be received every time motion is detected, for another motion sensor it could be E6545B. And for a door/window sensor with open/closed signals you will get 2 unique codes.
4: I have 2 units outdoors and they are doing fine
. If not directly exposed to rain I keep as is
. Otherwise I just add a strip of white electrical tape on the seam. I'd be surprised if they fail. Had X10 in the same locations for years and they never failed. I wouldn't take a chance with a 100$ device but for 10$ its not a big deal.... Another advantage. I actually keep a hot spare just in case
Hope this helps. Cheers.
Comment