 Alright, so today is the 3rd of February. This is the DevSync. Maybe the audio will record this time. Let's see. Okay, Chris has our backlog up. Let's go ahead. Oh, we need to go ahead and review Sprint 19 here. Go ahead and start with Chris then. Okay, so I got the testing done on and added some changes to tests for getting the Panticor device ID using our pairing code. That all is working now. So I've moved on to retrieving the device information and being able to and then the software endpoints and then there's three other endpoints I got to I got to implement for changing whether your auto update setting in your SSH key and something else. So yeah, that's that's what I'm moving on to next is I'll probably go in the same Selenium point because it'll talk to me on the device at its screen. So yeah, that's where I'm going next. Okay, sounds good. In terms of timeline, how do you feel about wrapping that work up by Friday? It'll be tight. I could probably get the API stuff done but linking it up to the UI. That last step of getting it all working together that maybe it'll be close. Okay. All right, because yeah, I mean, you know, it takes as long as it takes but I want to get this done so that we can move on to bug fixing because we've been spending a lot of time talking about bugs, which is great because you know, we're all in the same system now. I am anxious to actually start addressing those directly. Yeah, it's possible it may take another day or two after the sprint but hard to tell right now. Great. Who's next? Derek? Yeah. Okay, so I've been mostly working on my revisions to the SJ240. I think I mentioned yesterday I was going to, as I'm making these revisions and printing parts and so should have another device ready to distribute. So, hoping that by, definitely by the end of the week. And so I also started doing a little bit more testing so I've got this, Josh and I are kind of working on it together to a certain degree but this stress test idea. And so I was, you know, playing some music on it for a prolonged period of time to see how that affected things in it. And I was getting the thermostat icon popping up a lot on, you know, the Raspberry Pi is hot. Of course, we're not running the fan right now. So hopefully that alleviates that. So, where are we at on the fan stuff with somebody actively? Was Kevin working on that? Yeah, Kevin has something for that. But we haven't packaged it into something that I think we've, you know, we've exposed it to Ken, so that he can actually write, you know, that level. I will get with Kevin later today and figure that out. I'm not going to put a pin on that until we have the fan working because I guess what I can say is I think we need to have a fan. We're going to listen to music for prolonged periods of time. It doesn't seem to be an issue if you're not listening to music. So Josh and I talked about maybe, maybe it's the amp that's contributing to the heat as well. So getting a heat sink on the amp might help. Yeah, first step is to turn on the fan that we already have though. Yeah, might as well get the fan going. So I'm just going to get weighed on that until we got the fan working. But out of that, I did talk to Ake a little bit about the YouTube skill and when the time comes, you know, he wants to collaborate with us on getting that up to where we want it to be. Right. So, yeah, he, in his words, he said is kind of a proof of concept when Spotify shut down our, our access. So we put, you know, so it needs some work before. But I'm pretty impressed with it so far. Cool. Let's see. Oh, the guys and I reviewed the postcards last night. I'm going to send them to you, Michael, for one last check and then I think I'm ready to print them. Okay. It does. So the way the way we talked about yesterday, it is two separate cards, one for the enhanced kit and one for the regular kit, which I don't think they have separated as a bomb. Different in the bomb yet. I have to object to that. I made a bomb for each one. Oh, yeah. Yes, that's a good point. Yeah, you can make different bombs for this. Okay. Part numbers. Yeah, it's really possible to combine them, but I think it makes sense to just have them be separate. It's not expensive to print. Okay, that's it for me. Great. Let's see. Yeah, so I've had an incredibly frustrating, unproductive day. I'm working on syncing up the volume between the three points of interest. The screen GUI volume, I'll call it the volume skill and the buttons. And so, yeah, the problem is the skill we have doesn't really work with what we've got because it wasn't designed to. I haven't been able to see the mark one skill because I'm not really sure how to go and view with the latest skill deployed on the mark one was, but I suspect that it was intimately tied with the Andrino or Arduino code. And I'm not sure how that communication was being facilitated. So I'm going to have to modify the blue system skill. I'm going to have to modify the enclosure. And I'm pretty sure the blue system skill is what's ultimately driving the GUI. But then I have to tie the actual volume skill in with all of those guys as well. What I can tell you is if I change the volume using the GUI that I believe that's being controlled by the blue system skill. And I believe he's sending out the appropriate volume messages on the bus that are being picked up. So if I use the volume control on the screen, it will change the volume accordingly. But if I change it with anything else, it won't be reflected on the GUI. And I actually updated the ticket so you can see the conditions and what's getting updated and what's not. But once I get a working image tomorrow, I should be able to be productive and not frustrated and probably have all of this working. If not by end of date tomorrow, early Friday, it's not that big a deal. It's just a matter of getting on it and not being locked out of my device. I'm not going to commit any bugs because it doesn't sound like anybody else is having the problems I'm having. But yeah, I'm not real happy with the way that this thing rebooted. And it's a little bit scary that I woke up and it was kind of dead in the water. It was consuming 60, 70% of the CPU is 90% of the memory and just not working. You would say, hey, my craft and one, two, three, four, five, beep, you know what I mean? And anything you did, like what time is it? What time is it? It'd be like 20 seconds later and come back and say, oh, it's this time. And then the scream was acting weird because the, you know, the dimming and the idle or the timeouts were getting hit. It was getting confused. So I'm going to just chalk that up to a bad day at the office. So we call in Florida Tropical Depression. And I'll assume that it's going to magically go away with the next bill. There is a concern that the soft keyboard is sorry guys, configured for American British and not American English or British English and not American English. But that's a minor knit. So I won't bother posting a bug. We're all comfortable with using brick keyboard. And yeah, we'll see if these, if these things persist though, I will on the next bill submit some, some bugs. So that's, that's my status. Sorry, no good news today. On the volume. Yeah, yeah. On the volume front, can we, I think when we talked in our, in our summit that all the volume specific clicks platform, specific stuff for the volume should be any enclosure or the howl or whatever. And the only thing the volume skills should be doing is taking in intent and make pushing a bus message that the right howl will get to. So I'm a little concerned about putting like volume code in the mark two skill and the volume skill and, you know, is there a way we can move towards that. Well, I was going to say that there is only, there's one volume skill to the mark one and pie cropped and every, every platform they all use the same volume skill. So there's only one volume skill. We've removed all the volume code, I think, from the mark two skill already. No. Okay, I'll double check that, but I'm pretty sure it's over in driven from the. response to the GUI volume slider. I thought that we'd moved all that to the enclosure. No, the GUI is completely in the blue system skill. No, no, the pull down menu that's not, that's not in the skill at all that's in the, the Microsoft GUI mark two package. Microsoft GUI mark two package. Where is that? Yeah, yeah. Well, it would be helpful if somebody could point me to that so that I don't spend too much time looking for something I'm not going to find. Well, and I wouldn't, if it's, if it's, if the, the skill, if like if the voice interaction and the buttons are all synced up. And all that we're trying to do, all that we have left is, is getting the slider, the on screen slider synced up, then I think we can ask blue systems to fix that up. That would make my life immensely simpler, but I don't think it's going to be that simple. But yeah, because think about it, that, that code is interacting with the blue system skill via message bus messages. Right. So how are you going to eradicate that whole loop. It's not interact. I'm fairly sure that it's not interacting with the blue system skill. And by the blue system skill, like when we say blue system skill, we mean the mark two skill, right. Yeah, mark two, whatever, not the one that get Chris V did the blue systems mark two skill because if I slide the volume. I see the mark two skill sending out the volume adjustment messages on the bus, which is why I said the slider will control the volume, because those messages are picked up by my enclosure code. Okay, I'll have to go check that. I will focus on the first part of what you just said, and then I will pester you tomorrow for the gooey blue systems interaction piece of it. I will get the buttons. Well, let me put it a different way. I'm done. The buttons and the volume skill work as they're expected to in conjunction with each other. If you go and tell the mark to change the volume. Well, I take that back there's some gaps there but I can button that up pretty quick. The big McGill for me is the interaction with the screen and that volume control piece. I don't I don't have them perfectly in sync like if I tell the volume skill if I say set the volume 35% or whatever, the volume will get set to 35%. If I ask him with the volume set to it'll tell me 35%. The only faux pas there is if I go behind the scenes and change the volume with the buttons. It's not sending a message out the bus to the va so that the volume skill can pick it up and adjust. If I want to do that, or if I want to have modify the volume skill to query it via the message bus before it reports the value, but that's of little concern to me. I can button that up. Once I get locked back in this booker in an hour. What I'm concerned about is the interactions with the screen. And that's just totally foreign to me. And I spent significant time looking for that code and couldn't find it. So I'm not sure it makes sense. The mark one didn't have that skill to interact with so I just don't know. So I will get back with you first thing in the morning on that once I have this working, and we can re re investigate that. Yeah, I agree with gazes plan you know get as far as you can with what you've got and then throw a ticket for blue systems to fix up the gooey part. And I think I'll send the message out the bus when the buttons change the volume so that they have a half a chance of adjusting without having to get too closely tied to core. Can we document somewhere. What parts of the gooey are controlled by the gooey C plus plus code and what parts are not. I think that would help when we're looking for, you know, certain things. What the fine we I certainly couldn't provide that document. Yeah, I just want to pull them in. The pull that menu is the mark mark to do we the microcouple mark to package. And, you know, you should be a link to it anyway just so I can, you know, for grins I can look at it, but I'll do it Michael said I'll get it working with the buttons and the volume skill. And I'll file a ticket, and I'll try to get something in there so that they have a half a chance of resolving without too much work. Yeah, they should be able to follow whatever you do in the volume skill right. What's that. Yeah, they should be able to just follow whatever you've done whatever you whatever changes you make in the volume skill, they should be able to do the same thing, the equivalent thing in the in the pull down menu. Absolutely. Yeah, my point is that there's stuff happening in the gooey that happens within the C plus plus repo and yourself happen within skills and core. If we could know which is where and why that would be awesome. Agreed. Anyway, that's my status update for today. Sorry. Well, yeah, Chris, I think that's a great thing. We, that sounds like another ticket we should put up there for blue systems to answer if they can. All right. So, no update from Kevin. I chatted with them via text earlier today. We're going to get together this afternoon. And can update them. Yes. I spent way too much time yesterday responding to, well, not too much time. I spent a lot of time responding to community comments and questions and stuff around the market to update and and shipping address details and all that sort of stuff. Not a lot to report from me. We are, however, I did add that last ticket in progress for me to So we can get a, a better system of tracking what's, what, what we're doing with the blue system team and and where we're at and what they're working on and what they're waiting on us for and and all that sort of stuff. So, we're going to stick that in the micro gooey mark two repo that we were just talking about. And so back them up to the mode. Yes, where is the art arena code contained for the mark one. I will, I can go find that. I'm just saying, I think things like the art arena repository for posterity sake so we can look at how things used to be done. We can link to the blue systems, gooey code, stuff like that. I don't know that we need to act on it, but just having it somewhere for informational purposes if, if nowhere else a, an Atlassian wiki page. Just so that people have the opportunity to, you know, say, Oh, I need to look at the art arena code to see what it's doing here it is. Oh, I'm wondering what that gooey is that screens what's driving the screen here is the code. I think that we don't know it, but it would be nice to have links to it. I think a lot of the art we don't score and skills. Well there's there's definitely some of it in skills but a lot of it is being done elsewhere. I've noticed, and I'm talking about the actual code that runs on the Arduino well, not just the internet. Yeah, yeah, there's a specific repo for that enclosure dash mark one is what it is. Yeah, so we can just capture that. Last scene page would be awesome. I mean we've talked, we've talked about. I think that comes in in the whole like cleaning up GitHub and, and, you know, understand having a directory of exactly what's there and, and fixing up the naming conventions on things and like all that sort of stuff. I mean, I can, I can start to document stuff. I'll probably, if I, if I do that I'd do it in the public documentation so that, you know, other community members can also find that. Yeah, I don't know that we need anything elaborate. I'm just asking for those two particular pieces because they relate to work I'm doing. But I would imagine that it might relate to some additional work as well as we get into more detailed stuff, but I don't know. I'm just, I'm just saying at least those two would be helpful. So guess. I added a ticket for you. Welcome. Is it in the sprint. 597. Add build date and version number to the home screen. This has come up enough times. It seems to come up, you know, every day or almost every other day. I think it'd be great to know which version we're running on. And maybe even yeah channel and that kind of thing. Yeah, that's all. So the home screen of the Mark two. Yeah, where it just says, you know, right now it's telling me it's 301 Wednesday, February 3rd, you know, and then like in a little tiny font at the bottom. It could just say, you know, 2021.02.03, you know, 42am or whatever, whenever it got built, you know, while we're, while we're dabbing. Yeah, exactly. It could be somewhere permanent up in the top. It could, but then he has to get into the pull down menu and all that kind of junk, right. I'm just I'm thinking something relatively quick and dirty. We still have to define, you know, what the version numbers mean, but a build date I think is unambiguous. And, you know, and I also suggested in the ticket itself, like maybe even putting in like the, the get hash number so that you actually, you know, you can say, Oh, this is exactly what the, you know, code I'm using is. Yeah. Yep. Yeah, so that was something I put on your plate for you. You're welcome. Thank you, sir. May I have another. Oh yeah, I've got. Was that, was that all for you guys? Yeah, yeah. Okay, we can skip me. I've been working on this stuff, but I can't talk about unfortunately for regulatory reasons. So, yeah, all right. Well, seems like maybe a little bit of a rough day, but we'll, you know, it looks like we're on track to maybe wrap this up by Friday or maybe Monday. So let's do that and then get to grape and moaning about all the bugs that we have and get to fixing them. That'll be my faith. That's my favorite sprint. Yeah, like they say Michael, they can't all be gold, right? I take it. I take it everybody's weathering the polar vortex better than myself. It's been freezing down here. It's, I don't know. It's pretty cold. It's like 25 here. It's like that's a seasonally warm for me in this time of year. That's probably warmer than it is down here. Yeah, just went to this weekend. It's going to be like really freaking cold. This weekend it's going to get negative, I think. Like your sweater, Chris. Try it, baby. I'm chiefing up for the rest of it from now until Super Bowl. Let's see if you're wearing me to get on Monday. I'll try it with pride. When your buddy Tom Brady has his way with KC. I hope to beat him earlier this year if we can beat him again in Super Bowl. Any other topics people want to bring up over here? I wanted to bug. I want to put people's ears. And I just thought of it now because I'm doing testing. I'm going to go through the code, code, code tool that we're using for the core unit tests. Also can be supported with the behavioral tests that we run. You run it through coverage, through a coverage utility. So I'm wondering if maybe it would be a good idea to, and this could be a longer term thing. We don't do it right now, but to, you know, we can get code coverage for all of our repos in one place. Maybe it's this code. I hope place and you could just flip between the repos and check the code coverage. Are you saying that we can get code coverage numbers for VK tests? Yeah. That's wonderful. With the allure reports, but those just aren't working the way I would hope they were. So I'm hoping this would be a better solution to code coverage. Yeah. Cause I'm not a big, I don't care about code coverage for unit tests, but for system integration tasks, it's huge. So that would be, that would be a big win. Yeah. So I, I looked into it a little bit today. I didn't really do any work. I just wanted to see if it was possible. And I think it is, um, from what I've read. So, um, yeah. I don't know where to prioritize that or if it's even a priority, but I thought it was interesting. Yeah. I put a ticket in there for, uh, for the VK, uh, for the next VK, um, sprint anyway. Well, just the VK stuff with like the Selene stuff is all behavior tests, all the tests done in writing. Yeah. So that's kind of where I was going with that is, you know, it's just not just core. We can, we could use this for, we can use it for any, you know, any of our other repos that have any sort of testing. That would be awesome if we could have like a, uh, some sort of, uh, like the barometer that says, uh, you know, last week we had 20% VK code coverage. Last week we got 40 and, you know, six months down the road, we have 80 that would be awesome. Yeah. All right. Okay. That sounded like Derek maybe had something. Oh, uh, yeah. If you got a second after we stopped, um, I did want to ask you maybe about one of those things for. You cannot speak up for regulatory reasons. All right. We'll call it there then. Thanks everyone. All right. Thank you.