General TCP use?

[MikeMatthews]

Below is a snip from the log, showing the offending conversion which should be about 73 instead of 7.3.

8/19/2021 9:15:31 PM 24906 | DecodeWMP Received CHN,1:AMBTEMP,227

8/19/2021 9:15:31 PM 24918 | Update Accepted 218 to 7.3 StatusType=2 Payload=7.3 RegExValue=7.3
8/19/2021 9:15:31 PM 24920 | Updating Device from 7.3 PayloadNumeric=True
8/19/2021 9:15:31 PM 24921 | ActOnMessageForTrigger QueueSize=0 ,Topic Daikin/10.0.0.100,Payload {"InsideTemp":"7.3"}

I should confess that I tried out the new IntesisWMP plugin to see what that was about. I didn't have that and mcsMQTT running simultaneously, and the log above is even after I uninstalled the other plugin. As a check, I also loaded the Intesis config tool to see if the somehow another setting was present (it allows for a temp offset of a few degrees F). All of that looks fine. I only mention it here for completeness.

[MikeMatthews]

I added an expression so my scripts work properly again. BTW, the hover help over the expression field has the syntax wrong I think. It should be $$PAYLOAD: but the hover help doesn't have the colon.

UPDATE: By multiplying the payload by 10, I lose precision in the temperatures now (no fractional degrees).

[Michael McSharry]

I found the problem and some other cleanup that should be transparent to you now that HS devices have already been created

HS4 plugin update at http://mcsSprinklers.com/MCSMQTTHS4_51811.zip. TCP.html update is optional as it only adds the JSON tab.

[MikeMatthews]

Thanks! It seems to be working.

[MikeMatthews]

There seems to be another issue that occurs at HS startup. The features Mode and SetTemp are both set to zero in the HS device value. In the mcsMQTT associations tab, the values are shown correctly as Cool and 80.1 respectively (which are the actual values at the controller).
A consequence of this is that if I try to set the mode to Cool in HS, nothing happens. I must set the mode to something else, then back to Cool in order that HS has the proper device value. Likewise if I set settemp to 80, the HS value remains zero.

Below is the log at startup. It makes me wonder: Why is there no DecodeWMP for the various queries sent, apparently for the purpose of reading the current state? Maybe that's a red herring, just seems odd.

8/21/2021 8:04:24 AM 6644 | SetIOMulti DaikinDictionary.Count 0, Source=Daikin/10.0.0.100:Power to IP 10.0.0.100, Command Power, inDictionary=False
8/21/2021 8:04:24 AM 6651 | Publish Daikin/10.0.0.100/set=On
8/21/2021 8:04:24 AM 6651 | Background Init Beacon Enable = 0
8/21/2021 8:04:24 AM 6651 | mcsMQTT Debug Background Init 8
8/21/2021 8:04:24 AM 6696 | HSEvent VALUE_CHANGE| 1024| 10.0.0.100| 0| 3| 209
8/21/2021 8:04:24 AM 6696 | 209 has been blacklisted from event callbacks
8/21/2021 8:04:24 AM 6705 | HSEvent VALUE_SET| 2048| 10.0.0.100| 0| 0| 210
8/21/2021 8:04:24 AM 6706 | 210 has been blacklisted from event callbacks
8/21/2021 8:04:24 AM 6708 | HSEvent VALUE_CHANGE| 1024| 10.0.0.100| 0| 80| 211
8/21/2021 8:04:24 AM 6709 | 211 has been blacklisted from event callbacks
8/21/2021 8:04:24 AM 6709 | HSEvent VALUE_SET| 2048| 10.0.0.100| 0| 0| 213
8/21/2021 8:04:24 AM 6709 | 213 has been blacklisted from event callbacks
8/21/2021 8:04:24 AM 6710 | HSEvent VALUE_CHANGE| 1024| 10.0.0.100| 0| 71.6| 218
8/21/2021 8:04:24 AM 6710 | 218 has been blacklisted from event callbacks
8/21/2021 8:04:24 AM 6886 | mcsMQTT Debug Background Init Done
8/21/2021 8:04:24 AM 6919 | Daikin/Intesis Started
8/21/2021 8:04:25 AM 7866 | Send: ID\r\n QueueDept=8 Connected=True
8/21/2021 8:04:25 AM 7868 | SentWMP ID

