Have you done a full restart (not just a config reload)?
All the data I send from HA is done via a Node-Red flow.
Hi Brian, I think I had, but I’ve just done another to be sure and I also rebooted my emonbase. Still no sign of the CO2 data. A couple of questions if I may:
(1) Can I see what the HA box is doing in regards to this data? Are there error logs somewhere for example. I can see the /var/log directory but it is apparently empty.
(2) Can I see what the emonbase is receiving? I suppose I could set up POST data logging but that seems like a lot of effort if there’s an easier way to see the data that is being received?
TIA, Dave
I split this out 
You can edit the logger in configuration.yaml to give you more information but I’m not sure what the right component would be. As it is a core component I’d guess homeassistant.components.emoncms_history perhaps… I also do not know how much debug info the component has at the moment.
e.g. - various items I have debug set on…
logger:
# default: debug
# default: info
default: warn
logs:
# homeassistant.components.speedtestdotnet: debug
googleapiclient.discovery: warn
# homeassistant.components.recorder: debug
homeassistant.components.history: debug
# custom_components.mitemp_bt.sensor: debug
custom_components.ble_monitor.bt_helpers: debug
custom_components.fitbit: debug
custom_components.bodymiscale: debug
homeassistant.components.command_line: debug
What is your setup? The home-assistant.log file is found in the config folder (with all your configuration yaml files).
Also Settings -> System -> Logs takes you to the log - scroll to the bottom to get the full log file.
Yes. In emoncms under Admin - emoncms Log
You might find it easier to SSH in and filter a tail or syslog command.
You might want to temporarily change the logging level in the settings.ini file (via SSH).
Thanks
Ah, thanks. It’s a bog standard HA Green. Yes I can see it both in the terminal or in Settings. Sadly, there’s nothing about emoncms_history. The log is pretty short since we had a power failure this morning. There’s some nonsense about emoncms the other way:
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:304
integration: Sensor (documentation, issues)
First occurred: 08:10:10 (2 occurrences)
Last logged: 10:55:10
Entity sensor.emoncms_db1_energy from integration emoncms has state class total_increasing, but its state is not strictly increasing. Triggered by state 52.55 (52.56) with last_updated set to 2024-09-18T07:08:22.369784+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+emoncms%22
Entity sensor.emoncms_import_energy from integration emoncms has state class total_increasing, but its state is not strictly increasing. Triggered by state 13787.37 (13787.38) with last_updated set to 2024-09-18T09:52:22.367446+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+emoncms%22
It’s off-topic but obvious nonsense.
I generally have an ssh session open to the emonbase, so that’s easy. There’s nothing in syslog about the incoming data from HA. I’ve increased the log level to info but there’s still nothing. Do I need to restart anything?
I rebooted the emonbase again but I’m still seeing nothing relevant in /var/log/emoncms/emoncms.log It is logging messages about the feeds I have created from a few of the inputs, but nothing about the input data received.
Did you edit the configuration.yaml to add the logging (and restart)?
This is because the component isn’t compliant with the latest structures in HA. For the incoming data this will be solved shortly (not by me).
Odd. Where is the other data coming from? emonhub?
My data from emonhub comes in via MQTT (rather than HTTP) and the data log looks like this
2024-09-19 21:00:10.-72|INFO|emoncms_mqtt.php|MQTT Valid JSON found
2024-09-19 21:00:10.-72|INFO|emoncms_mqtt.php|Valid time in seconds used 1726779610.5002
2024-09-19 21:00:10.-72|INFO|emoncms_mqtt.php|emon/Serial_PiZ {"MSG": 1789379, "Vrms": 251.08, "P1": 523, "E1": 3422457, "pulse": 1, "time": 1726779610.5001853}
As I don’t use the component, I can’t help much more - sorry.
Sorry, I don’t understand what other data you’re talking about?
Sorry I don’t know anything about ‘data from emonhub’ or MQTT. Your third log entry looks a lot like what I see in the apache log for data that is input via HTTP GET. Sadly apache doesn’t log data sent by POST by default. I suppose I’ll have to jump through the hoops to log it and see whare that takes me.
I enabled POST data logging on the emonbase and it shows that it’s not receiving anything about the CO2 readings. So I suppose there’s something wrong with the way I’ve got HA set up, but I still haven’t been able to see anything relevant in its logging.
Previously you said
Do you see that being received in the emoncms log (not the Apache Log)?
In the emoncms settings.ini file?
No, but I haven’t been checking carefully. I see all the data (except the CO2 readings) in automatically created inputs, so I know it’s there. I don’t see it in the emoncms log at all.
In the dump_io log (i.e. apache error log) I saw all the Govee data but not the CO2 readings
A57.0%2Csensor.h5075_678d_signal_strength%3A-90.0%2Csensor.h5075_62fb_temperature%3A25.6%2Csensor.h5075_62fb_humidity%3A50.1%2Csensor.h5075_62fb_battery%3A51.0%2Csensor.h5075_62fb_signal_strength%3A-73.0%2Csensor.h5075_0973_temperature%3A26.0%2Csensor.h5075_0973_humidity%3A48.4%2Csensor.h5075_0973_signal_strength%3A-79.0%2Csensor.h5075_7865_temperature%3A24.7%2Csensor.h5075_7865_humidity%3A50.6%2Csensor.h5075_7865_battery%3A63.0%2Csensor.h5075_7865_signal_strength%3A-81.0%2Csensor.h5075_a1db_temperature%3A26.2%2Csensor.h5075_a1db_humidity%3A48.1%2Csensor.h5075_a1db_battery%3A64.0%2Csensor.h5075_a1db_signal_strength%3A-63.0%2Csensor.h5075_dca9_temperature%3A23.7%2Csensor.h5075_dca9_humidity%3A55.8%2Csensor.h5075_dca9_battery%3A69.0%2Csensor.h5075_dca9_signal_strength%3A-83.0%2Csensor.h5075_914a_temperature%3A27.2%2Csensor.h5075_914a_humidity%3A47.3%2Csensor.h5075_914a_battery%3A99.0
Yes, that’s right. I’ve put it back to WARN now.