enaon

like @Techos78 said, the first part is for installing espruino, the second is scripts management. The fists part is one time only, except on the event of a newer espruino image that adds something important, then you may do just step 4 again, but I don't think this will happen, the image is stable. The second part is done by the loader, it will inform you if you have any updates when you connect (in the tab "my apps") and you may apply them by pressing the update button. You do not really have to restart the watch in order to allow for incoming BT connections, if you leave it enabled it will stay enabled. But if you disable it, a restart from the watch menu is needed after selecting the >. icon from the bt menu to enable incoming BT connections for the loader. if you enable the >. icon but do not restart the watch from the info menu to save the changes, the loader will issue a restart to upload the scripts, and since the change is not saved, the watch will disable incoming bt connections on reboot and the loader will hang the connection. So , the easiest way to not worry about all that, is to not disable the incoming bt connections, the >. button, or maybe I will make it auto save the state, so as to not be confusing.

Another note: the speed and the ampere values on the haptic menu serve a third purpose too, they force the screen to stay on when over the limit.

I must rename this menu, it is dual purpose. The vibration part can be toggled by turning the corresponding switch off( gray) or on (blue) in the haptic menu. the dash color coding and visual alerting is fixed, it can not be disabled, it changes based on the values on the haptic menu.

Just a note on that, to make it a bit more clear. when this field is in ampere mode display, it tries to serve a dual purpose: provide a time graph of amps, negative and positive, provide visual feedback that amp usage is over the one that the user has set in the haptic amp menu, regardless if the haptic is on or not. So when the graph turns yellow, it means that you are "now" over the amp limit on the haptc menu. I will do some renaming, it is a bit confusing.

no the se is not compatible. in needs to be an nordic nrf52832, not the hs6620D. I think the p8 is getting out of production, prices will go up and then it will be end of line.

I am sorry, I only just show this post. Yes, there is watchdog enabled and a failsafe mechanism, it stops srcipts loading on start and enters a special state called devmode, that resets BT setup. hold the side button for over 40 seconds, you will feel a buzz at about 35 secs in, release the button 5 seconds after that. (screen will remain off) Scan for the watch from the loader, it will be shown as "espruino-devmode" re install the scripts. tap the side button when finished uploading, it will exit devmode and run the scripts.

Do a swipe down, it will change to the digital dash, you can set the miles/kph there, and it will keep it for the simple dash too. (change to simple dash by swipe down again)

the miles per hour or kilometers per hour is displayed under the speed, mph or kph. Long hold on the speed field to change it. Vibrations may be from the haptic menu, disable everything there, or long hold on the items to set the limits, and please tell me if that solved it.

thank you @Techos78 there was a mistake in the digital dash, it caused low mem and it killed the touch controll, it is now fixed. Also, only for degode wheels, a long touch in the amperage graph will reverce the amp bars, some wheels measure positive and some negative, so change it to yours. Settings are auto saved per wheel slot. For inmotion, total trip, top speed and time is not yet gathered, so I guess what you see is the info from the kingsong wheel, or a mistake. I will fix that and let you know so you can test. For the temperature on the inmotion I use the mos field, I think it is the most important.

Are you maybe using the testing branch? If so, please reload from the normal one. I have pushed some changes, and some fixes, I pushed too early yestreday and there were mistakes. @Techos78 please update too, I changed some things on the imotion too, mileage, clock. amps-bat-alarms log. This is what you can expect from a gotway wheel now, the graph under the speed is the buzzer history. One can change voltage o gw wheels by long hold on the battery in the digital face(67/84/100 volts) Testing is welcome

also a reminder about this message, I am this close to getting the bridge working.

no sniffer, just the watch On the eucbegode.js file, I uncommented this line //print( event.target.value.buffer); so I could have an echo on the cli of every response I got from the wheel when connected. I then went to the ide, https://www.espruino.com/ide/# connected to the watch, uploaded the file so that I can test, connected to the wheel, and did the freerun and alarms tests while looking at the output, trying to find what changes when the buzzer is on, in hopes that something will, and it did. I don't like manuals, I like the manual way 😁 https://forum.electricunicycle.org/topic/22393-vibrator-engine/page/2/?tab=comments#comment-369013

It wasn't I am afraid, I informed seba first thing, he will test too and add it to eucworld. There is no collaboration problem , both seba and the guys from wheellog are fine the way I see it. Lets hope it works and it was just an overlook, better late than never.

