Announcement

Collapse
No announcement yet.

Thermostat via mqtt?

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

    #46
    Originally posted by Michael McSharry View Post
    Use like the following in browser. Remove the Data from the middle.

    Code:
    http://192.168.178.60/aircon/set_control_info?pow=1&mode=6&stemp=16&shum=50&f_rate=3&f_dir=3
    This is working:
    mode7= auto
    mode6= fan
    mode5= heat
    mode4= heat
    mode3= cool
    mode2= fan
    mode1= cool
    mode0= cool

    Comment


      #47
      I should everything I need to finish it except confirmation of what value is used to change the mode to Fan. 6 is suppose to do it.

      Temperatures have mode-dependent limits, but should not generally change when mode changes if reasonable values are used. I will confirm the logic is working as intended for this.

      Comment


        #48
        The update is at http://mcsSprinklers.com/mcsMQTT_5_2_1_13.zip

        I believe it should be fully functional. Let me know of any issues. There was a difference between my two sources for Fan speed. This is one you should fully test.

        This update requires the HS Daikin devices to be recreated. The easiest method is to go to the General tab, Inbound Management section and enter Daikin/# in the textbox of the Obsolete row. After doing this you can look at HS Device Management to assure the device were deleted.

        When the Daikin unit(s) is first polled it will create new devices.

        The setpoint is reported by Daikin as "--" when the unit is off. This will show up as -99 in HS.

        Comment


          #49
          New testresults:
          Using "http://192.168.178.60/aircon/set_control_info?pow=1&mode=6&stemp=16&shum=50&f_rate=3&f_dir=3", I fond out the parameters for fan-level (f_rate)
          f_rate=3 is level 1
          f_rate=4 is level 2
          f_rate=5 is level 3
          f_rate=6 is level 4
          f_rate=7 is level 5
          f_rate=8 or higher is param ng
          I havent found out the variables for the quiet- or auto-mode.

          Fan-rates "auto" and "quiet" are not working.

          The plugin doesnt display fan-level 1, even if the unit accepts the command.

          The plugin doesnt display mode "fan" (unit accepts it)

          The plugind doesnt display "Off" (after unit has been turned on and off). Only after I recreated the devices (and didnt turn them on) they are listed as "Off).

          debug-file:
          - turned unit on (mode=cool, fan-level=3)
          - fan level =1 (unit turns to level 1, but plugin remains on the last level)
          - fan-level = quiet (both unit and plugin dont change state)
          - fan-level = auto (both unit and plugin dont change state)
          - mode = fan (unit turns to fan, but plugin remains on the last mode)
          - turned unit off (unit turns off, but plugin still displays "On")
          Attached Files

          Comment


            #50
            Good set of debug and test cases. Analysis for record below, but the bottom line is that everything should now be working with http://mcsSprinklers.com/mcsMQTT_5_2_1_14.zip
            Fan Auto should be "A" and Quiet should be "B" for f_rate. That is now what I have implemented.

            The power ON transition takes a little time before the Daikin updates its status. The polling interval is 15 seconds for status updates so there will be some delay to see this in HS. The other changes are reflected immediately.


            Code:
            - fan level =1 (unit turns to level 1, but plugin remains on the last level)  level commanded to F1 (3), status return F1 (3) ... why didnt plugin update Fan from 5 F3 to 3 F1?
            ----------------------------------------------------------------------------
            03.04.2020 16:43:17    5825113    | Daikin SubGet Return ret=OK,pow=0,mode=3,adv=,stemp=25.0,shum=50,f_rate=5,f_dir=3  
            
            03.04.2020 16:43:46    5854834    | SetIOMulti DaikinDictionary.Count 4, Source=Daikin/192.168.178.60:Fan  
            03.04.2020 16:43:46    5854834    | Daikin SubGet URL http://192.168.178.60/aircon/set_control_info?pow=1&mode=3&stemp=25&shum=50&f_rate=3&f_dir=3  
            03.04.2020 16:43:47    5855591    | Daikin SubGet Return ret=OK,pow=1,mode=3,adv=,stemp=25.0,shum=50,f_rate=3,f_dir=3
            
            
            - fan-level = quiet (both unit and plugin dont change state) level commanded to NONE (2), status returned NONE ... why was NONE (2) rather than QUIET (B/1) commanded 
            ------------------------------------------------------------
            03.04.2020 16:44:24    5892104    | SetIOMulti DaikinDictionary.Count 4, Source=Daikin/192.168.178.60:Fan  
            03.04.2020 16:44:24    5892104    | Daikin SubGet URL http://192.168.178.60/aircon/set_control_info?pow=1&mode=3&stemp=25&shum=50&f_rate=2&f_dir=3  
            03.04.2020 16:44:24    5892837    | Daikin SubGet Return ret=OK,pow=0,mode=6,adv=,stemp=--,shum=--,f_rate=3,f_dir=0  
            
                                    10 seconds later Daikin reports Power ON, Mode COOL, Fan F1
            03.04.2020 16:44:33    5901353    | Daikin SubGet Return ret=OK,pow=1,mode=3,adv=,stemp=25.0,shum=50,f_rate=3,f_dir=3  
            
            
            
            - fan-level = auto (both unit and plugin dont change state) level commanded to NONE (2), Daikin did not accept command, next status is Fan 3 (F1) 
            ------------------------------------------------------------
            03.04.2020 16:44:52    5920775    | SetIOMulti DaikinDictionary.Count 4, Source=Daikin/192.168.178.60:Fan  
            03.04.2020 16:44:52    5920775    | Daikin SubGet URL http://192.168.178.60/aircon/set_control_info?pow=1&mode=3&stemp=25&shum=50&f_rate=2&f_dir=3  
            03.04.2020 16:44:52    5920883    | Daikin SubGet Return ret=PARAM NG 
            03.04.2020 16:45:03    5931808    | Daikin SubGet Return ret=OK,pow=1,mode=3,adv=,stemp=25.0,shum=50,f_rate=3,f_dir=3  
            
            
            - mode = fan (unit turns to fan, but plugin remains on the last mode)  plugin commands ON fan F1 (3) and HORR/VERT ... why didnt plugin update mode from 3 (COOL) to 6 (FAN), why did Daiken Power=OFF
            ---------------------------------------------------------------------
            03.04.2020 16:45:14    5942808    | SetIOMulti DaikinDictionary.Count 4, Source=Daikin/192.168.178.60:Mode  
            03.04.2020 16:45:14    5942808    | Daikin SubGet URL http://192.168.178.60/aircon/set_control_info?pow=1&mode=6&stemp=25&shum=50&f_rate=3&f_dir=3  
            03.04.2020 16:45:14    5942839    | Daikin SubGet Return ret=OK,pow=0,mode=6,adv=,stemp=--,shum=--,f_rate=3,f_dir=0 
            
                                    5 seconds later Daiken reports Power 1 (ON)  Mode 6 (FAN) 
            03.04.2020 16:45:19    5947059    | Daikin SubGet Return ret=OK,pow=1,mode=6,adv=,stemp=--,shum=--,f_rate=3,f_dir=3  
            
            
            - turned unit off (unit turns off, but plugin still displays "On")  Daikin reports Power 0 (OFF) ... why didnt plugin update ON to OFF?
            ------------------------------------------------------------------
            03.04.2020 16:45:43    5971082    | Daikin SubGet URL http://192.168.178.60/aircon/set_control_info?pow=0&mode=6&stemp=10&shum=50&f_rate=3&f_dir=3  
            03.04.2020 16:45:43    5971193    | Daikin SubGet Return ret=OK,adv=  
            03.04.2020 16:45:49    5977541    | Daikin SubGet Return ret=OK,pow=0,mode=6,adv=,stemp=--,shum=--,f_rate=3,f_dir=3

            Comment


              #51
              Thank you so much!
              I think thats it.
              Controls all work fine now.
              The only little flaw is that the plugin deletes temperature and humidity as soon as I swich to mode = fan, but I think thats no barrier controling the units. The only thing I have to do, is always remember to set temperature and humidity when I turn the units on.
              ;-)

              Comment


                #52
                I changed the logic to ignore the "--" reporting of temp and humidity setpoints. This means that when the unit is powered it will be commanded to the same temp and humidity setpoints as when it was turned off. It should also allow new setpoints to be set prior to turning the unit on. The new setpoints will not be reflected in HS devices until the unit is turned on, but it will be visible because the HS text box will be the new setpoint and the HS device status will be the old one.

                http://mcsSprinklers.com/mcsMQTT_5_2_3_2.zip

                Comment


                  #53
                  I am about to buy a Daikin AC (FTXF25A) with wifi. I really know nothing about MQTT but willing to learn. Generally, to control these AC's via the PI, do I need any additional hardware or can I control the AC via the PI ? Thats with the assumption it uses the same commands as the ones implemented

                  Comment


                    #54
                    You need nothing else. mcsMQTT supports a generic MQTT protocol as well as protocols used for specific devices including the Daikin. Install the plugin, Select TCP Page from the plugin menu, enter the IP of the unit and HS devices will be created. Status and can control is available from HS.

                    If you happen to obtain a device that uses MQTT in the future then you will be all set with the same plugin.

                    Comment


                      #55
                      Ok great. The unit should be installed within the next couple of weeks, then I'll give the PI a go.

                      Comment


                        #56
                        Hello
                        I'm buying a Daikin air conditioner with internal piping distribution. I have this RTD-NET card that I attach. I will also use another card that allows RS485 / IP conversion. With this configuration, will it be possible to use this plugin (mcsMQTT) to manage air conditioning? Thanks
                        Massimo-RenderCAD
                        Attached Files

                        Comment


                          #57
                          I have never used MODBUS so doing a remote development using it would be difficult. While there are similarities between this interface and the interface of the Daikin units that are supported by mcsMQTT, they are sufficiently different that there is not much that could be shared. There is a MODBUS plugin that likely would be a closer match than mcsMQTT for controlling this unit.

                          Comment


                            #58
                            Originally posted by Michael McSharry View Post
                            I have never used MODBUS so doing a remote development using it would be difficult. While there are similarities between this interface and the interface of the Daikin units that are supported by mcsMQTT, they are sufficiently different that there is not much that could be shared. There is a MODBUS plugin that likely would be a closer match than mcsMQTT for controlling this unit.
                            Hello Michael
                            Thank you
                            I did not know the existence of the Modbus plugin, thanks again for the indication.
                            Massimo-RenderCAD

                            Comment

                            Working...
                            X