EKM Push

[dgh853]

3 more months - any further progress on this?

I bought my v4 and Push box in 2013 assuming that the EKM Push would be updated to support V4 but still waiting. I have a laptop running 24x7 just to run EKM Dash!

Happy to be part of a beta test/trial if that would speed this up for everyone that's waiting.

Even an explanation of the challenges in getting it working with v4 would help us put the waiting into perspective or someone may even have some suggestions to resolve outstanding issues.

Thanks

[Jameson]

Still hacking away on it on our end. It is all about reliability and scale testing at this point.

Most of the delay has to do with really upping the ante when it comes to data availability, short term, long term data sets, scaling of the architecture, making it so future improvements are easier, etc. We are well over time and well over budget, but the upside is, it will be better than ever.

Here is a data tease if you are interested (from a live v4 meter):

http://col.ekmmetering.com/readMeter/v4 ... ulse_Cnt_2

[stishsun]

I am waiting push support v4 over 1 year, I don't know how long still to wait...

[Jameson]

Yep, we also cant wait!! I have my money on 6 weeks from now. But as we all can tell by now I am a terrible judge of such things

[Kailua]

I haven't checked on this for over a year. Does Push work with v.4 meter now?

[Jameson]

This thread is keeping me awake at night

Nope, still not ready for prime time. It works here in our shop. Reliability, scalability, security, migrating from Push1 to Push2, testing, and future proofing are all on our task list.

We just (last night) tripped over an unforeseen issue, so hopefully we can get that one cleared out of the way pronto.

Thanks for hanging in there.

[nein]

Thanks Jameson.

I was also waiting for a year the Push v4 support, I just received yesterday the email and I'm pleased.

Is there any documentation sneak peek to understand in advance the API?.
I'm planning to install two v4 within the next two months and I'd love to start making the changes in my code.

Also, the refresh time with the new pushes will remains in 60 seconds?

Regards,
Diego.

[Jameson]

Woohoo! fingers crossed.

We dont have much in the way of documentation available right off, but what we do have is this API tool: http://107.191.48.206:1000/

This tool shows you how to create a call (in this case to col.ekmmetering.com), in the future it will be to io.ekmpush.com (I would just play around with it to get a sense of what you are able to do)

Here are some examples:

v.3 meter 47 has some good data. Push key is: NjUyMTgwOTk6alJxekRVY0g
v.4 meter 300000369 has a real water meter attached to it, so will give some interesting pulse count 1 data. Push Key is: MTExOjExMQ

If you are curious what the v.4 meter data will look like, take a look at these links:

http://72.52.205.201/readMeter/v4/key/M ... ulse_Cnt_2

http://72.52.205.201/readMeter/v4/key/M ... s_Angeles/

If you have any questions, or if you want us to setup your v.4 meter to work with your EKM Push ahead of time, please let us know.

Yes, if you were set to 60 second reads before, you will still get your data once every 60 seconds.

Thanks,

[Jameson]

Also,

If you setup your EKM Dash like the following screenshot, you will be able to retrieve new Push data from v.4 meter 300000369

[dgh853]

Great stuff, I'm able to get the Push working with my V4 meter.

I'm also able to use Dash to retrieve what has been sent to EKM and forward to Wattvision and onto pvoutput. Any idea if pvoutput can read directly from the EKM database /api for v4 meters as this would remove the need to use a laptop altogether to publish to pvoutput. Setting pvoutput to ekm meter as a source doesn't work for me.

Thanks