All of my feeds have become "inactive" and data is no longer logging

I have not looked at my emonpi in a while as I mainly use it to monitor A/C energy use in the summer. Today I logged in and data has not been logging since December. All of my feeds say “inactive” and there doesn’t seem to be any obvious way to turn them back on.

I have updated the software and restarted the device but it’s still not working. I don’t really know how to start debugging this.

Welcome, Stephen, to the forum.

There isn’t a way to “turn on” your feeds - they will update when data arrives in emonCMS from emonHub and is processed. So you need to start where the data comes in and follow it through.

Have you looked at emonHub? This is where the data from the analogue part (the energy monitor) first enters the Raspberry Pi. If you go to Setup → Emonhub (the loudhailer icon), it should open showing the emonHub log. Every 10 s, it should update with new values, something like

2024-05-01 16:48:09,745 DEBUG    EmonPi2    279529 NEW FRAME : OK 5 195 87 6 0 0 0 0 0 0 0 60 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 200 0 0 0 46 0 0 0 (-0)
2024-05-01 16:48:09,748 DEBUG    EmonPi2    279529 Timestamp : 1714578489.745139
2024-05-01 16:48:09,749 DEBUG    EmonPi2    279529 From Node : 5
2024-05-01 16:48:09,749 DEBUG    EmonPi2    279529    Values : [415683, 0, 0, 0, 0.6, 0, 0, 0, 0, 0, 0, 0, 0, 200, 46, 0, 0.0]
2024-05-01 16:48:09,750 DEBUG    EmonPi2    279529 Sent to channel(start)' : ToEmonCMS
2024-05-01 16:48:09,751 DEBUG    EmonPi2    279529 Sent to channel(end)' : ToEmonCMS
2024-05-01 16:48:09,872 DEBUG    MQTT       Publishing: emon/emonpiCM_5/Msg 415683
2024-05-01 16:48:09,874 DEBUG    MQTT       Publishing: emon/emonpiCM_5/power1 0
2024-05-01 16:48:09,875 DEBUG    MQTT       Publishing: emon/emonpiCM_5/power2 0
2024-05-01 16:48:09,877 DEBUG    MQTT       Publishing: emon/emonpiCM_5/power1pluspower2 0
2024-05-01 16:48:09,878 DEBUG    MQTT       Publishing: emon/emonpiCM_5/vrms 0.6
2024-05-01 16:48:09,880 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t1 0
2024-05-01 16:48:09,882 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t2 0
2024-05-01 16:48:09,883 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t3 0
2024-05-01 16:48:09,885 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t4 0
2024-05-01 16:48:09,887 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t5 0
2024-05-01 16:48:09,889 DEBUG    MQTT       Publishing: emon/emonpiCM_5/t6 0
2024-05-01 16:48:09,891 DEBUG    MQTT       Publishing: emon/emonpiCM_5/pulse1count 0
2024-05-01 16:48:09,892 DEBUG    MQTT       Publishing: emon/emonpiCM_5/pulse2count 0
2024-05-01 16:48:09,894 DEBUG    MQTT       Publishing: emon/emonpiCM_5/E1 200
2024-05-01 16:48:09,896 DEBUG    MQTT       Publishing: emon/emonpiCM_5/E2 46
2024-05-01 16:48:09,898 DEBUG    MQTT       Publishing: emon/emonpiCM_5/missed 0
2024-05-01 16:48:09,899 DEBUG    MQTT       Publishing: emon/emonpiCM_5/missedprc 0.0

If it is updating, look at the Inputs page and on the right there should be a column of times in green (up to 10 seconds since the data last came in) if that shows n/a in red, the data isn’t getting into emonCMS.

Still in Setup, go to Admin at the bottom of the menu, and look there: you should see a lot of Services listed, all should be Active and Running, except possibly for demandshaper: Not found or not installed

I’m not a RPi or emonCMS expert, so when you report back what you’ve found, I’ll need to hand over to somebody who knows more.

Thanks for your response. I have no clue how this thing works so it’s good to get some pointers!

The data is not appearing in emonhub. This is the log since it restarted about 11 hours ago:

