-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since 2.0.6 release the app crashes every day #181
Comments
Thanks for the details, I will have a look. Homey changed tons of things and the APIs are beta. I have to find workarrounds for the issues. The inner parts of the App have not changed in a single line. |
That's the report that you submitted. It does not contain any information. I will have a look at others and work from that side. App ID User Message: ---- stdout ---- ---- stderr ---- |
Can you please remove and recreate the Plan devices? Does it load then? |
To do that, I have to restart the app Heating Scheduler, then it’s ok but
for a while. I have removed and recreated one plan device.
Le dim. 7 mai 2023 à 10:15, Markus ***@***.***> a écrit :
… Can you please remove and recreate the Plan devices? Does it load then?
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF76MC3UL3MXCR3JDZUU6TXE5KY3ANCNFSM6AAAAAAXYU7SA4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You must please recreate all to test it, otherwise it has no effect. I saw a report where a capability was missing from the plan device. This is fixed by recreating the devices. |
Dear Markus, but recreating devices and flows is completely unwanted, I have 2 devices,with 4 flows connected, that's almost acceptable, but what if I have 7 devices, and 30 flows? Please revert to before 2.06. |
Hi Markus, I recreated the plan devices (Thermostats), I hope this is what
you expected.
Recreating all Scheduling, plans etc would be tricky on my side
Le lun. 8 mai 2023 à 08:51, pear7777 ***@***.***> a écrit :
… Dear Markus, but recreating devices and flows is completely unwanted, I
have 2 devices,with 4 flows connected, that's almost acceptable, but what
if I have 7 devices, and 30 flows?
Please revert to before 2.06.
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF76MECOD7DHB3IWDCY6QDXFCJX7ANCNFSM6AAAAAAXYU7SA4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi |
This device delete and recreate for Thermostat Plan Devices doesn’t work on
my side. Same issue: app stucked.
Le lun. 8 mai 2023 à 09:21, Alexis Daguès ***@***.***> a
écrit :
… Hi Markus, I recreated the plan devices (Thermostats), I hope this is what
you expected.
Recreating all Scheduling, plans etc would be tricky on my side
Le lun. 8 mai 2023 à 08:51, pear7777 ***@***.***> a écrit :
> Dear Markus, but recreating devices and flows is completely unwanted, I
> have 2 devices,with 4 flows connected, that's almost acceptable, but what
> if I have 7 devices, and 30 flows?
>
> Please revert to before 2.06.
>
> —
> Reply to this email directly, view it on GitHub
> <#181 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABF76MECOD7DHB3IWDCY6QDXFCJX7ANCNFSM6AAAAAAXYU7SA4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Hello, As from today 14:00, when i reset homey daily, my homey us completely unresponsive, since this app is the only one with problems, after installing the suggested other app, I guess this has to do with the suggested app in this thread. Don't know what to do, yet, suppose a restore... So far for auto updating apps. Br Peter |
Hi |
Hi,
Since last update 2.0.6, the app is stuck :
Pause symbol in the app list next to Heating Scheduler
The Plans Devices are ghost (see picture)
An app restart, works for a few hours, and it crashes again.
As seen on app reviews, other users have these concerns, luckily we are running to Spring.
crash report diagnostic : 60f53816-3c65-4b79-b77c-3509f5cb7e25
The text was updated successfully, but these errors were encountered: