@djniuss sorry, I don’t understand what you said.
on the computer that as the MM running i had the black screen
if u have black screen, ctrl-shift-i to open the developers env, and then select the console tab and scroll to find errors (red text)…
most of the UI errors like this, will kill the UI (and result in a black screen)
@ezarlive testing… before sending the code
@AdnanAhmed97 on discord, send me the info about how the keypad is wired to the pi… what pins mean what keypad characters
@MM-Hans can u mark your issue resolved please
@singhsoniya4nov he wants the UI on MM, and an external keypad to enter the number(in the near term), show on mirror, button to start and end call. button takes number and sends to modem (I think via serial port ) monitor status from modem, etc… detect end of call…
hm,… mine is like Mykle1’s
address: "0.0.0.0", // Address to listen on, can be:
// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
// - another specific IPv4/6 to listen on a specific interface
// - "", "0.0.0.0", "::" to listen on any interface
// Default, when address config is left out, is "localhost"
port: 8086,
ipWhitelist: [], // Set [] to allow all IP addresses
// or add a specific IPv4 of 192.168.1.5 :
// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
but u get a black screen? that sounds like two versions trying to run at the same time…
did u reboot?
I’ve spent the day looking over the module, and there are a number of bugs that had to be fixed.
the design is synchronous calls to simple-gits module, but simple-gits uses promises under the covers, so everything is actually async, which exposes some potential data corruption
also the module.js overwrites the this.status pointer on each notification from the helper, before checking if the data is useful (behind > 0)… which yanks the data out from under getDom().
and getDom() processes for each good data message, overlaying anything prior… only one module status shows
i am testing fixes for all of that…
@jpiatt open the developers window with
Ctrl-shift-i
Or start mm in dev mode
npm start dev
Select the console tab, and scroll up to find any errors, red rext
@htilburgs not so much numbers, but variable data… the notation
MWB.n.plaats
means the plaats element of the n element of MWB
so the dot notation treats the between dot things as literals…
a number can’t be a variable name literal in this sense…
so, you need the bracket notation [] (and remove the left side dot when u use it this way)