2024-05-01 11:02:49,479 INFO     MainThread EmonHub v2.6.6
2024-05-01 11:02:49,480 INFO     MainThread Opening hub...
2024-05-01 11:02:49,481 INFO     MainThread Running as user: pi
2024-05-01 11:02:49,481 INFO     MainThread Logging level set to DEBUG
2024-05-01 11:02:49,482 INFO     MainThread Creating EmonHubJeeInterfacer 'RFM2Pi'
2024-05-01 11:02:49,484 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2024-05-01 11:02:51,486 WARNING  MainThread Device communication error - check settings
2024-05-01 11:02:51,487 INFO     MainThread Setting RFM2Pi baseid: 5 (5i)
2024-05-01 11:02:52,489 INFO     MainThread Setting RFM2Pi frequency: 433 (4b)
2024-05-01 11:02:53,491 INFO     MainThread Setting RFM2Pi group: 210 (210g)
2024-05-01 11:02:54,493 INFO     MainThread Setting RFM2Pi quiet: 1 (1q)
2024-05-01 11:02:55,495 INFO     MainThread Setting RFM2Pi calibration: 230V (1p)
2024-05-01 11:02:56,497 DEBUG    MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2024-05-01 11:02:56,497 DEBUG    MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2024-05-01 11:02:56,499 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2024-05-01 11:02:56,501 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2024-05-01 11:02:56,502 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2024-05-01 11:02:56,502 INFO     MainThread Setting MQTT node_format_enable: 1
2024-05-01 11:02:56,502 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2024-05-01 11:02:56,503 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/
2024-05-01 11:02:56,503 INFO     MainThread Setting MQTT node_JSON_enable: 0
2024-05-01 11:02:56,504 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
2024-05-01 11:02:56,506 DEBUG    MainThread Setting emoncmsorg pubchannels: ['ToRFM12']
2024-05-01 11:02:56,507 DEBUG    MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2024-05-01 11:02:56,507 WARNING  MainThread Setting emoncmsorg apikey: obscured
2024-05-01 11:02:56,508 INFO     MainThread Setting emoncmsorg url: https://emoncms.org
2024-05-01 11:02:56,508 INFO     MainThread Setting emoncmsorg senddata: 1
2024-05-01 11:02:56,508 INFO     MainThread Setting emoncmsorg sendstatus: 1
2024-05-01 11:02:56,509 INFO     MainThread Setting emoncmsorg sendnames: 0
2024-05-01 11:02:56,509 INFO     MainThread Setting emoncmsorg compress: 0
2024-05-01 11:02:56,510 DEBUG    MainThread Automatic configuration of nodes disabled

I looked at the services and they all appear to be on.

emonpi_services

2024-05-01 11:02:49,484 DEBUG MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2024-05-01 11:02:51,486 WARNING MainThread Device communication error - check settings.

This is telling me it can’t communicate with the “emon” board that does the energy monitoring. It looks as if the baud rate is wrong - 38400 is an old setting, we now use 115200 baud.

On the emonhub page, click on “Edit config” and very near the top, you’ll see this:

[interfacers]
    ### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
    [[EmonPi2]]
        Type = EmonHubOEMInterfacer
        [[[init_settings]]]
            com_port = /dev/ttyAMA0
            com_baud = 115200
        [[[runtimesettings]]]
            pubchannels = ToEmonCMS,
            subchannels = ToRFM12,

I don’t know the age of your emonPi - in the [interfacers] section, try changing the baud rate to 115200, save the file and watch for that error as emonHub restarts. If it reappears, both 9600 and 57600 have been used in the past, so try those in turn.

My Interfacers section looked like this:

[interfacers]
### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
[[RFM2Pi]]
    Type = EmonHubJeeInterfacer
    [[[init_settings]]]
        com_port = /dev/ttyAMA0
        com_baud = 38400                        # 9600 for old RFM12Pi
      
    [[[runtimesettings]]]
        pubchannels = ToEmonCMS,
        subchannels = ToRFM12,

        group = 210
        frequency = 433
        baseid = 5                              # emonPi / emonBase nodeID
        calibration = 230V                      # (UK/EU: 230V, US: 110V)
        quiet = true                            # Disable quite mode (default enabled) to enable RF packet debugging, show packets which fail crc
        # interval =  300                         # Interval to transmit time to emonGLCD (seconds)

The only baud rate setting is for EmonHubJeeInterfacer so I tried changing that but none of the values worked:

2024-05-01 22:58:57,961 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 9600 bits/s
2024-05-01 22:58:59,964 WARNING  MainThread Device communication error - check settings
2024-05-01 22:59:37,931 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 115200 bits/s
2024-05-01 22:59:39,934 WARNING  MainThread Device communication error - check settings
2024-05-01 23:00:17,909 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 57600 bits/s
2024-05-01 23:00:19,911 WARNING  MainThread Device communication error - check settings

I bought and installed my emonpi around July 2022 if that helps? At least that is when the data started logging.

@TrystanLea @borpin Can either of you help here?

Hello @xylonsteve

Couple of things to try:

  1. Full power cycle, turn off the power for at ~10s.
    [Edit]
    DON’T just pull the plug, Do a controlled shutdown of the RPi via the Shutdown button on the Admin page or the pushbutton and menu on the emonPi.
    [ /Edit – RW]

  2. You could try updating the emonPi firmware via the local emoncms admin > update page. E.g:

Do you have any radio nodes, e.g emonTx3/4 or emonTh2?

I did a hard restart. There are some other errors in my log:

2024-05-02 16:09:05,068 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 57600 bits/s
2024-05-02 16:09:07,071 WARNING  MainThread Device communication error - check settings
2024-05-02 16:09:07,072 INFO     MainThread Setting RFM2Pi baseid: 5 (5i)
2024-05-02 16:09:08,074 INFO     MainThread Setting RFM2Pi frequency: 433 (4b)
2024-05-02 16:09:09,075 INFO     MainThread Setting RFM2Pi group: 210 (210g)
2024-05-02 16:09:10,077 INFO     MainThread Setting RFM2Pi quiet: 1 (1q)
2024-05-02 16:09:11,079 INFO     MainThread Setting RFM2Pi calibration: 230V (1p)
2024-05-02 16:09:12,081 DEBUG    MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2024-05-02 16:09:12,082 DEBUG    MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2024-05-02 16:09:12,083 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT'
2024-05-02 16:09:12,086 DEBUG    MainThread Setting MQTT pubchannels: ['ToRFM12']
2024-05-02 16:09:12,087 DEBUG    MainThread Setting MQTT subchannels: ['ToEmonCMS']
2024-05-02 16:09:12,087 INFO     MainThread Setting MQTT node_format_enable: 1
2024-05-02 16:09:12,087 INFO     MainThread Setting MQTT nodevar_format_enable: 1
2024-05-02 16:09:12,088 INFO     MainThread Setting MQTT nodevar_format_basetopic: emon/
2024-05-02 16:09:12,088 INFO     MainThread Setting MQTT node_JSON_enable: 0
2024-05-02 16:09:12,089 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
2024-05-02 16:09:12,091 DEBUG    MainThread Setting emoncmsorg pubchannels: ['ToRFM12']
2024-05-02 16:09:12,092 DEBUG    MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2024-05-02 16:09:12,092 WARNING  MainThread Setting emoncmsorg apikey: obscured
2024-05-02 16:09:12,093 INFO     MainThread Setting emoncmsorg url: https://emoncms.org
2024-05-02 16:09:12,093 INFO     MainThread Setting emoncmsorg senddata: 1
2024-05-02 16:09:12,093 INFO     MainThread Setting emoncmsorg sendstatus: 1
2024-05-02 16:09:12,094 INFO     MainThread Setting emoncmsorg sendnames: 0
2024-05-02 16:09:12,094 INFO     MainThread Setting emoncmsorg compress: 0
2024-05-02 16:09:12,095 DEBUG    MainThread Automatic configuration of nodes disabled
2024-05-03 10:13:44,965 INFO     MainThread Deleting interfacer 'RFM2Pi'
2024-05-03 10:13:44,966 INFO     MainThread Creating EmonHubJeeInterfacer 'RFM2Pi'
2024-05-03 10:13:44,966 ERROR    MainThread Unable to create 'RFM2Pi' interfacer: __init__() got an unexpected keyword argument 'orig: com_baud'
2024-05-03 10:13:44,967 INFO     MainThread Setting emoncmsorg senddata: 1
2024-05-03 10:13:44,968 INFO     MainThread Setting emoncmsorg sendstatus: 1