8/21/2021 8:04:25 AM 7869 | Send: INFO\r\n QueueDept=7 Connected=True
8/21/2021 8:04:25 AM 7869 | SentWMP INFO

8/21/2021 8:04:25 AM 7869 | Send: GET,1:ONOFF\r\n QueueDept=6 Connected=True
8/21/2021 8:04:25 AM 7869 | SentWMP GET,1:ONOFF

8/21/2021 8:04:25 AM 7870 | Send: GET,1:MODE\r\n QueueDept=5 Connected=True
8/21/2021 8:04:25 AM 7870 | SentWMP GET,1:MODE

8/21/2021 8:04:25 AM 7870 | Send: GET,1:SETPTEMP\r\n QueueDept=4 Connected=True
8/21/2021 8:04:25 AM 7870 | SentWMP GET,1:SETPTEMP

8/21/2021 8:04:25 AM 7870 | Send: GET,1:FANSP\r\n QueueDept=3 Connected=True
8/21/2021 8:04:25 AM 7870 | SentWMP GET,1:FANSP

8/21/2021 8:04:25 AM 7870 | Send: GET,1:VANEUD\r\n QueueDept=2 Connected=True
8/21/2021 8:04:25 AM 7870 | SentWMP GET,1:VANEUD

8/21/2021 8:04:25 AM 7871 | Send: GET,1:VANELR\r\n QueueDept=1 Connected=True
8/21/2021 8:04:25 AM 7871 | SentWMP GET,1:VANELR

8/21/2021 8:04:25 AM 7871 | Send: GET,1:AMBTEMP\r\n QueueDept=0 Connected=True
8/21/2021 8:04:25 AM 7871 | SentWMP GET,1:AMBTEMP

8/21/2021 8:04:25 AM 7896 | DecodeWMP Received IDK-RC-WMP-1,CC3F1D0247DC,10.0.0.100,ASCII,v1.3.3,-49,WMP_0247DC,N,3

8/21/2021 8:04:25 AM 7944 | DecodeWMP Received INFO:APPVERSION,1.0.0.1
INFO:RUNVERSION,1.3.3
INFO:CFGVERSION,1.2.3
INFO:WLANVERSION,2.0.0
INFOEVICEINFO,00080051FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
INFO:HASH,0801:0100

[mminehan]

There seems to be another issue that occurs at HS startup. The features Mode and SetTemp are both set to zero in the HS device value.

Yes.....I have the same issue.

I think that the Intesis system does not broadcast at a set interval, only if there wall controller has been changed. Each Intesis value/device has to be manually queried individually in order to get the correct values.

And like you say, for example, if the Intesis is in heat mode and HS is rebooted then the mode device and set temp in HS are set to off and 0 respectively.

It is as if the "GET" commands in the log you posted are not updating the HS devices on startup.......if that makes sense.

Maybe polling the devices at a set interval might help?

M

[Michael McSharry]

The plugin initializes the internal Intesis device states at startup based upon the HS DeviceValues. Problem was that this was not done early enough. It is fixed in 5.18.2.1

HS4: http://mcsSprinklers.com/MCSMQTTHS4_51821.zip
HS3: http://mcsSprinklers.com/MCSMQTT_51821.zip

[MikeMatthews]

This is working on HS4. Thanks!

[mminehan]

The plugin initializes the internal Intesis device states at startup based upon the HS DeviceValues. Problem was that this was not done early enough. It is fixed in 5.18.2.1

Brilliant. Works perfectly. Thanks again for your responsiveness.

Marty

[Techn0]

Is this Plugin one i could look into to control some AC units, Mitsubishi Heavy Industries, controlled with a 3rd party controller AIRCONWITHME, from INTESIS,

https://cdn.hms-networks.com/docs/li...rsn=339b5cd7_6

[Michael McSharry]

Yes it should work.

[mminehan]

Is this Plugin one i could look into to control some AC units, Mitsubishi Heavy Industries, controlled with a 3rd party controller AIRCONWITHME, from INTESIS,

https://cdn.hms-networks.com/docs/li...rsn=339b5cd7_6

If it uses the WMP protocol (like the link you provided) then it should work. But be warned, the Intesis interfaces are not cheap!