Emoncms History

[boelle]

The problem

when i enable this i get a 406 error and i have had this problem 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

[boelle]

i tried to find the folder

Logger: homeassistant.components.emoncms_history
Source: components/emoncms_history/__init__.py:92
Integration: Emoncms History ([documentation](https://www.home-assistant.io/integrations/emoncms_history), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+emoncms_history%22))
First occurred: 16.18.35 (51 occurrences)
Last logged: 16.43.35

Error saving data {sensor.rogalarm_kontor_entre_temperature:22.93,sensor.control_dhw_domestichotwatertanktemperature:54.5} to https://emoncms.net/emoncms//input/post.json (http status code = 406)
Error saving data {sensor.rogalarm_kontor_entre_temperature:23.06,sensor.control_dhw_domestichotwatertanktemperature:54.5} to https://emoncms.net/emoncms//input/post.json (http status code = 406)
Error saving data {sensor.rogalarm_kontor_entre_temperature:23.12,sensor.control_dhw_domestichotwatertanktemperature:54.5} to https://emoncms.net/emoncms//input/post.json (http status code = 406)

[core-ssh /]$ ls addons backup bin command config data dev etc home init lib media mnt opt package proc root run sbin share srv ssl sys tmp usr var [core-ssh /]$ find . -type d -name "emoncms_history"

my hope was that i could peak at the code and add user agtent just to test

[boelle]

if not much mistaken this is where a change is needed:

https://github.com/home-assistant/core/blob/dev/homeassistant/components/emoncms_history/__init__.py#L57

[home-assistant[bot]]

emoncms_history documentation emoncms_history source

[boelle]

emoncms_history documentation emoncms_history source

hi bot... that does not explain how to gain access to the file so i can hand edit and test if my assumption is correct

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[boelle]

It has not been update so yes suggested Edit should still be made

tor. 6. jul. 2023 12.06 skrev issue-triage-workflows[bot] < @.***>:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/90942#issuecomment-1623398133, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5HTLYVSITT63637WCZS2LXO2E27ANCNFSM6AAAAAAWVP462E . You are receiving this because you authored the thread.Message ID: @.***>

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[boelle]

It has not been updated so yes suggested Edit should still be made

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[boelle]

It has not been updated so yes suggested Edit should still be made

[djh42]

Does a real person ever review these things or is @boelle wasting his time?

[boelle]

well the bot text is the same, so i can spare 4 sec to just repeat myself

but to answer your Q.... i guess no

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[boelle]

It has not been updated so yes suggested Edit should still be made

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[boelle]

It has not been updated so yes suggested Edit should still be made