Info to homey #65
Assignees
Labels
bug
Something isn't working
help wanted
Extra attention is needed
wontfix
This will not be worked on
Comments
|
Probably, but I need more info and time. Can you please go in the settings of the app and submit a diagnostic report for me. Thanks |
|
a0c7cd01-3f66-4677-95b2-967bb1d52dc8
Report info
I can make another report tomorrow when info is old in homey again.
Op ma 5 feb. 2024 22:06 schreef Stefan Lenders ***@***.***>:
… Probably, but I need more info and time.
Next 2 weeks I can't fix it if it's an issue with the app.
Can you please go in the settings of the app and submit a diagnostic
report for me. Thanks
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMSMAPRXWFZEW2HYEZIQI3YSFCUVAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGA4TGMZQGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Can you switch on debug of one of the devices (settings of the device) let it run for 3 minutes and submit a report after. Don't restart the app after you switched on debugging |
|
Hi. Debug is at least 3 minutes activated.
f3eb9666-59b2-45ef-b743-b84f0a9038b4
Report make just before i closed debug.
Op ma 5 feb. 2024 23:02 schreef Stefan Lenders ***@***.***>:
… Can you switch on debug of one of the devices (settings of the device) let
it run for 3 minutes and submit a report after.
Don't restart the app after you switched on debugging
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMSMAPILNDPTUJF2LK2O3DYSFJFTAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGE3TKOJZGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Error: connect ETIMEDOUT 192.168.3.41:80 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '192.168.3.41', port: 80 } It simply can't connect. It gets a connection timeout . Please check your network connectivity. |
|
The network connection is ok.
I can connect to the homey, to the p1mon pi and after a restart of the
ztatz app it connects.
But when i opened a ztatz device on homey I got an orange bar with the text
"Refresh seems to take long..."
Op di 6 feb. 2024 10:55 schreef Stefan Lenders ***@***.***>:
… Error: connect ETIMEDOUT 192.168.3.41:80 at TCPConnectWrap.afterConnect
[as oncomplete] (node:net:1157:16) { errno: -110, code: 'ETIMEDOUT',
syscall: 'connect', address: '192.168.3.41', port: 80 }
It simply can't connect. It gets a connection timeout . Please check your
network connectivity.
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMSMAJZ2OK3ZKK54VLTGQTYSH42RAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRZGE2TIOJYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Homey tries to connect to http://192.168.3.41/api/v1/smartmeter?limit=1 That times out. That is why you are getting the orange bar. Not something I can fix in the app. Please check if you can reach it and check if any firewalls block that traffic. Has it worked before? |
|
It worked perfect . It started last two weeks.
No further problems on network.
Op di 6 feb. 2024 11:15 schreef Stefan Lenders ***@***.***>:
… Homey tries to connect to
http://192.168.3.41/api/v1/smartmeter?limit=1
That times out. What is why you are getting the orange bar. Not something
I can fix in the app.
Please check if you can reach it and check if any firewalls block that
traffic.
Has it worked before?
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMSMAJ52K4IPA3SE5DGS33YSH7EPAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRZGE4DSOJXGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Maybe it started after the last update 0.8.6
Op di 6 feb. 2024 12:01 schreef rpb006 ***@***.***>:
… It worked perfect . It started last two weeks.
No further problems on network.
Op di 6 feb. 2024 11:15 schreef Stefan Lenders ***@***.***>:
> Homey tries to connect to
>
> http://192.168.3.41/api/v1/smartmeter?limit=1
>
> That times out. What is why you are getting the orange bar. Not something
> I can fix in the app.
>
> Please check if you can reach it and check if any firewalls block that
> traffic.
>
> Has it worked before?
>
> —
> Reply to this email directly, view it on GitHub
> <#65 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFMSMAJ52K4IPA3SE5DGS33YSH7EPAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRZGE4DSOJXGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
The app didn't change nor was ztatz. So if it work there is no factor from the app side that could have broken it. The error you are getting again is network related. |
|
I shall duplicate an ztatz app on homey. See if the new one connect better.
Thanks for your suggestions so far.
Op di 6 feb. 2024 12:29 schreef Stefan Lenders ***@***.***>:
… The app didn't change nor was ztatz. So if it work there is no factor from
the app side that could have broken it.
The error you are getting again is network related.
You can try removing one of the devices and re-adding them. Further help I
can offer in 2 weeks. But then I would need to troubleshoot within your
network.
—
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMSMAN6P7VACSZKTCXVNG3YSIHYLAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRZGMZDGOJWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
After the update to 10.0.6 on homey the Orange bar is gone, and app works
well again.
Thanks for support.
Op di 6 feb. 2024 14:25 schreef Remco Bekkema ***@***.***>:
… I shall duplicate an ztatz app on homey. See if the new one connect better.
Thanks for your suggestions so far.
Op di 6 feb. 2024 12:29 schreef Stefan Lenders ***@***.***>:
> The app didn't change nor was ztatz. So if it work there is no factor
> from the app side that could have broken it.
>
> The error you are getting again is network related.
> You can try removing one of the devices and re-adding them. Further help
> I can offer in 2 weeks. But then I would need to troubleshoot within your
> network.
>
> —
> Reply to this email directly, view it on GitHub
> <#65 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFMSMAN6P7VACSZKTCXVNG3YSIHYLAVCNFSM6AAAAABC22VMVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRZGMZDGOJWG4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
burnacid
added
bug
|
Might have been an issue with the homey version for some reason. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The info to homey is only when I restart the app. And then only once until I restart the app ztatz again.
Can this be solved?
The text was updated successfully, but these errors were encountered: