1, Create an outlet device
2, Register a MQTT listener in node_red for said device
3, Connect MQTT to debug
4, "Okay google, turn on DeviceName power"
5, Observe the debug window
I had setup something like this
where by the entry point on the left was pushing back into its self (Causing a loop) rather than pushing into /set to inform the hosted service the switch was on
Instance Type : hosted UserID: u2682
1, Create an outlet device 2, Register a MQTT listener in node_red for said device 3, Connect MQTT to debug 4, "Okay google, turn on DeviceName power" 5, Observe the debug window
18/09/2019, 22:35:24node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}" 18/09/2019, 22:35:24node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}" 18/09/2019, 22:35:25node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}" 18/09/2019, 22:35:25node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}" 18/09/2019, 22:35:25node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}" 18/09/2019, 22:35:26node: e62bf2ac.5a06a gBridge/u2682/dxxxx/onoff : msg.payload : string[14] "{"state":"ON"}"
Expected Behavior Receive one payload from gBridge
Actual Behavior gBridge spams the mqtt server as fast as it can send