-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard not appearing in LCD #50
Comments
This is most likely what is preventing your flow from running:
When that happens, xsbug should break so you can inspect the state. It would be helpful to see the JavaScript stack trace at that point. Also, if you are able to share the JSON for a simple flow that reproduces this problem, it may help sort this out more quickly. Thank you. |
Sure, that's expected when there is an unexpected exception. I didn't suggest you proceed from the breakpoint, but that you share the JavaScript stack trace from that point.
To be certain we are looking at the same thing, it would be very helpful if you would share the JSON for a simple flow that shows the problem or, at least, reference one simple flow in the repo examples that is not working for you. Thank you. |
here is the flow
for this , apologize im not a developer , you will have to guide me in this. you share the JavaScript stack trace from that point. Regards, |
Another point off topic , i used these nodes and doesnt work . |
As a rule, third party nodes are not supported. In any case, please do not mix issues together. It creates confusion. |
I just ran the weather example from the Node-RED MCU repository. It works just fine on ESP32. Here's what I did:
In comparing the If you are using the Node-RED MCU Plug-in to build and deploy your flow, the plug-in should automatically ensure that the |
Still off topic: Behind the scene, the |
(To avoid going further off topic, I've opened a Discussion for Blockly on the Node-RED MCU repository. Please continue this there.) |
Hi @phoddie ,
Let me ask you what version of Node.js ,Node-red ,Node-red-dashboard , Node-red-mcu Plugin, Moddable SDK and ESP-IDF you are using , so that i can replicate the same and try out . The errors from linux.
To stay in line , this time used the m5stack fire . It gives another error , guess its was discussed in some other threads, beleive its a non-issue for this case. Next step is to downgrade the node-red-dashboard, node-red-mcu plugin to earlier versions and test as the problems comes up with UI nodes only . Meantime any help is welcome . Regards, |
macOS, actually. But, the OS where Node-RED runs probably doesn't make a difference here. From your notes, the steps you are taking to build, deploy, and run the Dashboard flows are not clear. Without that, neither @ralphwetzel nor I can reproduce the problem and so are limited in our ability to help resolve this issue. Would you share step-by-step instructions that we can follow to reproduce the issue? Thank you. |
Happy to provide what i did. Hardware Devices : M5stack Core2 , M5stack Fire , M5Atom Flows: https://github.com/phoddie/node-red-mcu/blob/main/examples/dashboard/weather/flows.json Followed the documentation at moddable for installing on esp32 devices and individually tested , esp-idf ($idf_path\examples\get-started\hello_world) , moddable sdk ($moddable\examples\piu\balls) ,nod-red-mcu plugin through the node-red plugin and using mconfig in the plugin cache folder.
Finally ended up looking into node-red-mcu and found out nodes/dashboard/ui_templates.js calling the fonts Appreciate @phoddie for willing to help out , but it seems not to be a plugin error , would you recommend shifting this to node-red-mcu repo?. |
Thanks for the additional info. I was eventually able to reproduce the problem. Simple fix. That's now committed. You just need to update/ireinstall the Node-RED MCU Plugin and you should be set. |
Hi,
Been playing with this great piece of work, however ran into a small problem. While the flows work perfectly , except for some errors in xsbug, the dashboard dont appear on my m5stack fire and m5stack core2.
i do see these as undefined , however my esp-idf doesnt throw it when i do an mconfig on the mcu-plugin-cache with my esp-idf terminal
and
Also another point to highlight is
May not be an issue though.
With this resolution im hoping to continue my tinkering!
Thanks,
spillz
The text was updated successfully, but these errors were encountered: