Currently we are in a process of generating JSON outputs through our service calls. So we decided to use HTTP Data Advanced Sensor. However our services using custom headers for authentication. Then we discovered that HTTP Data Advanced Sensor is not supporting Custom Headers. Since we want to populate multiple channels using our JSON outputs, "HTTP Advanced Sensor" is not going to work with us, which is supporting "Custom Headers". Any suggestions to get overcome our scenario? Can we have custom headers for HTTP Data Advanced Sensor?

Article Comments

Would it be possible for you to use HTTP Push Data (Advanced) sensors instead? This means that the device itself has to call the corresponding URL.


Mar, 2017 - Permalink

Thanks for the reply. I think it's not going to work because of the security practices we are following. Is there any possibility to integrate HTTP Advanced sensor, 'Custom Header' handling functionality to HTTP Data Advanced Sensor? If this happened, it would be great. Since we are using your sensors actively in PRODUCTION also, can I submit a feature request for this?


Mar, 2017 - Permalink

Given that the demand for this is rather low, I wouldn't bet my hat on it being implemented. But consider your vote counted.


Mar, 2017 - Permalink

Count my vote. Hoping to see it soon!


Mar, 2017 - Permalink

How much would it cost if we paid for the development of this feature?


Mar, 2017 - Permalink

We don't do paid development. You'll just have to wait on this one. Shouldn't take too long according to the development ticket which has been opened already ;)


Mar, 2017 - Permalink

Perfect, thanks for the update.


Mar, 2017 - Permalink