# Meeting Transcription

  Meeting started: 6/29/2026, 2:49:00 PM
  Duration: 35 minutes
  Participants: Aaron Tushabe, Hillary Arinda

  [View original transcript](https://app.tactiq.io/api/2/u/m/r/OkqE5FGNCvwfDOtDS265?o=txt)

    

  

  
    ## Highlights

    > 05:51 Aaron Tushabe: issue.
> 06:41 Hillary Arinda: another issue at least you're getting it in the log store your your almost
> 07:07 Hillary Arinda: Now the issue was the way edges I registered now.
> 08:12 Hillary Arinda: Yeah, so there are two sources one in the way back in control from the community because I didn't trust this guy. I wanted to get as much information as we can from the community but before you fix something you wonder how is the community like you say you would refers to wonder how is the community dealing with this issue, and then you get ideas on on the why and what to do. Yeah, so those were
> 12:01 Hillary Arinda: But it's something we could get into for the long term it makes sense but for now maybe not okay for now my goal was to get things working and then we think
> 16:05 Aaron Tushabe: doing summary danger on
> 24:46 Hillary Arinda: one I can confirm I was even saying it. Yeah, the issue is when is even back?
> 24:48 Aaron Tushabe: Okay then. Okay, then, I think those two areas. I want then it seems like this last PR is on replay, and it's it's can be a separent one. It's definitely a separate issue
> 25:01 Aaron Tushabe: okay.
> 30:10 Hillary Arinda: So that's that's really where I am at tonight. I want to finalize on this third
> 32:59 Hillary Arinda: and okay, I will take it out for me to more than Or tonight we'll see.
> 33:04 Aaron Tushabe: Card more you might tonight you you being me when you you're ready.
> 34:34 Aaron Tushabe: it. I'll check it that one I can check and I think by by the time we connect this to night outfit.
> 34:42 Hillary Arinda: Okay yeah, but just to be clear. I think it's on the stop bit that could be the issue because I fail into it and it took me 20 minutes.

  ## Transcript

  00:00 Aaron Tushabe: him
00:03 Hillary Arinda: Yes, I can hear you.
00:06 Aaron Tushabe: I found nearly free energy needs to launch everywhere. And then the guys are using it generator and it takes a good humanity to come on. When power comes back I imagine it would also introduce another great but we are back now.
00:30 Hillary Arinda: Man I had to do what I had to buy a guts and things in India is to get I had to back a ups for the router. It's really works. We need to get it for the pies.
00:39 Aaron Tushabe: Hey, that's supposed you send the link the link for that one, but you guys also
00:40 Hillary Arinda: Yeah.
00:46 Aaron Tushabe: have a generator backup generator.
00:49 Hillary Arinda: hmm
00:52 Aaron Tushabe: But the backup generator is connected. Can I forgot how it's you're not mitted
00:53 Aaron Tushabe: Hi, I'm transcribing this call with my Tactiq AI Extension. https://tactiq.io/r/transcribing
00:58 Aaron Tushabe: for it you pay a flat fee?
01:02 Hillary Arinda: I have I don't really know what happens. I'll be honest. Yeah.
01:09 Aaron Tushabe: Like you so you don't know if it if your your computer continues running when the generator is run.
01:18 Hillary Arinda: is by the utility run by Italy but we have only one meter so that means the generator is put under maintenance fees because we payment Ministries Bantu
01:30 Aaron Tushabe: That's flexible, but also if they guys didn't place the generator well it can run your commitment. It's just that the utility know that power is not coming
01:37 Hillary Arinda: No, they cannot that.
01:40 Aaron Tushabe: from from.
01:42 Hillary Arinda: These guys they are.
01:47 Aaron Tushabe: It would be like it wouldn't cost them more it. Would it would it would be
01:47 Hillary Arinda: they would
01:50 Aaron Tushabe: simple simpler. like anyway
01:53 Hillary Arinda: Not do the cost would cost the customers I mean no they would.
01:56 Aaron Tushabe: Yes, it would cost you the customer more.
02:01 Hillary Arinda: They would lose money as well like okay. They will not get that many guys anybody that would why would they?
02:08 Aaron Tushabe: Yes, they wouldn't yes, but for them. They already charging you fees the problem was that the technician who connected that generator could not find an easy way to connect directly to you behind your meters so they put it they put it in
02:20 Hillary Arinda: Know but but I don't expect such global air as in India in such a country. You
02:23 Aaron Tushabe: front of your meters.
02:29 Hillary Arinda: know I honestly do not expect yeah.
02:31 Aaron Tushabe: You know yeah, and if the priorities are not very bad. They are like you're just paying a few hours extract. I don't know it depends on customers if they assume they're kind of customers were not price sensitive. They're like connect.
02:48 Hillary Arinda: that one is not here in India everyone is
02:52 Aaron Tushabe: the brace
02:54 Hillary Arinda: the most precisive country Anyway, let's move on let's move on let's move one.
03:00 Aaron Tushabe: let but more than the stressing us for 20K
03:07 Hillary Arinda: And another one.
03:11 Aaron Tushabe: And I think as you still prices cities. Kelly you are just highlighted to issues. Not that yeah the question I asked was that for the the 2020 2026.6 back end is expecting both an API key and they and then ID from the edge.
03:38 Hillary Arinda: Yes.
03:40 Aaron Tushabe: Okay, but your age is only sending and if it's only sending the API key.
03:48 Hillary Arinda: Previously, yes.
03:52 Aaron Tushabe: okay but
03:53 Hillary Arinda: Yeah, so that's the first we are.
03:56 Aaron Tushabe: Wait wait does that need to be appear because PR to watch to the edge?
04:01 Hillary Arinda: Yeah, yeah most of the code. Yes, yes.
04:01 Aaron Tushabe: like oh like 20 20 26 age nesbians less than two not to send to send an Ida But guys how did this thing pass this thing?
04:14 Hillary Arinda: I did not that's why I took so much time but then I still ended up with the same solution. I said this makes sense for sure yeah and the code changes were not
04:21 Aaron Tushabe: okay
04:25 Hillary Arinda: allotted. That's a good news. Also. They are interfaces as well set topics so we just needed. I'd like one helper and one call to the help. I'm that's it. Okay, so that was the first year so just to it. hid and Wrapping it so remember there were two way first of all add an hid and then to wrap it in a what and and RPC connection kind of notification such that because that's what back end is expecting to receive so we did that and one is.
05:15 Hillary Arinda: 90 second one is a
05:18 Aaron Tushabe: Wait wait that one is ready by ready humidity is up or it is on your machine.
05:25 Hillary Arinda: Machine I have not I did not have to close four contain make the pr, but I thought we should first discuss before I go ahead. I mean I need it first it tests into ende. Yeah. No need direction. No need to rush yes.
05:43 Aaron Tushabe: Okay okay and and then did those two pairs seem to fix the of edges of line
05:45 Hillary Arinda: Yes.
05:51 Aaron Tushabe: issue.
05:51 Hillary Arinda: yeah
05:53 Aaron Tushabe: Nice nice okay.
05:56 Hillary Arinda: After discussing the players will take us to where we really actually are now and then I think most of those questions will have been answered so the next one so now we we finally are able to send a message and wrap it well to be received, but now another problem came.
06:19 Aaron Tushabe: Sorry, we leave that when you say well, it would send them a message that means if like the data coming in on let's say energy. It's showing up on the UI on
06:30 Hillary Arinda: Yes.
06:33 Aaron Tushabe: backend coming in from the namita. It's showing up on the UI
06:34 Hillary Arinda: No guys. Yeah, no Australian up in the logs, but not on the UI so there was
06:38 Aaron Tushabe: okay
06:41 Hillary Arinda: another issue at least you're getting it in the log store your your almost
06:46 Aaron Tushabe: You know it's reaching it's reaching yes.
06:46 Hillary Arinda: there. Yeah, the reaching. So now I need to find out why isn't it being displayed at least now? I can I'm
06:51 Aaron Tushabe: okay
06:55 Hillary Arinda: being shown I Am What I Am online when you check back and the energy values are reaching but on the UI you have zero so what's going on?
07:06 Aaron Tushabe: and then
07:07 Hillary Arinda: Now the issue was the way edges I registered now.
07:14 Aaron Tushabe: okay
07:18 Hillary Arinda: This is something we need to discuss as well the way most users probably use it currently like the latest version or maybe it hasn't been tested is that they is another gateway and Aggregate I get way in between age and backend a little is to aggregate all edges and send messages. You know at once basically it will it's the one that does the registry for the edges and then reports to the backend. That's the that's the setup that was working and that's the setup that backend expects. But in our setup our setup.
08:03 Aaron Tushabe: Where are we getting this information from like this this gateway in the middle this this aggregator in the middle setup?
08:12 Hillary Arinda: Yeah, so there are two sources one in the way back in control from the community because I didn't trust this guy. I wanted to get as much information as we can from the community but before you fix something you wonder how is the community like you say you would refers to wonder how is the community dealing with this issue, and then you get ideas on on the why and what to do. Yeah, so those were
08:47 Hillary Arinda: my two sources but of course now that you have an idea you can also go under those an independent verification to see if actually it's true or there's something I'm missing something Claude is missing not me. Yeah, yeah.
09:05 Aaron Tushabe: okay
09:07 Hillary Arinda: So, what would happen was? Like I said. In our setup we are supposed to we connect our ages directly to back in but in the big asset app where there are many ages that should be what that should be an aggregate. So Our Data yeah, Our Data was being thrown away.
09:39 Aaron Tushabe: Because we have multiple because because that the thing has multiple can see you
09:39 Hillary Arinda: And this is what took me a more time.
09:44 Aaron Tushabe: have multiple edges set up.
09:47 Hillary Arinda: No, it cannot recognize your age actually doesn't think your age is connected which was a bit confusing basically to get the data. It throws it away because it has not has not acknowledge your age because the one we supposed to report the edges someone bigger. Not you you do not report for yourself. You're not you
10:08 Aaron Tushabe: and I can answer that be a
10:09 Hillary Arinda: elevate your spells. Yes. That's yeah, which I thought is a good design.
10:14 Aaron Tushabe: Is another it's easy to separate deployable.
10:20 Hillary Arinda: Yeah, it's separate I didn't even ask much about it because I did not want to get into it. So I'm like now me. I just want to connect how do we connect? Yeah, so basically. We had to create another way of rejestering an individual Edge device to the back end. without going through the aggregate
10:47 Aaron Tushabe: hmm that's the next that's the other PR
10:54 Hillary Arinda: Mmm. That's the other PR
10:59 Aaron Tushabe: at PR sounds like community discussion because
11:04 Hillary Arinda: Icked me that much time but still brought me back to the same. I said why let's continue but they did not make sense I know but it made sense like probably in the new in the newer deployment no one has really tested it. Big time here now as you thought process.
11:27 Aaron Tushabe: okay Okay um do you think we're going to have?
11:30 Hillary Arinda: hmm
11:35 Aaron Tushabe: I'm trying to be like and we're going to run into multiple edges like we we are not we we don't want to be spinning up a backend for. Like with sounds like we're going to be the multiple.
11:50 Hillary Arinda: No, yeah, we're going to be using multiple agents definitely.
11:55 Aaron Tushabe: So should we be trying to use their aggregate?
12:01 Hillary Arinda: But it's something we could get into for the long term it makes sense but for now maybe not okay for now my goal was to get things working and then we think
12:11 Hillary Arinda: about what to change.
12:11 Aaron Tushabe: Okay when we come about it. I am trying to see their.
12:15 Hillary Arinda: yeah
12:22 Aaron Tushabe: EMS demo on the same coin upon But you believe to this down. I'm trying to pull up their demand I remember either they had. Incredible I think nowaday settled for some other game. I'm good. I'm not seeing it. I love to look for it so I thinking we push we push now this this PR that will add ability to register a single Edge directly to back and Yeah, yeah, let's put it in. I think I think I agree. Let's put it in. Let's put it in and see what they say.
13:46 Hillary Arinda: okay
13:48 Aaron Tushabe: How did the end-to-end test go like it with that with?
13:52 Hillary Arinda: okay, so we have we have one more PR
13:58 Aaron Tushabe: A third one so wait, what what what happened after that the second year you started seeing data on on the on the graph energi data on the graph or we still on energy data in dialogues.
14:20 Hillary Arinda: Just give me one second.
14:21 Aaron Tushabe: okay
14:31 Hillary Arinda: I need to just make a quick transaction here just image again.
14:53 Hillary Arinda: That's the second please do it.
15:15 Aaron Tushabe: okay, I'm
15:33 Hillary Arinda: Oh okay.
16:05 Aaron Tushabe: doing summary danger on
16:09 Hillary Arinda: mmm
16:09 Aaron Tushabe: Our default J to appreciate. with ox
16:51 Hillary Arinda: Okay, I'm back.
16:58 Aaron Tushabe: Asking what what happened after the second PR because that for the first year
17:01 Hillary Arinda: hmm
17:05 Aaron Tushabe: was seeing energy data in logs, what happened after the second year.
17:10 Hillary Arinda: Yeah, the energy logs the second PR fixes everything almost into end. but feeling for influx While still not done. Yeah, actually that part is not yet done. It's what I'm right now on yeah.
17:41 Aaron Tushabe: By not yet done you mean not yet tested or tested and it's still fail.
17:45 Hillary Arinda: Not yet, not implemented. They're just stabs. for influx
17:52 Aaron Tushabe: So sorry, what do you mean that stamps for instance?
17:56 Hillary Arinda: They are just methods that are not implemented yet.
18:00 Aaron Tushabe: No, but I mean what how does it behave as is have you tested it?
18:06 Hillary Arinda: Yeah, I know it doesn't back fuel in short.
18:10 Aaron Tushabe: Like power goes off and and we we are back on and the gaps remain.
18:11 Hillary Arinda: Yes. Yeah, basically, you just turn off just turn off back end. Yes, just kind of
18:19 Aaron Tushabe: oh, yeah, sorry connection is
18:23 Hillary Arinda: backend. Keep the meter on then turn it back on back filling the the like we'll see that edge actually fires the data. Yes. Yes.
18:36 Aaron Tushabe: That but that's not that I would testing properly Hillary like you don't turn off back end.
18:42 Hillary Arinda: No, because the auntie backend is where the problem is see button is the one receiving the data. So if you turn it off it will not receive anything right.
18:52 Aaron Tushabe: What do you mean turn it? How do you how are you simulate in this turning off of backends?
18:58 Hillary Arinda: Just kind of the service.
18:58 Aaron Tushabe: Are you searching down the hits? You are shutting down the VM
19:03 Hillary Arinda: I know not the real the service itself the open EMF
19:09 Aaron Tushabe: m but for me that I think the things I think we're trying to simulate is that backend stays alive what happens is that you unplugged you unplug Wi-Fi
19:16 Hillary Arinda: no if
19:21 Aaron Tushabe: Really you you unplug that the edge you completely unplugged power has gone off.
19:27 Hillary Arinda: You see the same thing really at the end of the day what you want to kill is the web socket connection. there are so many ways of Killing It
19:36 Aaron Tushabe: Okay now marketing. Not sure what what do they think we want to test because in some like we want to test a scenario where age kept running? Locally it had no internet connection, but it kept real that's scenario one maybe let's see is down here that scenario one is that the edge loses internet connection? But people are still power is still being used data is blown that data needs to
20:05 Hillary Arinda: So it's like this.
20:05 Aaron Tushabe: be replaced replayed back when that internet connection is restored, but all the
20:09 Hillary Arinda: Yeah, yeah.
20:12 Aaron Tushabe: services were still running the service never stopped running it was just internet connection that dropped like the meter kept putting data in our dj4.
20:24 Hillary Arinda: correct
20:25 Aaron Tushabe: that's in a real one is so
20:26 Hillary Arinda: And that's the only constant the one constant is keep our 4DJ storing data. You can do anything yes, you can turn off Wi-Fi that's fine, but you can also turn
20:36 Aaron Tushabe: current data
20:41 Hillary Arinda: off you can also turn off back in that's another way. because if you cannot but
20:48 Aaron Tushabe: I guess I'm like turning off back and yeah the yeah that connection or the fail
20:52 Hillary Arinda: this age
20:55 Aaron Tushabe: also yes.
20:56 Hillary Arinda: Yeah, it would fail and the thing is Edge keeps all these to try and change.
20:59 Aaron Tushabe: But I think for me that the different seems like if we turn off back ends the
21:04 Hillary Arinda: hmm
21:05 Aaron Tushabe: edgy still sending data that data is just not receiving a positive response.
21:11 Hillary Arinda: And 90 because remember it transcript websocket before it's in so in the websocket breaks automatically store as that as a fail and it keeps storing those notifications that all these data has not been sent.
21:27 Aaron Tushabe: Okay and you're feeling confident that killing that tells bricks that websocket when you kill back into that websocket bricks not sure our website.
21:36 Hillary Arinda: I mean, it's like it's more like any other HTTP connection you send the request you never get a response. That's broken right. Hmm. Yeah, so it keeps so it's a family here just that here the connection is.
21:54 Aaron Tushabe: Even it sounds like it's situation that will send that request and the requests to just came out. because it's spending waiting some sort of response and
22:09 Hillary Arinda: Yeah, that could be one way to look at it, but the result is the same ideally.
22:16 Aaron Tushabe: Okay okay, so what what you tested was killing killing the back ending it back
22:17 Hillary Arinda: Yes, the result is.
22:24 Aaron Tushabe: on will it back feel data?
22:27 Hillary Arinda: correct
22:29 Aaron Tushabe: So that that would require that age remembers the last data. I sent that it didn't get a response and then replay that data and it seems like edges failing to do that so this next PR is like.
22:41 Hillary Arinda: And no no, no, it's doing that that's exactly that's exactly how it works.
22:47 Aaron Tushabe: Yeah, but it sounds it's it's not doing it.
22:48 Hillary Arinda: It looks like it it sends it it's just no it's doing it the pr is not an edge.
22:53 Aaron Tushabe: hmm the prison Like it looks like backend. It's failing to to receive the replay. when
23:09 Hillary Arinda: No like I say it has the methods to receive but they are not implemented. It's something I need to look into deeper so on this one. I need I need yes method
23:16 Aaron Tushabe: like in the court in Accord it looks like it has them it's
23:21 Hillary Arinda: yes, the method is there is
23:24 Aaron Tushabe: This is the code you pulled down the most recent chords.
23:28 Hillary Arinda: Yeah, 2026 yes, not true. So this is the last thing I did but I'm not exclusively looked at it so put the question mark on this on that's the one
23:38 Aaron Tushabe: Okay okay, then, I think let's if we can push this to PR as a I can be there and
23:40 Hillary Arinda: thing I need to accomplish and then we'll be done. Yeah.
23:48 Aaron Tushabe: we explain them because what they are fixing is pretty separate from replaced functionality. They are fixing just Able to to stream to send to send the data directly from an edge.
24:04 Hillary Arinda: The data is being sent.
24:07 Aaron Tushabe: No, no, they're fixing back and being able to receive data from an edge device right.
24:13 Hillary Arinda: Hey yeah, yeah.
24:14 Aaron Tushabe: Direct yes, yes a big thing that so the first two parent speaks being able to register the one being able to register that device with this new requirements, then then being able to somehow push that data beyond their logs to the dashboard. Yeah to the UI and all the way into the influx for the back end.
24:33 Hillary Arinda: I Yeah, so yeah for real-time date because for real-time data it goes to influx at
24:40 Aaron Tushabe: okay so that's
24:46 Hillary Arinda: one I can confirm I was even saying it. Yeah, the issue is when is even back?
24:48 Aaron Tushabe: Okay then. Okay, then, I think those two areas. I want then it seems like this last PR is on replay, and it's it's can be a separent one. It's definitely a separate issue
24:58 Hillary Arinda: yeah
25:01 Aaron Tushabe: okay.
25:02 Hillary Arinda: Yeah, they are three separate issues and well distinct. Just one cat Boxing Day there's not going to have a semi resolution as as real-time data real-time data is resolution is one second and for it. There is no aggregator if I remember correctly like you see how DJ works it aggregates and it does what not all that stuff but can doesn't do that it receives and just so as every second.
25:29 Aaron Tushabe: Great great but even by the time back end receives data. It's already coming in at if it's coming from an Rd Jeff whatever.
25:38 Hillary Arinda: No, no no no no no no no that's two things. They're two things. We can we shouldn't mix them. When there is the web socket. There's a web socket connection that is for real time data. It's streaming data okay every second no no no no no no no no no no no is only for replaying.
25:54 Aaron Tushabe: it's not coming from from the they are whatever back and
26:05 Hillary Arinda: Yeah, yeah.
26:06 Aaron Tushabe: okay So the website is streaming is streaming real data, so would so anyway so replay data is going to be our DJ data and that is not it's meant to be as granular as
26:15 Hillary Arinda: micro Yes, but with low resolution.
26:26 Aaron Tushabe: lowa, it was yeah the lord. It's not yes, it's not not resolution. Yes.
26:26 Hillary Arinda: It's it has no resolution because remember it's aggregated. It's aggregated but now in that's the thing that is still confusing me. Why we don't have aggregated
26:34 Aaron Tushabe: okay
26:39 Hillary Arinda: data on the back end and I don't have clear answers yet. I need to go back and look at the logic again.
26:45 Aaron Tushabe: Ah, what do you mean? Why would we don't have aggregated data because it came straight from there, so they were socket the real.
26:54 Hillary Arinda: No, they no they still guy I read somewhere yes somewhere. It's somewhere
26:56 Aaron Tushabe: Or like why it's not implemented.
27:02 Hillary Arinda: implemented but not directly it's like we may have to do our own service that does aggregation why you get
27:09 Aaron Tushabe: Yeah, yeah, but also when I'm thinking about it from a requirements perspective Hillary you want to give users the option like when if you have if your managing to stream the an aggregated data you you don't want to lock people in into aggregated data. You want them to have the option if especially if they are streaming to something on a server that has all the resources. They want while
27:36 Hillary Arinda: Why do you agreement on RR why you lock them on this other side?
27:37 Aaron Tushabe: locally Because of the limited resources you expect to an edge.
27:41 Hillary Arinda: On replay.
27:47 Aaron Tushabe: And really you need to lock them in if if you wanted if they wanted to have real
27:47 Hillary Arinda: But now but then when you're replaying.
27:51 Aaron Tushabe: if they wanted to have whatever they would have to use influx and maybe that's why implex exists you didn't lock them, but if they recognize their edges a week then they use the are the whatever you need you didn't block them, but now it's
28:06 Hillary Arinda: Okay yeah that makes sense that makes sense, but then I have one question.
28:10 Aaron Tushabe: open to them if they decide they want to aggregate, then. They write they aggregate us that way they want so you don't force awhile community into a specific aggregation.
28:21 Hillary Arinda: Okay I agree, but then one more question why then why I replay aggregated data onto granuary and data.
28:32 Aaron Tushabe: Why replay aggregate because you've made the choice of whatever down here if you admit the choice of influxia? I think it would Replay from influx and you would
28:43 Hillary Arinda: But you see influx is not implemented down here. That's why we went for RR for
28:45 Aaron Tushabe: have. that
28:48 Hillary Arinda: DJ we implement it yourself.
28:50 Aaron Tushabe: what do you mean it's Yes, you would implement it yourself hey yeah that means that's incomplete.
28:55 Hillary Arinda: okay okay
28:57 Aaron Tushabe: Yeah, it's also incomplete. It's also incomplete from what I'm reading about the
29:01 Hillary Arinda: The implement but you're right you implement it yourself if you want to do
29:03 Aaron Tushabe: R&D it seems like this file best system it has better persistence like for
29:06 Hillary Arinda: influx. performance
29:12 Aaron Tushabe: something that we're trying to make sure that it's It reliably records this data in case of of issues things like that.
29:21 Hillary Arinda: Yeah, like you cannot have yeah. It's one system. You cannot have say a dB failing something okay like you see when you have influx is really independent from from backend so back independence, but yeah, but for our it's one
29:35 Aaron Tushabe: Yes, yes another service. Yes.
29:40 Hillary Arinda: wholeservice. I think some there's more reliability I would say. okay, I think I think I think I
29:45 Aaron Tushabe: and yes, it's more reliability and not
29:50 Hillary Arinda: I think the hotel process is okay. I would probably have done the same. yeah
29:58 Aaron Tushabe: Yeah, but yeah, I think that trade off. We have here is that replay data is going to be aggregated data and I think that tradeoff is okay. I think I tried graph is okay.
30:07 Hillary Arinda: It's okay.
30:10 Aaron Tushabe: I think that.
30:10 Hillary Arinda: So that's that's really where I am at tonight. I want to finalize on this third
30:16 Hillary Arinda: one of resending data and then I can make the pr sounds good.
30:23 Aaron Tushabe: Okay yeah, yeah, I would say make that PR no I would say if you can send those first to it. I also pull them down. I can do some testing myself and also respond respond on the
30:37 Hillary Arinda: But Wait you can you can okay
30:45 Aaron Tushabe: Like go ahead and push the pr on the project. I will likely respond before
30:49 Hillary Arinda: okay
30:50 Aaron Tushabe: maintain as respond and I also I also run them but those two ways so that's I can check the case of and I can technically still work with stop the data. No. Because the real time yeah, so I can just enable some CSV and and look at see if
31:05 Hillary Arinda: Yeah, yeah.
31:13 Aaron Tushabe: the data comes through and I particularly yeah, because I think what I'm trying
31:16 Hillary Arinda: okay
31:17 Aaron Tushabe: to work with is that 2020 26.6 Edge but the patched back into that UV your you you've worked on.
31:31 Hillary Arinda: One some okay that will be at night on some through with that already you know.
31:38 Aaron Tushabe: The Kali but I I think for sure this we are going to have to to go and buy one the both of those sound like I was wondering whether those two should be combined but no I think let them be too separate and and I start start tagging the maintainers to help us review and approved and just let me know when those two are up and I also pull them down and test them and and then tag maintain us.
32:06 Hillary Arinda: okay okay sure Thanks.
32:13 Aaron Tushabe: As usual open source projects are turning out to be more here even. But hopefully these pixels are yeah. Yeah, but then it I guess the benefits. I see like this guys. Already have spent time to think through that the age having these two options that would have taken us a while to realize that yeah influx
32:32 Hillary Arinda: yeah exactly exactly
32:36 Aaron Tushabe: as its advantages, but after it fails in production is when we start trying to compose something like are the j5.
32:49 Hillary Arinda: Okay so do anything be sure to send me that transcript or the recording but preferably the transcript.
32:57 Aaron Tushabe: Let me send the transcript.
32:59 Hillary Arinda: and okay, I will take it out for me to more than Or tonight we'll see.
33:04 Aaron Tushabe: Card more you might tonight you you being me when you you're ready.
33:08 Hillary Arinda: okay, Kylie Okay and then on your pie. I think how do you remember why you fail to receive data from the meter by any chance?
33:22 Aaron Tushabe: No, I I think we had we had I think I kept thinking it's that the connection of the the wires and I kept trying to screw on.
33:29 Hillary Arinda: I think it's a configuration. I fell into the same scenario so I think in yeah in the config in the config, but you help me verify this in the config. I think the configuration is 8 parity bits. You know eight wide eight data bits then
33:49 Aaron Tushabe: What moderate of a moderate something like that?
33:51 Hillary Arinda: then so there's something along the lines of instead of eight and two in our config of there is eight N1 yet our meter are most likely 8 into so you have to change the convig to to the stock beat to be equal to 2.
34:12 Aaron Tushabe: it 8 and
34:13 Hillary Arinda: So the issues on top beat.
34:14 Aaron Tushabe: Okay, I'll check that if is that the configuration your your age right now has
34:17 Hillary Arinda: Yeah, stop bit yeah.
34:21 Aaron Tushabe: in git in the report as I can just copy your configuration. I can literally stop
34:25 Hillary Arinda: I Yeah, I changed it to.
34:28 Aaron Tushabe: your configuration and build from the and also you this recent okay. I'll check
34:32 Hillary Arinda: okay
34:34 Aaron Tushabe: it. I'll check it that one I can check and I think by by the time we connect this to night outfit.
34:42 Hillary Arinda: Okay yeah, but just to be clear. I think it's on the stop bit that could be the issue because I fail into it and it took me 20 minutes.
34:55 Aaron Tushabe: Wondering how you fail into it because you had the working state. How did it
34:57 Hillary Arinda: yeah No, because I reset exactly because we reset everything I'm like now. Let's
35:01 Aaron Tushabe: suddenly become?
35:05 Hillary Arinda: start again so if you see.
35:10 Aaron Tushabe: Big leads to stay beats so that we know the last working statement. Just work okay transcript on bookstack and send you.
35:17 Hillary Arinda: yeah okay kind of things
35:27 Aaron Tushabe: Hello, thank you.
35:29 Hillary Arinda: right