# Mitsubishi AC in Melcloud node
**URL:** https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621
**Category:** General
**Created:** [8 November 2025 20:30 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621 "2025-11-08T20:30:43Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Felix](https://discourse.nodered.org/u/Felix)
#### Post date: [8 November 2025 20:30 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/1 "2025-11-08T20:30:44Z")
Hi all,
after 2 years I've tried to setup my two AC included in home (mitsubishi AY35) to NodeRed via Melcloud node. On APP are both of them connected, working properly. But in nodered I am not able to read any data, after connect via connect melcloud node is not possible to list devices ....
Please, help me with it, if have any knowledge.
Thanks a lot. Bohumil.
---
### Author:  [@Brian5600](https://discourse.nodered.org/u/Brian5600)
#### Post date: [9 November 2025 18:18 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/2 "2025-11-09T18:18:39Z")
Hi Felix,
After setting up credentials, with melcloud-connect node, inject and debug node. The inject node is just injecting default timestamp. In debug window you can look in the output from debug node, you have to find BuildingID and DeviceID by opening the structure. It is under Devices. The structure depends on how the AC is set up in the APP. In "melcloud device node" these parameters can be used to manage your device.
I have 2 LN35, which I manage in node-red for a couple of years by now.
Best regards,
Brian.
---
### Author:  [@Felix](https://discourse.nodered.org/u/Felix)
#### Post date: [9 November 2025 19:07 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/3 "2025-11-09T19:07:55Z")
@Brian5600 thanks to reply, I have created, as you described, but on the output debug node I have only error. Nothing appears from defined credentials.
---
### Author:  [@Brian5600](https://discourse.nodered.org/u/Brian5600)
#### Post date: [9 November 2025 20:48 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/4 "2025-11-09T20:48:07Z")
If you show the whole message in debug window, you get the status code, fx. 200 for at valid response. I think it will be different, if something is wrong.
Credentials is email and code, same as for the app or web, [https://app.melcloud.com/](https://app.melcloud.com/)
---
### Author:  [@Felix](https://discourse.nodered.org/u/Felix)
#### Post date: [9 November 2025 21:13 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/5 "2025-11-09T21:13:50Z")
@Brian5600 sure, agree with you.
Here is some errors that provides debug after got timestamp inject via melcloud connect :
So, this done after complete reinstall of NodeRed to new card, Rpi 3B.
This is the same, as before. Credentials are tested on melcloud app and WEB. Completely OK, without problems in login.
Well .... I am sad.
Best regards ... Bohumil.
---
### Author:  [@Brian5600](https://discourse.nodered.org/u/Brian5600)
#### Post date: [9 November 2025 22:46 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/6 "2025-11-09T22:46:46Z")
I can see you have another post with versions. I think that should be solved first. This look like an installation error in node-red.
---
### Author:  [@Felix](https://discourse.nodered.org/u/Felix)
#### Post date: [10 November 2025 16:30 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/7 "2025-11-10T16:30:55Z")
@Brian5600 I am not sure, because this actual node-red version is totally newer and node.js jumped from 14.3 to 24 and node-red version jumped from 2.3 to 4.1.
I think, that this may be another problem. May be in network or with AY25(and 35) process adding in network.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [8 February 2026 16:31 UTC](https://discourse.nodered.org/t/mitsubishi-ac-in-melcloud-node/99621/8 "2026-02-08T16:31:37Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.