search

Christian-Me / remote-device-table

Node-RED flow to display the status of remote devices on the dashboard using ui-table
Apache License 2.0
16 stars 10 forks source link

"TypeError: func.apply is not a function" #2

Open smcgann99 opened 3 years ago

smcgann99 commented 3 years ago

hi,

I'm trying to adapt your flow for use with tasmota and other devices. Most things seem to be working but there are a few issues. The watchdog doesn't work for me, it is creating the context variables for two devices that "should" be showing as lost but the table doesn't update- I see this error in debug 25/01/2021, 16:47:03node: $state watchdogfunction : (error) "TypeError: func.apply is not a function"

I also see

"Context 84e3502f.6ee37:9d52d40a.a63668 contains a circular reference that cannot be persisted"

Do you have any ideas - I cannot see any reference to func.apply in the watchdog node ??

Christian-Me commented 3 years ago

I looked into it .... Think I found the problem:

line 59 should be changed into: lostTimers[msg.topic].timer=setTimeout(mqttTimeout, (timeout+graceTime)*1000,

I added the graceTime to the function pointer and not the timeout value. Or a search / replace problem... ups. Now I don't get that error any more ... but don't know if it actually works until the timeout kicks in.

smcgann99 commented 3 years ago

I will test when I get time thanks

Sent from Mail for Windows 10

From: Chris Sent: 13 February 2021 02:45 To: Christian-Me/remote-device-table Cc: smcgann99; Author Subject: Re: [Christian-Me/remote-device-table] "TypeError: func.apply is not a function" (#2)

I looked into it .... Think I found the problem: line 59 should be changed into: lostTimers[msg.topic].timer=setTimeout(mqttTimeout, (timeout+graceTime)*1000, I added the graceTime to the function pointer and not the timeout value. Or a search / replace problem... ups. Now I don't get that error any more ... but don't know if it actually works until the timeout kicks in. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

smcgann99 commented 3 years ago

I'm still getting "Context 84e3502f.6ee37:9d52d40a.a63668 contains a circular reference that cannot be persisted"

Christian-Me commented 3 years ago

Context 84e3502f.6ee37:9d52d40a.a63668 contains a circular reference that cannot be persisted

Where you get this? in the debug tab or in the browser console?

smcgann99 commented 3 years ago

its in the debug tab