Problems with new nxpanel.be

[viper-666]

For your Autoupdate and fully FTP upload feature I installed the newest nxpanel.be.
But after a reboot I get several error messages on the console and no nxpanel, installnxpanel command works.
Here the console log:
00:00:00.003 HDW: ESP32-D0WD-V3 00:00:00.131 UFS: FlashFS mounted with 288 kB free 00:00:00.260 CFG: Loaded from File, Count 241 00:00:00.276 QPC: Count 1 00:00:00.384 BRY: Berry initialized, RAM used=3849 00:00:00.413 BRY: no 'preinit.be' 00:00:00.421 Project tasmota - NSPanel Version 10.1.0(tasmota)-2_0_1_1(2021-12-08T14:50:20) 00:00:01.485 BRY: Exception> 'syntax_error' - /nxpanel.be:285: 'tcpclient' undeclared (first use in this function) 00:00:01.487 stack traceback: 00:00:01.498 <native>: in native function 00:00:01.498 <unknown source>: in function load00:00:01.499 <unknown source>: in functionload00:00:01.510 <unknown source>: in functionmain00:00:01.511 <unknown source>: in functionload00:00:01.512 <unknown source>: in functionload``

[peepshow-21]

Sure you are on correct versions?

I just downloaded the one from git myself to check and copied to my panel and it boots fine.

did installnxpanel command work? Can the box see the external download URL? If not download yourself and flash as before (locally) with flashnextion command.

It's not not FTP. it's HTTP.

[viper-666]

Yes it is static VERSION = "1.1.1".
And no installnxpanel don't work nspanel/RESULT = {"Command":"Unknown"}

[viper-666]

Ok, found the issue, I have to update tasmota, now it works and also installed automatically the new tft file from your github after the installnxpanel command.

[peepshow-21]

I fixed the infrequent random error when sending messages. I get no errors at all anymore and all.

the error, was a very hard to get buffer overrun. now you just get a little warming and the message get's picked up.

[viper-666]

You mean this errors?
18:56:00.961 MQT: nspanel/RESULT = {"error":{"e:":1,"s":79,"h":"PS"}} 18:56:01.202 MQT: nspanel/RESULT = {"error":{"e:":2,"s":79,"h":"2,"}}

[peepshow-21]

yes, all fixed now

[peepshow-21]

I've just released 1.0.1, so be interesting to see if auto update works. it you have it turned on and want force and update check, before the 24hr check kicks in, type 9998 red button, on the alarm page

[viper-666]

That with 9998 red button don't work.
Also seems there a bug on the alarm page, the first number I pressed will turn red but no beep .

[peepshow-21]

can you send a weblog 4 after your press 9998 red. maybe 15 secs worth after

…

On Wed, 16 Feb 2022 at 19:26, Andre ***@***.***> wrote: That with 9998 red button don't work. Also seems there a bug on the alarm page, the first number I pressed will turn red but no beep . — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKBSYTEVVOBZMO3JZOUKLK3U3P27JANCNFSM5OLK3Z5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[viper-666]

Ok it seems to work but it means 1.0.0.0 was the newest firmware.
20:46:33.755 NXP: Update check for 'release'
20:46:34.056 HTP: Connected in 296 ms, stack low mark 3780
20:46:34.066 NXP: Current version 1.0.0 is latest

[peepshow-21]

have have not checked test auto updates, so its only checking 'release' auto updates not 'testing' it's all testing now, so tick that and it will work. it will then look more like this 20:46:33.755 NXP: Update check for 'testing' 20:46:34.056 HTP: Connected in 296 ms, stack low mark 3780 20:46:34.066 NXP: Current version 1.0.0 newer 1.0.1 availalle kind of thig

…

On Wed, 16 Feb 2022 at 19:51, Andre ***@***.***> wrote: Ok it seems to work but it means 1.0.0.0 was the newest firmware. 20:46:33.755 NXP: Update check for 'release' 20:46:34.056 HTP: Connected in 296 ms, stack low mark 3780 20:46:34.066 NXP: Current version 1.0.0 is latest — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKBSYTFOFRKOJFX7QS7Z5I3U3P54BANCNFSM5OLK3Z5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[viper-666]

With the test button checked it wotks 👍

[viper-666]

Yesterday it updates automatically.
Have you a tipp to what MQTT command I should look to know when the panel reboots and boots from scratch?
I look for changes on the Info3 channel, but in this channel will be only postet if you boot from scratch not if you reboot like the panel doe's after update. So the necessary commands will not be send from my home automation system.

[peepshow-21]

If look in the logs, I think a few different ones are sent, some via tasmota, but nxpanel sends an init one also, best way is reboot yourself, and see what looks useful to you.

…

On Tue, 22 Feb 2022, 13:45 Andre, ***@***.***> wrote: Yesterday it updates automatically. Have you a tipp to what MQTT command I should look to know when the panel reboots and boots from scratch? I look for changes on the Info3 channel, but in this channel will be only postet if you boot from scratch not if you reboot like the panel doe's after update. So the necessary commands will not be send from my home automation system. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKBSYTAYWEQL7LTHOZVAYZLU4OHOLANCNFSM5OLK3Z5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[viper-666]

The "problem" is, that I can't see if the panel has rebooted after a tft update so I missed maybe some informations.

[peepshow-21]

someone else using pxpanel with ibroker here you might be able to help? https://community.openhab.org/t/nxpanel-replacement-firmware-for-sonoff-nspanel/132869/219 as for the other issue, you dont see the {"init".. message sent over mqtt when it restarts?

…

On Tue, 22 Feb 2022 at 14:59, Andre ***@***.***> wrote: The "problem" is, that I can't see if the panel has rebooted after a tft update so I missed maybe some informations. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKBSYTESS27D5VFDEXX3LHDU4OQELANCNFSM5OLK3Z5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>