Yes it should be possible, emonhub is not dependent on the emonPi board, if you had just copied or swapped the SDcard from the emonPi to the other PI, it would have worked. I think you have gotten a bit confused with your emonhub versions when installing to the 2nd Pi.
At first glance the log output looks like output from original emonHub despite you saying it is the “emonPi variant” because the format of the log output is different for the “emonPi variant”, it has an extra column for the thread name. For example this first line of the log
2016-10-07 16:47:05,025 DEBUG SIGINT received.
would actually be “2016-10-07 16:47:05,025 DEBUG Main SIGINT received.” if it was from the “emonPi variant” of emonHub.
2016-10-07 16:47:05,236 INFO Exiting hub…
2016-10-07 16:47:05,266 INFO Exit completed
2016-10-07 16:47:05,691 INFO EmonHub Pre-Release Development Version (rc1.2)
The line above also says it is emonHub rc1.2 not the “emonPi variant”.
2016-10-07 16:47:05,691 INFO Opening hub…
2016-10-07 16:47:05,692 INFO Logging level set to DEBUG
2016-10-07 16:47:05,692 INFO Creating EmonHubEmoncmsReporter ‘emonCMS’
All reporters were removed from the “emonPi variant” so maybe it is the original version!
2016-10-07 16:47:05,693 INFO Set up reporter ‘emonCMS’ (buffer: memory | size: 1000)
The “emonPi variant” has no buffers to set to 1000 entries therefore it must be the original version.
> 2016-10-07 16:47:05,694 INFO Setting emonCMS url: https://emoncms.org
> 2016-10-07 16:47:05,694 INFO Setting emonCMS apikey: set
> 2016-10-07 16:47:05,694 INFO Creating EmonHubJeeInterfacer 'RFM2Pi'
> 2016-10-07 16:47:05,695 DEBUG Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
> 2016-10-07 16:47:07,699 DEBUG Opening serial port: /dev/ttyAMA0 @ 9600 bits/s
There is no baud detection in the "emonPi variant" for it to cycle though the bauds, this absolutely most definitely the original version.
> 2016-10-07 16:47:09,702 ERROR Unable to create 'RFM2Pi' interfacer: Attempting to use a port that is not open
To be expected if there is no RFM2Pi attached
>2016-10-07 16:47:09,703 INFO Creating EmonHubMqttInterfacer 'MQTT'
Hello what's this? there's no MQTT in original emonHub!
>2016-10-07 16:47:09,704 ERROR Unable to create 'MQTT' interfacer: 'module' object has no attribute 'EmonHubMqttInterfacer'
Told ya!
>2016-10-07 16:47:09,704 INFO Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
There is no need for a "EmoncmsHTTPInterfacer" in the original version of emonhub because it still has Reporters, maybe it is the "emonPi variant"?
>2016-10-07 16:47:09,705 ERROR Unable to create 'emoncmsorg' interfacer: 'module' object has no attribute 'EmonHubEmoncmsHTTPInterfacer'
Maybe not then!
>2016-10-07 16:47:09,706 INFO Creating EmonHubVEDirectInterfacer 'VEDirect'
VEDirectInterfacer was only added to the "emonPi variant"
>2016-10-07 16:47:09,706 ERROR Unable to create 'VEDirect' interfacer: 'module' object has no attribute 'EmonHubVEDirectInterfacer'
This clearly is not the "emonPi variant" of emonhub, but I don't think it is the original version any longer either, perhaps it's a "Battou variant" ???
I'm not sure how you got in this pickle, what were you trying to do? Have you attempted to fashion something specific from the 2 versions or have you accidentally ended up with various parts?
I strongly suspect you have more than one copy of emonhub.conf, or have you just taken the conf from the "emonPi variant" and added it to the "original version" ? (I now suspect this is most likely the case)
Unless you specifically want the original emonhub version you should probably just install the "emonPi variant" clean and then all you need to do is remove the [[RFM2Pi]] from the config and add the VEDirect details to the [interfacer] and [nodes] sections of the emonhub.conf and it should work without any alteration to the serial port, as that has nothing to do with the USB's.
Is there any reason you didn't use the emonSD image on the 2nd Pi?
