setting fast poll seems to do nothing

[Human]

I have a new EMU 2, and I've tried setting fast polling to no avail. I even tried sending the example XML provided in your github project for setting fast polling, but I can see no change in behavior. My unit continues to poll every 15s, and queries of its fast poll state show no change:

<FastPollStatus>
  <DeviceMacId>0xMYMACIDHERE</DeviceMacId>
  <MeterMacId>0xMYMETERIDHERE</MeterMacId>
  <Frequency>0x00</Frequency>
  <EndTime>0x00000000</EndTime>
</FastPollStatus>

I assume that the frequency field is some polling interval (in Hz? In seconds between polls?) and that the duration is a time period (in seconds? milliseconds?) after which polling returns to normal, but it'd be nice to see API documentation for specifics.

[mattncsu]

I'm seeing the same issue. If I paste

<Command>
  <Name>set_fast_poll</name>
  <Frequency>0xff</Frequency>
  <Duration>0x03</Duration>
</Command>
<Command>
  <Name>get_fast_poll_status</name>
</Command>

in to the terminal, there doesn't seem to be any change in the fast poll status regardless of a few frequency and duration combinations.

[gitHub-pbMay2021]

https://rainforestautomation.com/wp-content/uploads/2015/03/EAGLE_REST_API-1.0.pdf
is another source of information, but seems inconsistent with the python2 reference code.
No mention of fast_poll there

An earlier product called Raven has some additional docs
https://rainforestautomation.com/wp-content/uploads/2014/02/raven_xml_api_r127.pdf
fast_poll is mentioned here.

====
Some notes from an EMU-2 that has device_info() reporting
FWVersion - 2.0.0 (7400)
HWVersion - 2.7.3

Regarding get/set schedule, from experimentation I have found that the "mode" is:

• "default" when the EMU-2 backlight is on
• "rest" when the EMU-2 backlight is off
  and there are separate schedules for each mode.
  These settings remain across EMU-2 power cycles.

Regarding get_fast_poll_status, my EMU-2 does not reply to the request/command.
I suspect that fast_poll has been replaced by set_schedule.
I have experimented with setting the "demand" schedule to a variety of values from 5 minutes down to 1 second.
The EMU2 seems to issue notifications at about the time intervals specified by this setting until you get below about 15 seconds.
Below 15 seconds the intervals become variable and don't get much faster than every 8 to 12 seconds (and vary in this range). The EMU won't let you set this below 2 - but from my experiments there is no point going below 10 anyway.