
PRO
smiller29
USA
Asked
— Edited
Can someone help me with the development of a ARC skill? I have put together a Arduino script that is for an ESP32 it contains the EZB firmware and it also has a very robust MPU6050 logic. I need to have the skill in ARC be able to allow some options to be set and also bring MPU data back in variables. Like I said I have all the logic I just need help making the UI for ARC.
If you are willing to help let me know and I will send you the code.
Well that would explain it LOL. Let me see if I can do something about that..:
DJ, Tell me where I screwed up now please. I hope you are not get mad at me.... Please understand I am doing the best I can with my limited understanding of all this stuff but I feel I am getting closer.
What’s wrong with it?
the only suggestions I’d have are to check if there’s a connection to the ezb otherwise you’ll throw an exception every second. But looks fine other than that
It disconnects the ESP32 EZB connection the vars are set to 0 when it starts they don't ever change in the var watcher service. and then it disconnects.
Id suggest taking the readvalues() out of the timer event. Put it in a button for testing.
That way you can rule out the exception that’s repeatedly thrown during disconnect. And you can verify other features of the esp32 firmware you altered is working.
Also, the disconnection would have a message in the log window. That’s useful because it’ll tell you why it disconnected
DJ, I made the changes you recommended as seen below. When I connect to the ESP32 from ARC the firmware starts the process polling the MPU6050 ARC does not have any connection issues until I click on the Get MPU Values button. When I do that the connection is dropped to the ESP32. I will also attach the VS code if you want to play with that.
ESP32_MPU6050.zip
That's good progress. Now you can look at the debug log window that i have suggested so you can see why it's disconnecting
When I run this from the VS debugger I get no errors that I can see. also nothing shows up in the text area of the skill is there another debug log I can look at? Sorry if this is a stupid question.