I have no radios etc.

I have updated the firmware too and it doesn’t seem to make any difference.

Can I just re-install everything? How would I do that? I can get a fresh SD card and start again.

Is there any way to copy across my old data?

Hello @xylonsteve, looks like this is the error tripping it up:

When creating the EmonHubJeeInterfacer RFM2Pi interfacer.

Could you share a copy of your emonhub.conf file, Available from EmonHub > Edit config:

#######################################################################
#######################      emonhub.conf     #########################
#######################################################################
### emonHub configuration file, for info see documentation:
### https://github.com/openenergymonitor/emonhub/blob/emon-pi/configuration.md
#######################################################################
#######################    emonHub  settings    #######################
#######################################################################

[hub]
### loglevel must be one of DEBUG, INFO, WARNING, ERROR, and CRITICAL
loglevel = DEBUG
### Uncomment this to also send to syslog
# use_syslog = yes
#######################################################################
#######################       Interfacers       #######################
#######################################################################

[interfacers]
### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
[[RFM2Pi]]
    Type = EmonHubJeeInterfacer
    [[[init_settings]]]
        com_port = /dev/ttyAMA0
        orig: com_baud = 38400                        # 9600 for old RFM12Pi
        # com_baud = 57600
      
    [[[runtimesettings]]]
        pubchannels = ToEmonCMS,
        subchannels = ToRFM12,

        group = 210
        frequency = 433
        baseid = 5                              # emonPi / emonBase nodeID
        calibration = 230V                      # (UK/EU: 230V, US: 110V)
        quiet = true                            # Disable quite mode (default enabled) to enable RF packet debugging, show packets which fail crc
        # interval =  300                         # Interval to transmit time to emonGLCD (seconds)


[[MQTT]]

    Type = EmonHubMqttInterfacer
    [[[init_settings]]]
        mqtt_host = 127.0.0.1
        mqtt_port = 1883
        mqtt_user = emonpi
        mqtt_passwd = emonpimqtt2016

    [[[runtimesettings]]]
        pubchannels = ToRFM12,
        subchannels = ToEmonCMS,

        # emonhub/rx/10/values format
        # Use with emoncms Nodes module
        node_format_enable = 1
        node_format_basetopic = emonhub/

        # emon/emontx/power1 format - use with Emoncms MQTT input
        # http://github.com/emoncms/emoncms/blob/master/docs/RaspberryPi/MQTT.md
        nodevar_format_enable = 1
        nodevar_format_basetopic = emon/

        # Single JSON payload published  - use with Emoncms MQTT
        node_JSON_enable = 0
        node_JSON_basetopic = emon/

[[emoncmsorg]]
    Type = EmonHubEmoncmsHTTPInterfacer
    [[[init_settings]]]
    [[[runtimesettings]]]
        pubchannels = ToRFM12,
        subchannels = ToEmonCMS,
        url = https://emoncms.org
        apikey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        senddata = 1                    # Enable sending data to Emoncms.org
        sendstatus = 1                  # Enable sending WAN IP to Emoncms.org MyIP > https://emoncms.org/myip/list
        sendinterval= 30                # Bulk send interval to Emoncms.org in seconds

#######################################################################
#######################          Nodes          #######################
#######################################################################

[nodes]

## See config user guide: https://github.com/openenergymonitor/emonhub/blob/emon-pi/conf/emonhub.conf

[[5]]
    nodename = emonpi
    [[[rx]]]
        names = power1,power2,power1pluspower2,vrms,t1,t2,t3,t4,t5,t6,pulsecount
        datacodes = h, h, h, h, h, h, h, h, h, h, L
        scales = 1,1,1,0.01,0.1,0.1,0.1,0.1,0.1,0.1,1
        units = W,W,W,V,C,C,C,C,C,C,p

[[6]]
    nodename = emontxshield
    [[[rx]]]
       names = power1, power2, power3, power4, vrms
       datacode = h
       scales = 1,1,1,1,0.01
       units = W,W,W,W,V

[[7]]
   nodename = emontx4
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units = W,W,W,W,V,C,C,C,C,C,C,p

[[8]]
    nodename = emontx3
    [[[rx]]]
       names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[9]]
   nodename = emontx2
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units = W,W,W,W,V,C,C,C,C,C,C,p

[[10]]
    nodename = emontx1
    [[[rx]]]
       names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[11]]
    nodename = 3phase
    [[[rx]]]
       names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[12]]
    nodename = 3phase2
    [[[rx]]]
       names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[13]]
    nodename = 3phase3
    [[[rx]]]
       names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[14]]
    nodename = 3phase4
    [[[rx]]]
       names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
       datacodes = h,h,h,h,h,h,h,h,h,h,h,L
       scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
       units = W,W,W,W,V,C,C,C,C,C,C,p

[[15]]
    nodename = emontx3cm15
    [[[rx]]]
       names = MSG, Vrms, P1, P2, P3, P4, E1, E2, E3, E4, T1, T2, T3, pulse
       datacodes = L,h,h,h,h,h,l,l,l,l,h,h,h,L
       scales = 1,0.01,1,1,1,1,1,1,1,1,0.01,0.01,0.01,1
       units = n,V,W,W,W,W,Wh,Wh,Wh,Wh,C,C,C,p
       whitening = 1

[[16]]
    nodename = emontx3cm16
    [[[rx]]]
       names = MSG, Vrms, P1, P2, P3, P4, E1, E2, E3, E4, T1, T2, T3, pulse
       datacodes = L,h,h,h,h,h,l,l,l,l,h,h,h,L
       scales = 1,0.01,1,1,1,1,1,1,1,1,0.01,0.01,0.01,1
       units = n,V,W,W,W,W,Wh,Wh,Wh,Wh,C,C,C,p
       whitening = 1

[[19]]
   nodename = emonth1
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[20]]
   nodename = emonth2
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[21]]
   nodename = emonth3
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[22]]
   nodename = emonth4
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[23]]
    nodename = emonth5
    [[[rx]]]
       names = temperature, external temperature, humidity, battery, pulsecount
       datacodes = h,h,h,h,L
       scales = 0.1,0.1,0.1,0.1,1
       units = C,C,%,V,p

[[24]]
    nodename = emonth6
    [[[rx]]]
       names = temperature, external temperature, humidity, battery, pulsecount
       datacodes = h,h,h,h,L
       scales = 0.1,0.1,0.1,0.1,1
       units = C,C,%,V,p

[[25]]
    nodename = emonth7
    [[[rx]]]
       names = temperature, external temperature, humidity, battery, pulsecount
       datacodes = h,h,h,h,L
       scales = 0.1,0.1,0.1,0.1,1
       units = C,C,%,V,p

[[26]]
    nodename = emonth8
    [[[rx]]]
       names = temperature, external temperature, humidity, battery, pulsecount
       datacodes = h,h,h,h,L
       scales = 0.1,0.1,0.1,0.1,1
       units = C,C,%,V,p

That’s not legal. Delete it so that the line reads

com_baud = 38400 # 9600 for old RFM12Pi # com_baud = 57600

A comment, ignored by emonHub, is anything following a ‘#’ character. If you want to keep a note in there to say what it was, adding orig com_baud = 38400 after the ‘#’ on the present line, or separately on a new line, is OK.
# orig: com_baud = 38400 is fine - it will be ignored.

Well that is embarrassing! I have copy+pasted this config so many times, I can’t believe that was it!

Thank you so much - it seems to be working now.

2 Likes

You need to look where you copied it from - before you do the same again :face_with_hand_over_mouth:

1 Like

Honestly it’s really embarrassing because I am actually a programmer and I write this kind of stuff all of the time!

I think what happened was I had that line commented out, and then I got confused and uncommented it and commented the next line instead. I updated that file loads of times trying different baud rates.

I think it shows how much I rely on syntax highlighting! I should really just set up my SSH key and log in and use vim.

2 Likes

I think it’s much more likely that to a fresh pair of eyes, it stood out like a sore thumb, whereas you’d seen it so many times it was familiar.

I know I can’t proof-read something I’ve written for at least 3 days, otherwise I read what I wanted to write and not what’s actually on the screen. Strangely, a different font helps in this case. :thinking: