www.brultech.com

So, I officially heard from Bidgely that data sent through the API is not routed through their disaggregation routines. Why? Dunno. Maybe they don't trust it, and don't want to mess up the machine learning?

Anyway, what you can do is send fine-grained data to wattvision, and tell bidgely to pull from wattvision. And it all actually works, and it's pretty cool.

But they are using the Wattvision V1 API, which is slated to go away fairly soon.

Another thought I had was to make a "fakeTED" output for btmon, and send TED5000-like pushes to a destination, using that format. Or a cgi script to make it look like an external application is pulling from an actual ted device, by querying the btmon database...

Bidgely also claims to support the ECM-1240 directly; so the official software must send something with an official handshake to get it accepted. Has anyone looked a that?

I looked at idgely, plotwatt and other and never managed to figure out how to get the GEM to work with them, if you ever figure out let me know.

In the end I just put a full 32 channel GEM in the house and it is pretty apparent to me what spikes are for what devices.

scyto wrote:In the end I just put a full 32 channel GEM in the house and it is pretty apparent to me what spikes are for what devices.

Sure, that's the advantage of the per-channel monitoring - you know exactly what's what. I was more curious to see how well their disaggregation algorithm could figure it out.

scyto wrote:I looked at idgely, plotwatt and other and never managed to figure out how to get the GEM to work with them, if you ever figure out let me know.

In the end I just put a full 32 channel GEM in the house and it is pretty apparent to me what spikes are for what devices.

BTmon.py would be your best bet.

Bidgelys API is too heavy for the GEM to output natively, and PlotWatt requires a time-stamp with every sample, and some back and forth to register devices, etc.

Ok, I finally got it working with btmon.py, shame about the disaggregation.

Any chance the DB might support bidgely directly - does it have enough power?

scyto wrote:Ok, I finally got it working with btmon.py, shame about the disaggregation.

Any chance the DB might support bidgely directly - does it have enough power?

Bidgely is ending support for most 3rd party devices soon.

https://bidgely.uservoice.com/knowledge ... ou-support

Thanks, yes they said the same to me. They don't indicate wether they are dropping their support for public access to the API but blueline indicated to me bidgely only wants to work directly with power companies. so I guess they will only support the devices the power companies tell them to.

And I logged a call to ask them to support you, but yes they said no

scyto wrote:Thanks, yes they said the same to me. They don't indicate wether they are dropping their support for public access to the API but blueline indicated to me bidgely only wants to work directly with power companies. so I guess they will only support the devices the power companies tell them to.

And I logged a call to ask them to support you, but yes they said no

Yeah, I don't think our stuff fits into their ecosystem. It looks like the main focus is to try to detect loads based off of your main load profile.