search

twocolors / node-red-contrib-esphome

Node-RED nodes to ESPhome devices
MIT License
18 stars 5 forks source link

Non-fatal bug, just letting you know #31

Open DeeBeeKay opened 6 months ago

DeeBeeKay commented 6 months ago

Hi @twocolors

This does not break anything, it just sends a message into debug.

When I deploy a flow, I get an error message in the debug window, for example:

Entity (2974081917) not found on device

However, this does not stop the ESPHome node from working, and my automations still work correctly despite this message.

Thank you for your continued work on this.

twocolors commented 6 months ago

show screen from node OUT and you use full deploy ? or modify deploy?

DeeBeeKay commented 6 months ago

Hi, sorry I am slow to respond, there's a lot going on.

This is the output in debug:

2023/12/29, 07:20:57node: Front Highmsg : string[39]
"Entity (2974081917) not found on device"
2023/12/29, 07:20:57node: Rear Highmsg : string[39]
"Entity (2680563962) not found on device"
2023/12/29, 07:20:57node: Front Lowmsg : string[39]
"Entity (1088152393) not found on device"
2023/12/29, 07:20:57node: Rear Lowmsg : string[38]
"Entity (883961372) not found on device

So it is one ESPHome device that controls 4 sets of floodlights: Front High, Rear High, Front Low, and Rear Low. They are circuits that use different amounts of power.

This node works as expected. But the error messages appear when I press Deploy.

Also, I upgraded now to 0.25, and I had to delete and re-add my ESPhome devices. It is working again 100%, but, just telling you.

Thank you for your work on this project.

twocolors commented 6 months ago

you use full deploy ? or modify deploy?

tethlah commented 5 months ago

This is happening to me too. It happens on Full Deploy or When Node-Red starts, but not on Modify Deploy.

twocolors commented 5 months ago

read this answer https://github.com/twocolors/node-red-contrib-esphome/issues/15#issuecomment-1493763057

tethlah commented 5 months ago

read this answer #15 (comment)

What about it, that says that you corrected the issue 8 months ago. I'm still having this issue in 0.2.6 today.

DeeBeeKay commented 5 months ago

Hi @twocolors,

Again, sorry I am slow to respond. I did the test you asked.

It happens only on full deploy, not on modified nodes. Again, it has no effect on actual running code - everything works 100%. It's just some debug code.

However, I saw something interesting.

I have now many ESPHome devices using your node. This error only happens on ONE ESPHome device. The other ones do not produce this output on startup.

If I figure out why, I will tell you. If it matters, it is the first device I added.

Also, please remember I am happy to help with English documentation.

twocolors commented 5 months ago

read this answer #15 (comment)

What about it, that says that you corrected the issue 8 months ago. I'm still having this issue in 0.2.6 today.

This is the correction that you see warnings while there is no connection to the device...

everything used to break and the node would crash

tethlah commented 5 months ago

Hi @twocolors,

Again, sorry I am slow to respond. I did the test you asked.

It happens only on full deploy, not on modified nodes. Again, it has no effect on actual running code - everything works 100%. It's just some debug code.

However, I saw something interesting.

I have now many ESPHome devices using your node. This error only happens on ONE ESPHome device. The other ones do not produce this output on startup.

If I figure out why, I will tell you. If it matters, it is the first device I added.

Also, please remember I am happy to help with English documentation.

Interesting, the same for me. I have 9 out nodes, only one of them is having this problem. It also just so happens to be the last device I have listed in ESPHome.

twocolors commented 5 months ago

@tethlah @DeeBeeKay this error occurs when, after restarting node-red, you immediately send data to esphome (set a delay because node-red does not yet have time to connect to esphome and receive its capabilities)

tethlah commented 5 months ago

@tethlah @DeeBeeKay this error occurs when, after restarting node-red, you immediately send data to esphome (set a delay because node-red does not yet have time to connect to esphome and receive its capabilities)

It's not just after restarting, it's also when redeploying. And based on timestamps on other flows, there are other nodes that are instantiating prior to this node throwing the error. It's literally just one node throwing the error. There are 2 nodes being triggered at the same time, one throws the error, the other doesn't.

twocolors commented 5 months ago

oh full deploy / restart flow / restart nod-red all this method reconect to esphome , show screen where you see this error

tethlah commented 5 months ago

I'll have to wait, i can force it to pop up during all those instances, but it'll randomly pop up at some point during the day in the debug, when it pops up again I'll look and see if something happened before it pops up.