The emoncms history integration has been recently updated, it is now using for communications the same lib used by the emoncms integration, so an external lib.
This is something required by home-assistant : all comms must be wrapped in an external lib…
It will be available in the new release of home assistant, probably in september. No breaking change, it is designed to be backward compatible
5 Likes
it is a good step to solve the pending issue
opened 02:36PM - 06 Apr 23 UTC
integration: emoncms_history
### The problem
when i enable this i get a 406 error and i have had this proble… m with a raspberry pi that runs a python script
my webhoster where i have emoncms running requires a user agent when the server is contacted or else it will reject. that is also done on many other servers as a attack prevention thing
conn.request("GET", conarg, headers = {"user-agent": "Mozilla/5.0"})
that solved the problem on my pi, it controls an electrical heating panel and sends in temeprature etc....
### What version of Home Assistant Core has the issue?
2023.3.6
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
emoncms_history
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/emoncms_history/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
completing the pyemoncms lib and bump the lib in HA should do the job
python library for emoncms API
1 Like
does anyone also face a problem of duplicated inputs as reported here ?
opened 07:59AM - 09 Sep 25 UTC
integration: emoncms_history
### The problem
Inputs in EmonCMS "received" from emoncms history integration a… re duplicated. The new input entries have the same identical name of the existing ones but of course are missing of all the processes.
Reverting to 2025.8.3 fix the problem and all the new entries created by 2025.9.0 (and 2025.9.1 as well) are timing out.
### What version of Home Assistant Core has the issue?
core-2025.9.0
### What was the last working version of Home Assistant Core?
core-2025.8.3
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
EmonCMS History
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/emoncms_history/
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
_No response_
christian
13 September 2025 09:00
7
Yes; I was just trying to work out why some data wasn’t coming through and see all except the first one are duplicated.
borpin
16 September 2025 07:50
8
There are a couple of threads on this. It is possibly a legacy format issue. Try forcing the fulljson rather than the legacy format.
