Announcement

Collapse
No announcement yet.

History with InfluxDB not working

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    History with InfluxDB not working

    I'm working on getting InfluxDB integration working. I have existing Grafana and InfluxDB Docker containers running, so that part was easy. I selected a single HS device (outdoor temperature) and checked the "i" column. When I went to the History page, I didn't see anything when I clicked "Show Selected InfluxDB Device History", so to get more information I also checked the "d" column to see if any value change were occurring.

    I am seeing records written to SQLite, but not to InfluxDB. The database I specified at the top of the History page did get created on my InfluxDB server, so it seems that there are no permission issues. There are no messages in the log relating to this. Any suggestions on how to troubleshoot?
    Tags: None
    #2
    I added debug at the HSEvent notification and at the Influx Write in the attached. Enable debug from top of the General Tab. Debug file will be at \data\mcsMQTT\mcsMQTT Debug.txt. Post of email the debug file.
    Attached Files

    Comment

      #3
      That provided more information, although I don't know why the 404 is happening. I'm running a fairly old version of InfluxDB (1.2). Maybe that's the issue? I am going to upgrade (or perhaps build a new VM) soon anyway.

      Code:
      5/30/2021 4:45:55 PM 128544 | InfluxDB Write URI http://192.168.59.9:8086/api/v2/write?bucket=hs2&orgID=homeseer body mcsMQTT,device=Main_Deck_Outdoor\ Temperature value=81
5/30/2021 4:45:55 PM 128545 | InfluxDB Write After postStream
5/30/2021 4:45:55 PM 128584 | InfluxDB Write Finally no Response The remote server returned an error: (404) Not Found.
5/30/2021 4:45:55 PM 128584 | InfluxDB Write Finally The remote server returned an error: (404) Not Found., Queue Depth =0

      Comment

        #4
        Only tested with 1.8 and 2.0. There was another user with 1.7 and the update to 1.8 allowed it to work with the APIs being used by mcsMQTT.

        Comment

          #5
          Ok - I'm fine with that answer. It will get me to upgrade sooner. 😉

          Comment

            #6
            I upgraded to 1.8.6, and I'm getting records now. However, I'm seeing another odd issue that I'll put in another topic.

            Comment

            Previous template Next
            Working...
            X