As per title, the RM end points on HE running v2.3.4.128 return a result for a trigger that isn't correctly formed json. Some software might barf at the returned result and point the finger at HE as being at fault (which technically it is) - so perhaps consider fixing that in the next release if it isn't fixed already in later releases.
Should be easy to check as the incorrect returned json is {'result':'triggered'} when it should be using double quotes such as {"result":"triggered"}
