Yes to both. LIMITS on initialisation and keep alive every 45 sec.
1 Like
Hi guys. I have got an MH-AC-WIFI-1 IntesisHome adapter which came with my new Mitsubishi Heavy SRK20ZS-S split unit, and I’ve found that it has affordable local REST API apart from cloud connection.
You can get endpoints description by GET on http://address/js/data/data.json
Response:
{
“api”:{
“url”:{
“getinfo” : “/js/api/getconfig.json”,
“login” : “/js/api/login.json”,
“logout” : “/js/api/logout.json”,
“update_password” : “/js/api/update_password.json”,
“getavailabledatapoints”: “/js/api/getavailabledatapoints.json”,
“getdatapointvalue” : “/js/api/getdatapointvalue.json”,
“setdatapointvalue” : “/js/api/setdatapointvalue.json”,
“getcurrentconfig” : “/js/api/getcurrentconfig.json”,
“identify” : “/js/api/identify.json”,
“wpsstart” : “/js/api/wpsstart.json”,
“getaplist” : “/js/api/getaplist.json”,
“setdefaults” : “/js/api/setdefaults.json”,
“setconfig” : “/js/api/setconfig.json”,
“reboot” : “/js/api/reboot.json”,
“getavailableservices” : “/js/api/getavailableservices.json”
},
“error”:{
“0”:“Undefined error”,
“1”:“Login Required.”,
“2”:“Write Error”,
“3”:“Read Error”,
“4”:“Malformed Command”,
“5”:“Incorrect User name or password”,
“6”:“Current password is incorrect”,
“7”:“Out of range”,
“8”:“Invalid datapoint”,
“9”:“Internal error”,
“10”:“General error”
}
},
“info”:{
“deviceModel”:“Device Model”,
“fwVersion”:“Device Firmware Version”,
“wlanFwVersion”:“Wireless Firmware Version”,
“sn”:“Serial Number”,
“wlanSTAMAC”:“Device Client MAC Address”,
“ssid”:“Wireless Network SSID”,
“wlanLNK”:“Connection Status with Wireless Network”,
“rssi”:“Wireless Signal Strength”,
“wlanAPMAC”:“Device Access Point MAC Address”,
“ownSSID”:“Device Access Point SSID”,
“tcpServerLNK”:“Cloud Server Connection”,
“acStatus”:“Air Conditioner Communication Status”,
“lastconfigdatetime”:“Last Configuration”,
“localdatetime”:“Local Date Time”
},
“types”:{
“int”:0,
“enum”:1,
“temp”:2
},
“acStatus”:{
“0”:“Ok”,
“1”:“Indoor Unit Error”,
“2”:“Communication Error”
},
“lastError”:{
“0”:“No error”,
“1”:“Wrong SSID introduced in the last configuration attempt”,
“2”:“Unsuccessful connection with the Access Point or router, check the password or the security mode selected”,
“3”:“Wrong IP configuration introduced or Internet connection problem in your network”,
“4”:“Your Access Point might be a captive portal. This type of network is not supported”,
“7”:“WPS failed. Try it again or configure your device by using the automatic or manual mode”
},
“wifiConfig”:{
“securityType”: {
“0”:“Open”,
“1”:“WEP”,
“2”:“WPA_PSK”,
“3”:“WPA2_PSK”,
“4”:“WPA_WPA2_PSK”,
“5”:“WPA2_Enterprise”
},
“levelText”:{
“0”:“Low”,
“1”:“Acceptable”,
“2”:“Good”,
“3”:“Very Good”,
“4”:“Excelent”
}
},
“signals”:{
“uid”:{
“1”: [“On/Off”, “TEXT_VALUES_ONOFF”, “”],
“2”: [“User Mode”, “TEXT_VALUES_MODES”, “”],
“4”: [“Fan Speed”, “TEXT_VALUES_FANSPEED”, “”],
“5”: [“Vane Up/Down Position”, “TEXT_VALUES_VANES”, “”],
“6”: [“Vane Left/Right Position”, “TEXT_VALUES_VANES”, “”],
“9”: [“User Setpoint”, {}, “°C”],
“10”: [“Return Path Temperature”, {}, “°C”],
“12”: [“Remote Disable”, “TEXT_VALUES_REMOTE”, “”],
“13”: [“On Time”, {}, “h”],
“14”: [“Alarm Status”, “TEXT_VALUES_ONOFF”, “”],
“15”: [“Error Code”, {}, “”],
“34”: [“Quiet Mode”, “TEXT_VALUES_ONOFF”, “”],
“35”: [“Min Temperature Setpoint”, {}, “°C”],
“36”: [“Max Temperature Setpoint”, {}, “°C”],
“37”: [“Outdoor Temperature”, {}, “°C”],
“60”: [“Heat 8/10ºC”, “TEXT_VALUES_ONOFF”, “”],
“61”: [“cfg Mode Map”, {}, “”],
“62”: [“cfg Mode Restrict”, {}, “”],
“63”: [“cfg Horizontal Vanes”, {}, “”],
“64”: [“cfg Vertical Vanes”, {}, “”],
“65”: [“cfg Quiet mode”, {}, “”],
“66”: [“cfg Confirmation On/Off”, {}, “”],
“67”: [“cfg Fan Map Speed”, {}, “”],
“68”: [“Instant Power Consumption”, {}, “W”],
“69”: [“Accumulated Power Consumption”, {}, “Wh”],
“181”: [“Maintenance time”, {}, “h”],
“182”: [“Maintenance config”, {}, “h”],
“183”: [“Maintenance Filter time”, {}, “h”],
“184”: [“Maintenance Filter config”, {}, “h”]
},
“uidTextvalues”:{
“TEXT_VALUES_ONOFF”: {
“0”:“Off”,
“1”:“On”
},
“TEXT_VALUES_MODES”: {
“0”:“Auto”,
“1”:“Heat”,
“2”:“Dry”,
“3”:“Fan”,
“4”:“Cool”
},
“TEXT_VALUES_FANSPEED”: {
“0”:“Auto”,
“1”:“Speed 1”,
“2”:“Speed 2”,
“3”:“Speed 3”,
“4”:“Speed 4”,
“5”:“Speed 5”,
“6”:“Speed 6”,
“7”:“Speed 7”,
“8”:“Speed 8”,
“9”:“Speed 9”,
“10”:“Speed 10”
},
“TEXT_VALUES_VANES”: {
“0”:“Auto”,
“1”:“Position 1”,
“2”:“Position 2”,
“3”:“Position 3”,
“4”:“Position 4”,
“5”:“Position 5”,
“6”:“Position 6”,
“7”:“Position 7”,
“8”:“Position 8”,
“9”:“Position 9”,
“10”:“Swing”,
“11”:“Swirl”,
“12”:“Wide”
},
“TEXT_VALUES_REMOTE”: {
“0”:“Remote Enabled”,
“1”:“Remote Disabled”
}
}
}
}
API interaction using POST on http://address/api.cgi
Example request: {“command”:“getinfo”,“data”:{“sessionID”:“RqHv083x1S5027n4MVVR56JrpeD1UMY”}}
Example response:
{
“success”: true,
“data”: {
“info”: {
“wlanSTAMAC”: “XX:XXXX:XX:XX:XX”,
“wlanAPMAC”: “XX:XXXX:XX:XX:XX”,
“ownSSID”: “DEVICE_XXXXXX”,
“fwVersion”: “1.4.4; 1.3.3; 1.3; 1.0.0.11”,
“wlanFwVersion”: “1.2.0”,
“acStatus”: 0,
“wlanLNK”: 1,
“ssid”: "My ssid,
“rssi”: -52,
“tcpServerLNK”: 1,
“localdatetime”: “Thu Apr 23 07:23:47 +3:00 2020 DST”,
“powerStatus”: 78,
“wifiTxPower”: 78,
“lastconfigdatetime”: 4744445520498393088,
“deviceModel”: “MH-AC-WIFI-1”,
“sn”: “XXXXXXXXXXX / XXXXXXXXXXXXX”,
“lastError”: 0
}
}
}
Hope this helps with integration
I also have a MH-AC-WIFI-1 unit and can confirm it has a locally accessible page that allows manual control of these settings without using IntensisHome cloud.
There’s a Homebridge plugin available for the unit but would be great if someone with the skills would develop similar for Openhab.
I am waiting for my air conditioning to be installed, which contains those devices. Once it is there, I am willing to dig into development.
That’s great news. They’re a good unit but cloud control system limits things a bit and having to purchase the IntensisBox model is less than ideal for most people. Please let me know if you want anything tested once you get into it.
Hi everyone,
I’ve been looking for something to connect my Fujitsu air-conditioner units (ASYG07LMCE, ASYG12LUCA; using the FGLAir app by default) with OpenHAB and I just managed to do it.
In case anyone comes across this issue, follow my guide below - it describes how to integrate the Fujitsu air-conditioners with FGLAir app connectiviy (Wifi module) with OpenHAB through MQTT.
-
You will need Deiger’s python script: https://github.com/deiger/AirCon
-
Extract the zip with the script to your home folder (ie. on a Raspberry to /home/pi/opt/fujitsu).
-
Make sure you have python3 (apt-get install python3)
-
Find the IP addresses of your airco units - unfortunately the FGLAir app doesn’t seem to support it now, so either you put them on a static IP upon installing them or you’ll need to look into your router’s network map to find them. You will need the IPs, there’s no way around.
This can help, my wifi module’s MAC addresses start with this bit, you might get lucky. The device ID is something like Murata Manufacturing Co., Ltd.
arp-scan 192.168.0.0/24 | grep -i "A0:CC:2B:EC"
Result:
192.168.0.x a0:cc:2b:ec:xx:xx Murata Manufacturing Co., Ltd. -
We’ll need to find the device IDs and create the config file:
python3 /home/pi/opt/fujitsu/query_cli.py --user your_FGLAIR_USERNAME --passwd your_FGLAIR_PASSWORD --app fglair-eu --config config.json
This should give you a result like this like my 3 units:
I0605 13:15:40.971 query_cli.py:196] Found devices: [{‘device’: {‘product_name’: ‘AC000W00285XXXX’, ‘model’: ‘AY001MTS1’, ‘dsn’: ‘AC000W00285XXXX’, ‘oem_model’: ‘AP-WB2E’, ‘sw_version’: ‘bc 2.6.15-fgl 02/04/20 12:25:04 ID phunt/bf51432’, ‘template_id’: 4904, ‘mac’: ‘a0cc2becxxxx’, ‘unique_hardware_id’: None, ‘hwsig’: ‘mac-a0cc2becxxxx’, ‘lan_ip’: ‘192.168.0.2’, ‘connected_at’: ‘2020-05-15T12:12:49Z’, ‘key’: 56789, ‘lan_enabled’: True, ‘has_properties’: True, ‘product_class’: ‘demo’, ‘connection_status’: ‘Online’, ‘lat’: ‘50xxx’, ‘lng’: ‘xxx’, ‘locality’: ‘xxxx’, ‘device_type’: ‘Wifi’}}, {‘device’: {‘product_name’: ‘AC000W00281YYYY’, ‘model’: ‘AY001MTS1’, ‘dsn’: ‘AC000W00281YYYY’, ‘oem_model’: ‘AP-WB2E’, ‘sw_version’: ‘bc 2.6.15-fgl 02/04/20 12:25:04 ID phunt/bf51432’, ‘template_id’: 4904, ‘mac’: ‘a0cc2becyyyy’, ‘unique_hardware_id’: None, ‘hwsig’: ‘mac-a0cc2becyyyy’, ‘lan_ip’: ‘192.168.0.3’, ‘connected_at’: ‘2020-05-15T12:12:56Z’, ‘key’: 345678, ‘lan_enabled’: True, ‘has_properties’: True, ‘product_class’: ‘demo’, ‘connection_status’: ‘Online’, ‘lat’: ‘50.xxx’, ‘lng’: ‘5.xx’, ‘locality’: ‘xxx’, ‘device_type’: ‘Wifi’}}, {‘device’: {‘product_name’: ‘AC000W00285ZZZZ’, ‘model’: ‘AY001MTS1’, ‘dsn’: ‘AC000W00285ZZZZ’, ‘oem_model’: ‘AP-WB2E’, ‘sw_version’: ‘bc 2.6.15-fgl 02/04/20 12:25:04 ID phunt/bf51432’, ‘template_id’: 4904, ‘mac’: ‘a0cc2beczzzz’, ‘unique_hardware_id’: None, ‘hwsig’: ‘mac-a0cc2beczzzz’, ‘lan_ip’: ‘192.168.0.3’, ‘connected_at’: ‘2020-05-15T12:12:59Z’, ‘key’: 123456, ‘lan_enabled’: True, ‘has_properties’: True, ‘product_class’: ‘demo’, ‘connection_status’: ‘Online’, ‘lat’: ‘50.xxx’, ‘lng’: ‘xxx’, ‘locality’: ‘xxxx’, ‘device_type’: ‘Wifi’}}] -
We’ll need to take the bold bits and generate config files for each of them:
python3 /home/pi/opt/fujitsu/query_cli.py --user your_FGLAIR_USERNAME --passwd your_FGLAIR_PASSWORD --app fglair-eu --config configairco1.json --device AC000W00285XXXX
You need to do the same for each airco unit, only changing the config file name (which will be in the home folder of your RPI - if you’re root then in /root/configairco1.json, if you’re user pi then /home/pi… -
Start the service and check - here you need to pair the config file (configairco1.json) with the appropriate IP address.
python3 /home/pi/opt/fujitsu/hisense.py --config configairco1.json --mqtt_host localhost --ip 192.168.0.2 --port 8888 --device_type fgl_b
This will start the script in the present window - it should look something like this:
192.168.0.2 - - [08/Jun/2020 18:42:30] "POST /local_lan/property/datapoint.json?cmd_id=204&status=200 HTTP/1.1" 200 -
192.168.0.2 - - [08/Jun/2020 18:42:30] "GET /local_lan/commands.json HTTP/1.1" 200 -
For every airco unit/service you run you must give a different port. Ie. for airco2 you should NOT give port 8888, but something different ie. 8887, since that will be the way to address it later.
- From another terminal window you can try to query this service:
curl -ik 'http://localhost:8888/hisense/status'
The result should be like this:
HTTP/1.0 200 OK
Server: BaseHTTP/0.6 Python/3.7.3
Date: Mon, 08 Jun 2020 16:57:16 GMT
Content-type: application/json
{"operation_mode": "OFF", "fan_speed": "AUTO", "adjust_temperature": 210, "af_vertical_move_step1": 0, "af_horizontal_move_step1": 0, "economy_mode": "OFF"}
-
If this works you’re good. In this case I’d suggest to either follow the script writer’s advice to make it a service, or alternatively you can run it manually in the background with ie. screen:
sudo screen -dmS airco1 python3 /home/pi/opt/fujitsu/hisense.py --config configairco1.json --mqtt_host localhost --ip 192.168.0.2 --port 8888 --device_type fgl_b --mqtt_topic Airco1
This will start the service running in the background as an app. You can put it in crontab as well for automatic execution upon boot:
crontab -e
@reboot sleep 30; sudo screen -dmS airco1 python3 /home/pi/opt/fujitsu/hisense.py --config configairco1.json --mqtt_host localhost --ip 192.168.0.2 --port 8888 --device_type fgl_b --mqtt_topic Airco1 -
Normally your script should be up and running. It should post to the MQTT topics of your choice:
By default it’s hisense_ac - in my example it’s Airco1.
So you can subscribe to the following topics:
Airco1/operation_mode/status
Airco1/fan_speed/status
Airco1/adjust_temperature/status
The actual values are posted on these topics every 10 minutes automatically as long as your service is running.
For publishing you use very similar topics, just replace the /status with /command:
Airco1/operation_mode/command [values: AUTO/COOL/HEAT/DRY/FAN/OFF]
Airco1/fan_speed/command [values: QUIET/LOW/MEDIUM/HIGH/AUTO]
Airco1/adjust_temperature/command [values: temperature10 -> if you want 24 C, you post 240; if you want 21 C, you post 210]*
You can also try it with curl:
curl -ik 'http://localhost:8888/hisense/command?property=adjust_temperature&value=220'
-
OpenHAB setup - Items:
Status: we need one which shows the actual status through incoming MQTT and one which publishes to MQTT for our commands:
String AircoLivingStatus “Airco Living status [%s]” <ac_unit> (Changesonly, GF_Living) { mqtt="<[JagoMQTT:Airco1/operation_mode/status:state:default" } // updates every 10 minutes
Switch AircoLivingStatusCMD “Airco Living” (gPseudo) { mqtt=">[JagoMQTT:Airco1/operation_mode/command:command:ON:ON], >[JagoMQTT:Airco1/operation_mode/command:command:OFF:OFF]" } // we publish ON/OFF, and that’s okTemperature: we need one which gets the actual set temperature through incoming MQTT (ie. 240), which we convert into proper Celsius/Fahrenheit by making it look like 24.0 and then show on sitemap, and the third one for controlling the temperature from sitemap.
Number AircoLivingTemperature “Airco Living temperature [%.0f]” (gPseudo) { mqtt="<[JagoMQTT:Airco1/adjust_temperature/status:state:default" }
Number AircoLivingTemperatureSELECT “Airco Living temperature [%.0f]” (Changesonly, GF_Living) // Sitemap SELECTION ITEM, auto-updated by AircoLivingTemperature and posts to AircoLivingTemperatureCMD through .rules.
Number AircoLivingTemperatureCMD “Airco Living temperature [%.0f]” { mqtt=">[JagoMQTT:Airco1/adjust_temperature/command:command:*:default" }Fan speed: we need one to show the actual setting, and one which we select in sitemap and command the airco.
String AircoLivingFanspeed “Airco Living fan [%s]” { mqtt="<[JagoMQTT:Airco1/fan_speed/status:state:default" }
String AircoLivingFanspeedCMD “Airco Living fan [%s]” { mqtt=">[JagoMQTT:Airco1/fan_speed/command:command:*:default] } // Selection item directly: QUIET/LOW/MEDIUM/HIGH/AUTO -
OpenHAB - rules:
rule “Airco Living Fan to Sitemap”
when Item AircoLivingFanspeed received update
then
postUpdate(AircoLivingFanspeedSELECT, AircoLivingFanspeed.state.toString)
endrule “Airco Living Temperature to Sitemap”
when Item AircoLivingTemperature received update
then
var Number receivedtemp=AircoLivingTemperature.state
var Number temptopost=receivedtemp/10
postUpdate(AircoLivingTemperatureSELECT, temptopost.intValue)
endrule “Airco Living Fan to Sitemap”
when Item AircoLivingFanspeed received update
then
postUpdate(AircoLivingFanspeedSELECT, AircoLivingFanspeed.state.toString)
endrule “Airco Living Temperature SELECT to Airco”
when Item AircoLivingTemperatureSELECT received command
then
var Number receivedtemp=AircoLivingTemperatureSELECT.state
var Number temptopost=receivedtemp*10
postUpdate(AircoLivingTemperatureCMD, temptopost.toString)
end -
OpenHAB - Sitemap:
Note: I have used “ON” instead of “AUTO” as a label on the sitemap for the StatusCMD.Text item=AircoLivingStatus icon=“ac_unit”
Switch item=AircoLivingStatusCMD label=“Airco Living” icon=“ac_unit” mappings=[AUTO=“ON”, COOL=“COOL”, DRY=“DRY”, FAN=“FAN”, OFF=“OFF”]
Selection item=AircoLivingTemperatureSELECT label=“Airco Living Temperature” icon=“temperature” mappings=[19=“19”, 20=“20”, 21=“21”, 22=“22”, 23=“23”, 24=“24”, 25=“25”, 26=“26”]
Selection item=AircoLivingFanspeedSELECT label=“Airco Living Fan” icon=“fan” mappings=[auto=“AUTO”, quiet=“QUIET”, low=“LOW”, medium=“MEDIUM”, high=“HIGH”] -
Enjoy:
1 Like
Hi all,
Very nice work again, victory to openhab.
I am installing a AC system (Mitsubishi) and i am very interested for this project/plugin of course.
All my house is connected to openhab =)
But … where the hell do you all find an affordable intesisbox ??
Perhaps i have not the good ref (https://www.intesis.com/products/ac-interfaces/mitsubishi-heavy-industries-gateways/mitsubishi-heavy-ascii-wifi-ac-mh-ac-wmp-1) but i find nothing below 160€ per unit…
Is it normal price ? (i understand in this case the other MQTT/ESP8266 solution … for 15€ per unit)
Any clue ?
Thanks
Don’t know if there is such a thing as an affordable Intesisbox.
Cost me AUD $430 to get an an INTESIS FJ-AC-WMP-1 Wi-Fi delivered home from AU reseller :-/
I got the MH-AC-WIFI-1 module for the Mitusbishi Heavy Industries AC unit. it was AUD190 through Bunnings. A little on the expensive side but it is very functional.
Has any been able to get their hands on the API documentation for the IntensisHome module?
Hit this guy up if uk
They are not cheap, my intesis’box’ were £155 each plus vat - and I’m in the trade! 
And guys be careful:
Mitsubishi is a very general term when it comes to a/c,
Mitsubishi Electric : Premium Brand
Mitsubishi Heavy Industries : Budget Brand
They are completely separate companies so be careful
Hi @delid4ve
Thanks for the advice, i was actualy wrong on the reference, this is the good one for model "MSZ-AP xx VG-E1 " :
https://www.intesis.com/products/ac-interfaces/wifi-gateways/mitsubishi-electric-ascii-wifi-ac-me-ac-wmp-1?ordercode=INWMPMIT001I000
(not even cheaper …)
Thanks
That’s the model I use, doesn’t miss a beat. I have 3 x Mitsubishi Zen Wall mounts on a multi using these.
Hey Dave, out of curiosity, have you ever had a chance to run the add-on? org.openhab.binding.intesisbox-2.5.1-6.jar 1
Has been working fine for me over these months but would be good to know how it plays with the Mitsubishi box.
Cheers.
@rb44 Noticed this in my logs today. Haven’t had a chance to look at the code yet to see whats causing it.
I tried with my original tweaked version and your newest one
2020-07-16 08:17:08.691 [ERROR] [ntesisbox.internal.IntesisBoxHandler] - openConnection(): Socket Exception: No route to host (Host unreachable)
2020-07-16 08:17:08.691 [ERROR] [ntesisbox.internal.IntesisBoxHandler] - write(): Unable to write to socket: null
java.lang.NullPointerException: null
at org.openhab.binding.intesisbox.internal.IntesisBoxHandler.write(IntesisBoxHandler.java:378) ~[?:?]
at org.openhab.binding.intesisbox.internal.IntesisBoxHandler.sendAlive(IntesisBoxHandler.java:291) ~[?:?]
at org.openhab.binding.intesisbox.internal.IntesisBoxHandler.polling(IntesisBoxHandler.java:340) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_241]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_241]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_241]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_241]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_241]
2020-07-16 08:17:08.694 [INFO ] [ntesisbox.internal.IntesisBoxHandler] - keep alive sent
2020-07-16 08:17:08.694 [ERROR] [ntesisbox.internal.IntesisBoxHandler] - write(): Unable to write to socket: null
java.lang.NullPointerException: null
@rb44 So just checked my router and one of my units hasnt got a dhcp lease. I did update fw the other day and havnt restarted it yet…
Either a new firmware issue or i just need to restart.
Will let you know once I’ve restarted and had a better look
Hi @delid4ve, yes that does sound like a network issue. Anyway just to confirm no changes to the network layer within the add-on. Thanks for the heads up.
Finally, I got my AC installed with IntesisHome/AirconWithMe WiFi adapters.
I will soon start development to get it fully implemented into openHAB.
@rb44 @delid4ve @ccutrer As you guys alreday implemented a IntesisBox Binding, I would suggest to merge the two appeoaches into a general Intesis Binding with seperate handlers for Home and Box devices. WDYT?
I already saw that yor Binding needs some refactoring, as it has channels implemented with static information, that should be changed into properties.
Best
Hans-Jörg
2 Likes
@hmerk One Intesis binding that just does the right thing, think that would simplify life for many Intesis device owners.
