HP23 how to get Error msg?

Hi

Got HP23 and Nimly TouchPro. I’m trying to make some simple flows (I’m new with Homey) and it’s not working. Looks like the problem is with Nimly (I will talk with producer) but because of that I found that Homey (or Nimly app) cheat me. In developer tools I found that device and is written there that is „Ready” „Available” and no „Warnings” but in the same app at Zigbee devices lists I see that Nimly was „Last seen 3 days ago”. In addition, flows are executed the way that it looks like everything works fine but it isn’t because phisically nothing hepening. Ok, and here is my question.

How you know that everything is ok with system/devices? Is it written somewhere? Are there any log files? Why homey do not give any Error msgs for example at Timeline? And how can I get error push message when some flow don’t work properly because device is for example disconnected?

TIA

Unfortunately devices which become “silent” are not, or far too late considered unreachable.
But there’s a nice script you could run 1 or more times a day, to get reports about zigbee devices which were last seen more than x hours ago.
You’ll need to install Homeyscript for it to work.

Zigbee ins & outs:

2 Likes

You will at least get a error message when you try to trigger the device in a flow.
When calling the card for the device; if it gets an error the flow will exit throu the lower part of the card. Connect a e.g. push notis card to it and use the tag “error” in the message.

Very good tutorial. I see that need to do few changes, buy some routers and change Zigbee chanel which will not be in collision with wifi. Script is also very nice, very good for admin but it’s not resolving my problem. And by the way I see that I can’t trust to my system. In my opinion Nimly shall give me warn when something is wrong with lock. I got a lot of Frient smoke alarms, hopefully that works better. I will need to do some tests.

I made a tests and see that Nimly app is working bad. It takes a lock status from Homey, not from real phisical device.

About getting error, you say that I shall use “else” card? From what I see, that part is activated when something goes wrong in general and it’s not only to get errors. Or I understood it wrong?

I see you are using standard flow. The error connector only exists in advanced flows.
As you have a Homey 2023 I should suggest you to start using advanced flow (only in web browser, not in app).
It will give you so much more possibilities.

In advanced flows mot cards have an error connection at the bottom of the card.

Ok, now I see. Yes, advanced flows is what I need, thanks :slightly_smiling_face:

P.S. Sad that in standard flows is not possible to get an error. In my opinion it is something necessary, it’s basic.

No, indeed you can’t rely on Homey and on wireless systems.

I would advise everyone against considering Homey as a security device or life-saving device.
No wireless system is “to trust”, it can and will fail at times.

Well, I was not thinking that this is highly trusty system but in my opinion I could expect some higher level than I get. Because from what I see until now, for example Nimly Touch Pro Lock got one way communication which is… unprofessional. Everything works very nice when everything is fine but when the connection between Homey and Lock is lost, Nimly app still working like “normaly”. Looks like they don’t have any “check” protocol. When app (flow) is sending command to device it goes without checking if that was received and done by lock. Simply sending and that’s all. The status is not taken from real device but from app variable. That’s a kid level of programming and I’m surprised of that.

So yes, agree with you, wireless systems can easily fail, but like I said, could be much better. At least I should get message every time when something is wrong with communication.