I’m probably doing something wrong, but just tried the device module for adding a emonTH following this post and it seems to create an additional 2 inputs at the bottom of the input list, instead of using input #1 & #3 Below are screenshots of the process I followed; [1] [2] [3] [4]

…also, shouldn’t the inputs include a process - x 0.1 to scale the correct values.

You haven’t done anything wrong, it’s because of the age old conflict between input indexes and input names both occupying the “key” field… The templates have been written to suit named inputs and therefore posting to emoncms from emonhub via the bulk input api will not work without changes, either…

[image] Paul: …also, shouldn’t the inputs include a process - x 0.1 to scale the correct values. Yes, but not if you are using the “emonpi” variant of emonhub that does the scaling before sending. There are many potential variations of any given template, many uses will want to track battery…

@trystanlea has said (back in Feb) he will look into allowing both indexed and named inputs to be used in emoncms simultaneously as the current code seriously divides users into one camp or the other, mixing is really quite difficult. [image] EmonHub Development emonHub I…

Hopefully this will be resolved soon, so self-builders will be able make full use of the device module. Paul

Community

OpenEnergyMonitor

Home
Docs
Community
Shop
Search

OpenEnergyMonitor Community

Device Module selecting wrong input

Emoncms

device-module

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled