Announcement

Collapse
No announcement yet.

after installing 5.21.7.2 can't seem to receive any MQTT messages

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    after installing 5.21.7.2 can't seem to receive any MQTT messages

    installed 5.21.7.2 about 2 hours agoi, since, the plugin does not seem to receive MQTT message from the server

    I made sure the MQTT server is up and running and is receiving data from devices but if I select filter on devices, I don't see any of the changes coming from MQTT

    if I look in the log file I can see the devices changed:
    2021-12-10 15:25:28 964837 | ActOnMessageForTrigger QueueSize=0 ,Topic ESP_Pression_eau/pression/Analog,Payload 46
    but if I look at the device the value is still with a value fromn 2 hours ago

    Click image for larger version  Name:	aaa.JPG Views:	0 Size:	29.7 KB ID:	1513392

    Any idea what could be wrong ?

    #2
    You should be able to view the HS Device page that refreshes every second or so. It is about 10 seconds for the MQTT pages (to conserve CPU). MQTT pages also expire after 15 minutes or so if no user action taken on the page.

    Comment


      #3
      Originally posted by Michael McSharry View Post
      You should be able to view the HS Device page that refreshes every second or so. It is about 10 seconds for the MQTT pages (to conserve CPU). MQTT pages also expire after 15 minutes or so if no user action taken on the page.
      Michael McSharry in fact, the device value NEVER changes, if you look at the example I send ealier, the last change of HS device 1693 happend at 14:26:50 and there were change on the physical device at 15:25:28 but the payload (46) never made it to the HS1693 device who is staying at (52)

      If I look in the history database, filtering on the table "Received MQTT Topics" history and filtered by MQTT Topic "ESP_Pression_eau" there is no entry after 14:28 time at wich I installed the latest version

      Comment


        #4
        I picked a random message in my mcsMQTTDebug.txt file that shows the "ActOn..." receipt of message and the handling of its payload through "SetDeviceValueString...". You should have similar in our debug file but may not have the expression related lines unless you have an expression being evaluated before storing into HS device. Also look at the Edit tab for your topic and assure that the Control/Status UI is not Text and that the target property is DeviceValue and not DeviceString.
        Code:
        12/9/2021 1:25:08 PM 1146114 | ActOnMessageForTrigger QueueSize=24 ,Topic wled/100/status,Payload online
        12/9/2021 1:25:08 PM 1146146 | Update Accepted 4404 to 128 StatusType=11 Payload=128 RegExValue=128
        12/9/2021 1:25:08 PM 1146147 | Updating Device from 0 PayloadNumeric=True
        12/9/2021 1:25:08 PM 1146147 | PayloadSubstitution value 128, Payload 128, Expression $$PAYLOAD:*100/255
        12/9/2021 1:25:08 PM 1146148 | ApplyExpression 128*100/255 Result=50.1960784313725
        12/9/2021 1:25:08 PM 1146148 | SetDeviceValueString Number newValue 50.1960784313725, inputValue 128

        Comment


          #5
          Originally posted by Michael McSharry View Post
          I picked a random message in my mcsMQTTDebug.txt file that shows the "ActOn..." receipt of message and the handling of its payload through "SetDeviceValueString...". You should have similar in our debug file but may not have the expression related lines unless you have an expression being evaluated before storing into HS device. Also look at the Edit tab for your topic and assure that the Control/Status UI is not Text and that the target property is DeviceValue and not DeviceString.
          Code:
          12/9/2021 1:25:08 PM 1146114 | ActOnMessageForTrigger QueueSize=24 ,Topic wled/100/status,Payload online
          12/9/2021 1:25:08 PM 1146146 | Update Accepted 4404 to 128 StatusType=11 Payload=128 RegExValue=128
          12/9/2021 1:25:08 PM 1146147 | Updating Device from 0 PayloadNumeric=True
          12/9/2021 1:25:08 PM 1146147 | PayloadSubstitution value 128, Payload 128, Expression $$PAYLOAD:*100/255
          12/9/2021 1:25:08 PM 1146148 | ApplyExpression 128*100/255 Result=50.1960784313725
          12/9/2021 1:25:08 PM 1146148 | SetDeviceValueString Number newValue 50.1960784313725, inputValue 128
          these are the only two lines I have
          2021-12-10 17:13:50 2954213 | ActOnMessageForTrigger QueueSize=0 ,Topic ESP_Pression_eau/pression/Analog,Payload 46
          2021-12-10 17:13:51 2954854 | HSEvent VALUE_CHANGE| 1024| | 93| 92| 205

          What I don't understand is that I am having this updating issue with only 4 devices. There was no changes done to thoses devices for months and I know they were working prior the update because if I don't receive a "wake-up" every 30 minutes i receive a Pushover notification for those 4 devices, in fact, this is how I found out the issue, I received 4 notifications 30 minutes after updating the plugin saying that thoses devices were offline !

          Looking at the devices, the only difference I can see is with the topic, those 4 devices start with a "/":
          /ESP_Pression_eau/pression/Analog
          /ESP_Puit/Temp/Temperature
          /ESP_Frigidaire/Congelateur_ssol/Temperature
          /ESP_Arrosage/MQTT/Valve1

          Looking at the history I can see that the topic included the "/" :
          194 S 2021-12-10 14:28:42 /ESP_Pression_eau/pression/Analog 52
          But if I look at the associations page and filter table by "include received MQTT messages" only, I see that now entries are coming in without the "/":

          exemple "ESP_Frigidaire/Congelateur_ssol/Temperature"

          This tells me that there have been a change somewhere in the way topics are handled

          Comment


            #6
            You are correct that the leading slash is removed so the first part of the topic will not be null. In the Association table you should have the set of topics shown without the leading slash. Enter the ref number of the older topics so that either topic is associated with the same HS device.

            Comment


              #7
              Thanks Michael McSharry , I decided to fix the issue at device level, I have change the topic to remove the first / and recreated the devices in HS4, I only has 5 devices to rebuild, that keeps a clean system...

              Comment

              Working...
              X