Is this a beta release? Any plans to release to official?
No, this is a community developerās release; as explained in post #1 of this topic.
About the fuzzy title āofficialā:
Athom tends to label apps released āby a companyā as āofficialā;
Which has nothing to do with quality, better or quicker support, or more options/settings.
The fact about the āofficialā Panasonic app not working, and this one by Robert Schmidt is, makes āofficialā a bit meaningless. imho.
2 Likes
yes I know but for a big crowd installation via git/docker/npm is no option.
Then youād follow this topic and hope for the best:
2 Likes
First I would like to say that to install this alternative was like a dream - it just installed and when having the correct credentials it found my ACĀ“s without any problem.
I have not use the app yet, more than to monitor the temperature set on the ACĀ“s. I did have a look at the source code and the cards. I am missing 2 things that I would like to have added or add myself:
- There is a operation_mode missing that we use - it support 8-15 degrees heating in a special way with high fan and no stop for de-icing - typically used for buildings in winter mode to prevent freezing.
=>
I did investigate around this mode using this application (the alternative) comparing to how the Panasonic app show the settings. It seems like the 8-15 setting is just a preset in the remote control and the official application that set the temparatur. If I adjust in the alternative the temperature above 15 degrees it show āheatā. Setting down to 10 degrees it show 8-15.
But this is not what the AC is actually doing. After this test it heated to 16 degrees even showing 8. So something hidden is happening here.
- Outdoor temperature. This is not a āmust haveā, since there exists forecasts, but it is a good way to see how cold the unit think it is.
1 Like
Good to read about your experience!
Iāve not planned any changes related to the ā8-15 degreeā mode. I also donāt fully understand how it works. But a PR is always welcome 
See GitHub issue here.
Good question! It sure sounds like it - but the code was written to share one client object between all devices. Looking at the code now, I think multiple authentication flows could take place if Homey initializes devices in parallel.
I only have one device myself, but Iāll add a GitHub issue.
I did read the thread for the other project and found out how it works. It requires 3 things to be triggered (yes triggered - it is not a mode by itself)
- Temperature in the range 8-15
- Fan at max
- Heating mode
When all these are true it will run the 8-15 mode and set the wanted temperature.
QA OK on issue #26. Ready for merge
1 Like
Thanks for testing so quickly, @Jarl!
It was a while since I used the app and tried to upgrade.
It didnāt work and I uninstalled the app and installed it again.
Nothing happens when I press Authenticate?
No, latest version is 1.1.11 (GitHub - ugumba/homey-panasonic-comfort-cloud-alt)
2 Likes
is there comming a official homey app in the future for this?
And this one is use the https://aquarea-smart.panasonic.com/ platform
But is comming in the future depending at this one https://aquarea-service.panasonic.com/
Or using heisamon?
Questions about an official app for any Panasonic products should be directed to Panasonic and/or Homey.
I have no intention of publishing my app on the app store.
Firstly, because Panasonic provides no support for community developers, Iām firmly convinced they should take responsibility for an official app.
Secondly, I have no interest on being on āthe hookā for providing commercial quality software for free, into the thoroughly one-sided commercial ecosystem which Homey is.
1 Like
Iām strugiling with the latsest 1.1.13 version. Builds OK, but fails to start on the Homey. I just got two different errors when the only thing i did was build+install>error#1 and then build+install->error#2, so not sure whatās the source of the instability.
Anyone else seeing similar issues or is it working for you?
2024-12-11T21:25:39.572Z [log] [MyApp] MyApp has been initialized
2024-12-11T21:25:41.344Z [log] [ManagerDrivers] [Driver:aircon] Driver has been initialized
2024-12-11T21:25:41.999Z [log] [ManagerDrivers] [Driver:aircon] initializing client (1.22.0)
2024-12-11T21:25:42.029Z [log] [ManagerDrivers] [Driver:aircon] authenticating xxx[dot]yyy[at]gmail.com
2024-12-11T21:25:47.646Z [log] [ManagerDrivers] [Driver:aircon] authenticated
2024-12-11T21:25:49.536Z [err] [ManagerDrivers] [Driver:aircon] [Device:9a5aeee2] getDevice failed: RangeError: Value longOffset out of range for Intl.DateTimeFormat options property timeZoneName
at new DateTimeFormat ()
at MyDevice.getCurrentTimezoneOffset (/drivers/aircon/device.js:36:27)
at MyDevice.fetchLastHourWattsConsumption (/drivers/aircon/device.js:58:29)
at /drivers/aircon/device.js:75:28
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async MyDriver.invokeClient (/drivers/aircon/driver.js:109:24)
at async MyDevice.fetchFromService (/drivers/aircon/device.js:72:22)
at async MyDevice.fetchAndRestartTimer (/drivers/aircon/device.js:104:9)
at async MyDevice.onInit (/drivers/aircon/device.js:177:13)
at async MyDevice._onInit (/opt/homey-client/system/manager/ManagerApps/AppProcess/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:1:1682)
(I get this same error for all my 4 devices)
On second build+install I get a different error:
2024-12-11T21:37:55.040Z [log] [MyApp] MyApp has been initialized
2024-12-11T21:38:01.034Z [err] [ManagerDrivers] Error Initializing Driver aircon: ReferenceError: ReadableStream is not defined
at Object. (/node_modules/undici/lib/web/fetch/response.js:528:3)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
at Object.Module._extensionsā¦js (node:internal/modules/cjs/loader:1157:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at Module.require (/opt/homey-client/system/manager/ManagerApps/AppProcess/node_modules/@athombv/homey-apps-sdk-v3/index.js:1:183)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/node_modules/undici/lib/web/fetch/index.js:11:5)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
Hmmā¦ did you run ānpm installā before building? Iāll give it a closer look when I get home.
The second error looks stranger - it looks like a web request failing downloading a JS module - quite far from the code in this app. Does it happen again?
I suspected issues with my Homey Pro (2016-2019), so did a restart and it failed to complete the boot. It āvisitedā the floor here the other day and the shell broke open, so seems more broke (a PowerSupply component looks bad).
Got hold of a new (usedā¦) device, restored from backup (was a dream defintly worth the backup cost!) and things look OK - until I started installing the PCC APP. HEAD gave me the same issue as reported above.
Started testing older versions of the app starting from a version I know worked. And it still worked. But when I moved to the commit/merge with support for consumption/outside temp (Dec 2nd), I got the same āReadableStream is not definedā error on the device. So that commit broke support for Homey Pro 2016-2029 in this APP. Iāll do some more investigation into the commit to try to find the actual reason.
Suspect the root cause is that my āoldā Homey is running an older version of Node.js (v12.22.11), but not sure.
Hi,
I am also getting the same error as Jarl:
Homey Pro (2016-2019)
While installing:
(node:1776) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
And the App log:
2024-12-14T19:48:01.054Z [err] [ManagerDrivers] Error Initializing Driver aircon: ReferenceError: ReadableStream is not defined
When installing a new aircon, there is a red error triangle in the aircon icon.
Any advice would be recieved with a big thanks.
Thanks for reporting, @RuneTun. Iām getting the same two warnings/errors.
Red triangle is due to that the app has failed loading so the device is unknown.
Short term workaround is to do āgit pullā on ugumbas repo and then do āgit checkout a7c5e6a6dd4f7f12d24f08f446c6e3f2f91c91aeā (last working version for me), ānpm installā, āhomey app buildā and finally āhomey app installā.
I raised issue v1.1.13 not working on Homey Pro (2016-2019) Ā· Issue #30 Ā· ugumba/homey-panasonic-comfort-cloud-alt Ā· GitHub to track the issue.
1 Like
