You just need to modify the modules.xml file to fix this without messing with _nodesetup.js. I did this for HEM v1 and it works great. I needed to add "85" to nodeinfo param. Easier said than done, because the value in the XML file is encrypted. I had to follow how HG encrypts the values, then I just manually encrypted my new string and pasted it in. If you remove the device, you would need to modify this value again, so it's not as good has having pepperdb fixed.
We appear to have a local cache of pepperdb. This local cache has the missing value, so I don't know why the module value is wrong. I spent a little time tracing what HG does when filling this field, but have not finished yet (it is not obvious with a quick glance how it works).
Ideally, we would always use the local "cache" of pepperdb first (unless we command an update) that we can manually modify, especially so we won't have to rely on a 3rd party service that could go down any day. I must be missing something, so I will report back when I have more time to go through it.