If anyone is using a gotway, I think I have good news. A friend of mine had an accident on a gw, what else, he could not hear the buzzer. The wheel came to me for inspection, and I got some motivation to look if the buzzer is reported on the bt level. The wheel is a moster v3, and I found a flag that is raised when the buzzer is on. Anyone that want to test, do the three updates using the site: https://enaon.github.io/eucWatch/p8# the buzzer will cause 4 long haptic feedbacks on the watch, and light up a exclamation mark to the digital dash. Please test if you have some time.

yes, voltage readings on begode are off, but % is ok I believe. Touch once on that area, and it will turn to %, and please let me know if it is ok.

I removed the shutdown menu button because it was draining the battery, I will add it again later if I fix it.

Thanks for testing. Screen-on most of the time, means you have the speed haptic alert very low. The number you set on the speed haptic menu, is not just for the buzzer, it also changes the color of the display, and turns on the screen. It is something like an alarm, ready to see, but maybe if you want better battery life, take it a bit higher. You can enable/disable the buzzer output, but the color change and the screen-on is not selectable yet, it will happen over the limmit. The watch should be able to do over 2 days of riding with sceeen off, and about 3 hours with screen on at 7, so if you set it to always-on at a higher speed, it will last all day. The menus will change to make this simpler, I only write all this for your tests, thanks for doing them this is the part that takes the screen on, if either speed or amprere is over the set values on haptic menu for inmotion, he screen is on too. ps. I am following all the issues you report, I will add them and let you know if you can test. ps2. there is a global gesture you may find useful. A swipe up from bottom left corner, will toggle setbrightness/fullbrigtness, just a quick way to get it to full from any screen, without changing your settings. ps3. This maybe means that you have the 716 controller, there is a version that works even if 816 is selected, but not well. You can update only the handler file from the loader page, and select the 716 to see if it gets any better. https://enaon.github.io/eucWatch/p8#core

It is even simpler. Just long hold the button, it will connect/diconnect, no matter the screen it is on etc. I removed the long hold on screen to connect/disconnect, because it confused some people, nice you told me about the way you connect, you would have thought it didn't work anymore :) I could add it again if you find it more usefull than long press on the side button.

I have pushed some changes, I think I took care most of the good points you made, and made some improvements too. https://streamable.com/yizpuy https://enaon.github.io/eucWatch/p8

NIce. What do you think are the most importand settings that you may want to use on the V11, so that I will put them on the watch?

I pushed some changes: Inmotion V11 should now connect and display basic dash info, no settings yet, please confirm as we do not have a wheel to check. The work on the imotion client was done by @freestyl3r, he now sold his wheel to get a monster sport. Kingsong 18A should display battery correctly. On the simple dash, touching the top right corner will toggle between battery percentage - voltage On the simple dash, long holding on speed will toggle between Kh/h - ml/h On the clock face, long hold on hours will toggle 24 - 12 hour mode. https://enaon.github.io/eucWatch/p8

I am sorry, my mistake, I thought you could not move inside the menus. Ok, so, the time gets lost after power loss, the watch does not have an rtc chip inside. two options: 1.Go to the loader web page, and press the "set time" button, and then the "restart" button, it will set the time. 2.set the watch to work with gadgetbridge , it will auto get the time from the phone. https://github.com/enaon/eucWatch/issues/6 also, do not use the "shutdown" button on the info page on the watch yet, it drains the battery, it needs some work. Just let it be if you don't use it, it will last over a month when doing nothing.

Are you sure the touch is working? Select another controller if not, the menu is a bit strange, but what you describe looks like you do not have touch enabled. @Techos78 A little bit more time

my bad, I thought all KS18 were 84V, I will update and let you know for tomorrow, goodnight

I have been waiting for a watch like that for years myself too. When it comes to the watch, I feel like the wheel is our King, we all are D'Artagnan, and @fanoush, @atc1441 and @gordon are the three Musketeers. If it wasn't for them, especially ATC1441 and fanoush that formed an team that was a joy to follow on their hacking voyages, I would not have gone far by myself. I was just lucky to be on the right place at the right time with the right mentality, so they helped me a lot with everything. I didn't even know any javascript when I started, i tried it because I wanted one and could see it is possible, but I was a newbie. So I got my reward, knowledge and results, no need for anything else. But, if one wants to offer a coffee, do consider one of the three in my credits page, fanoush is Athos