You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after I finally got the node working a few weeks back, I just encountered the next problem a few days back :(
Node-Red does not detect any button presses anymore (weirdly enough, I did not change anything much, which could cause this problem).
The terminal output for node-red upon a button press ist:
node_pcap: EthernetFrame() - Don't know how to decode ethertype 34958
node_pcap: EthernetFrame() - Don't know how to decode ethertype 34958
node_pcap: EthernetFrame() - Don't know how to decode ethertype 34958
node_pcap: EthernetFrame() - Don't know how to decode ethertype 34958
This output is generated each time I press the button. The node-red-contrib-amazondash/node_modules/node-dash-button/bin/findbutton script shows similar symptoms. Each time the button is pressed, the four lines appear, but no button/mac-address is detected.
For comparison, I installed the npm node-dash-button module seperately and ran the findbutton script. here, the output was correct and as shown on the README.md file:
Possible dash hardware address detected: ab:cd:ef:gh:ij:kl Manufacturer: unknown Protocol: udp
Although the manufacturer (Amazon) was not detected (see node-dash-button issue #59), the IP-adress matched.
Therefore, I am now wondering if this node-red-node uses an older version of node-dash-button or how come the standalone installation works, but the node doesn't?
Since the node does not work for me and I am not very experienced in javascript, could anyone help me implement the new version of node-dash-button? Suggestions to solve the problem in another way would be helpful too! I have so far tried googling, reinstalling, and replacing the node-red-contrib-amazondash/node_modules/node-dash-button/ folder, none of which solved the problem or worked.
Thank a lot in advance!
The text was updated successfully, but these errors were encountered:
Mine detects the button presses but those messages constantly flood the logs, is there any way we can have these filtered out?
update: was able to filter it out by hacking at the pcap/decode/ethernet_packet.js and just deleting the console alert line for the "default"
I also have the same problem (using the homebridge plugin amazondash). Could you please explain what you exactly did? Where is the ethernet_packet.js file you edited stored?
Hello,
after I finally got the node working a few weeks back, I just encountered the next problem a few days back :(
Node-Red does not detect any button presses anymore (weirdly enough, I did not change anything much, which could cause this problem).
The terminal output for node-red upon a button press ist:
This output is generated each time I press the button. The
node-red-contrib-amazondash/node_modules/node-dash-button/bin/findbutton
script shows similar symptoms. Each time the button is pressed, the four lines appear, but no button/mac-address is detected.For comparison, I installed the npm node-dash-button module seperately and ran the findbutton script. here, the output was correct and as shown on the README.md file:
Although the manufacturer (Amazon) was not detected (see node-dash-button issue #59), the IP-adress matched.
Therefore, I am now wondering if this node-red-node uses an older version of node-dash-button or how come the standalone installation works, but the node doesn't?
Since the node does not work for me and I am not very experienced in javascript, could anyone help me implement the new version of node-dash-button? Suggestions to solve the problem in another way would be helpful too! I have so far tried googling, reinstalling, and replacing the
node-red-contrib-amazondash/node_modules/node-dash-button/
folder, none of which solved the problem or worked.Thank a lot in advance!
The text was updated successfully, but these errors were encountered: