CMD_SDINFO_EX failed with error: undefined (-148) #379
Comments
|
Ich habe die gleichen Fehlermeldungen, selbes System, aber JS-Controller 4.0.24. Die Fehlermeldungen begannen erst 17 Stunden nach dem Start des Adapters. I have the same error messages, same system, but JS-Controller 4.0.24. However, the error messages began 17 hours after starting the adapter. warn: eusec.0 (109721) Heartbeat check failed for station T8410xxxxxxxxxxxx. Connection seems lost. Try to reconnect... |
|
habe den gleichen fehler immer wen die Kamera eine Bewegung erkennt, habe nun den Adapter ausgeschalet |
|
Habe den selben Fehler, bei mir genau alle 9min59sec. |
|
Ich habe folgenden Fehler, erfolgt alle 5 Minuten. Ich hoffe sehr, dass wir es lösen können.
|
|
Same here |
|
Same for me |
|
eusec.0 | 2023-10-17 22:22:30.142 | error | Station: T8030xxxxxxxxxxx command CMD_SDINFO_EX failed with error: undefined (-148) every one minute. |
|
Same here Station: T8030xxxxx command CMD_SDINFO_EX failed with error: undefined (-148) |
|
same here! 2023-10-31 00:03:13.595 - �[32minfo�[39m: eusec.0 (304976) Disconnected from station T8200N0020280047 |
|
Same error here |
|
Hallo @bropat auch unter der neuen Version v1.2.1 immer noch da selbe Problem. Hello @bropat still having the same problem under the new version v1.2.1.** eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 eusec.0 |
|
Hallo @bropat ich denke das Probelm liegt in der Abfrage der SD Karten Info und hat damit zu tun falls man eine SSD in eine homebase s380 verbaut hat. Bei mir bleiben die drei Datenpunkte im Eusec Adapter unter Station immer leer. Herzliche Grüße Hello @bropat I think the problem lies in the query for the SD card information and has to do with it if you have installed an SSD in a homebase s380. For me, the three data points in the Eusec adapter under station always remain empty. Best regards |
|
Hello @sansonifabio, |
|
Hallo @bropat vielen Dank für deine Antwort. Also es ist ja so das du die Datenpunkte im Eusec Adapter für SD anlegst.
Und ja der Fehler tritt auch auf wenn man die Eufy App öffnet und sich einen Livestream anaschaut oder Aufnahmen löscht. Kann ich irgendwie helfen? Hello @bropat, thank you very much for your answer. So it's like that you create the data points in the Eusec adapter for SD.
And yes, the error also occurs when you open the Eufy app and watch a live stream or delete recordings. Can I help you? |
|
I can try to look at the problem, but for that I need access to a Homebase S380. If you are willing to share it with me, I can try to isolate the problem. |
|
All what I can say is that since the update to version 3.x of HomeBase firmware (2 and 3), the retrieving of storage info is not working anymore. |
@bropat We can do that, but I need an email address from you. Would it be possible to release a version where you can deactivate the log? Because these error messages flood the log file. |
|
I'll get back to you as soon as I have time. |
|
Okay 👍 |
|
I have removed the storage info gathering for the HomeBases and created a pull request. For the T8410 the storage info is gathered correctly. |
|
Hello @PhilippEngler, I'm not a programmer, just a user, could you briefly explain what you did? Hallo @PhilippEngler ich bin kein Programmierer sondern nur User, könntest du kurz erklären was du gemacht hast? |
|
Hello @sansonifabio, I have changed the capability of the HomeBases so that the storage information should not be gathered anymore for these devices. At the moment, the behaviour has not changed, it is nessessary to release a new version of the client and a new version of the ioBroker addon. Best, Philipp |
|
@PhilippEngler Thanks, that sounds very good. This means that when @bropat has time, a new version will be released and the errors will be gone. Now my logs are completely overflowing because I have 4 home bases and I have to pause the adapter during the day. Greetings @PhilippEngler Danke, das hört sich ja sehr gut an. Das bedeutet, das wenn @bropat Zeit hat dann eine neue Version veröffentlicht und dadurch die Fehler weg sind. Jetzt ist das so bei mir die Logs völlig überlaufen da ich 4 Homebase habe tagsüber muss ich den Adapter pausieren. Grüße |
@bropat hier noch ein paar Logs: 2023-11-08 16:35:50.585 debug [P2PClientProtocol.handleData] Handle DATA DATA - Result data received - Detecting correct sequence number [{"stationSN":"T8410P422302BC3B","commandIdName":"CMD_SDINFO_EX","commandId":1144,"seqNumber":6,"newSeqNumber":7,"p2pSeqMappingCount":0}] eusec.0 2023-11-08 16:35:50.585 debug [P2PClientProtocol.handleData] Handle DATA DATA - Received data [{"stationSN":"T8410P422302BC3B","commandIdName":"CMD_SDINFO_EX","commandId":1144,"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0,"resultData":"11750000c3740000","data":"0000000011750000c3740000","seqNumber":8,"p2pDataSeqNumber":7,"offsetDataSeqNumber":0}] eusec.0 2023-11-08 16:35:50.576 debug [P2PClientProtocol.handleData] Handle DATA DATA - Result data received - Detecting correct sequence number [{"stationSN":"T8410P422302BC3B","commandIdName":"CMD_SDINFO_EX","commandId":1144,"seqNumber":5,"newSeqNumber":6,"p2pSeqMappingCount":1}] eusec.0 2023-11-08 16:35:50.576 debug [P2PClientProtocol.handleData] Handle DATA DATA - Received data [{"stationSN":"T8410P422302BC3B","commandIdName":"CMD_SDINFO_EX","commandId":1144,"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0,"resultData":"11750000c3740000","data":"0000000011750000c3740000","seqNumber":8,"p2pDataSeqNumber":7,"offsetDataSeqNumber":0}]` |
|
@sansonifabio: You also have these problems also with the T8410? Do you see the free and used values and are they the same as in the App? If not, which firmwareversion is your T8410 on? |
|
The command for Homebase 3 is different:
{
"account_id":"<REDACTED>",
"cmd":1307,
"mChannel":0,
"mValue3":0,
"payload":{
"version":0.0,
"cmd":11001.0
}
}Response: {
"cmd":1307,
"payload":{
"cmd":11001,
"version":127,
"mIntRet":0,
"msg":"",
"old_storage_label":"",
"cur_storage_label":"",
"body":{
"body_version":1,
"storage_days":1,
"storage_events":2,
"con_video_hours":0,
"format_transaction":"",
"format_errcode":0,
"hdd_info":{
"serial_number":"<REDACTED>",
"disk_path":"/dev/sda",
"disk_size":1048576,
"system_size":2099,
"disk_used":45689,
"video_used":4,
"video_size":900654,
"cur_temperate":27,
"parted_status":1,
"work_status":0,
"hdd_label":"hdd_9A815F3ACC822B1BD17AE9F740D085F1",
"health":0,
"device_module":"CT1000MX500SSD1",
"hdd_type":1
},
"move_disk_info":{
"disk_path":"",
"disk_size":0,
"disk_used":0,
"part_layout_arr":[
],
"data":[
]
},
"emmc_info":{
"disk_nominal":0,
"disk_size":15974,
"system_size":3158,
"disk_used":2792,
"data_used_percent":18,
"swap_size":2048,
"video_size":10435,
"video_used":6,
"data_partition_size":12816,
"eol_percent":0,
"work_status":0,
"health":0
}
}
}
}I first have to re-implement everything for this. |
Wow @bropat |
I have also tested the code suggested above with the Homebase3 and it works without me having to implement the "new interface". ;) |
|
I get the following values: |
|
These are the values of the integrated memory (EMMC). |
|
To make the values of the SSD (extended memory) available, I must of course implement the new interface. |
@bropat Thank you very much for the information and your endless effort, I'm really happy that you managed it. |
|
Created feature request: [Feature request]: Support HB3 extended storage |
bropat
added
fixed in next version
|
@sansonifabio you can remove the sharing. |
|
Hello @bropat , thank you very much for your help and I just deleted the share. |
bropat
added
fixed
and removed
fixed in next version
|
Any estimate when the new version that has this fixed will be released? |
|
Sorry for repeating my question above. Any plans when the update with the fix will be released? |
|
Hello @bropat , I also ask, do you know when you will release the update? I now have 4 home bases and my ioBroker is full of hundreds of errors every day. I know you have a lot to do but it would be nice if you could do it in a timely manner. Hallo @bropat , auch von mir die Frage ob du weißt du wann du das Update freigibst? Herzliche Grüße und vielen Dank |
|
Also, and yes i know you said don't ask for a Time... |
|
The prerequisite for a new release is reaching the milestone |
|
Hallo, Danke im Voraus und beste Grüße |
|
Same Problems here. Thx for your Work. i will try to be patient :-) |
Das würde mich auch interessieren. |
|
eufy-security-client 3.0 was released in march... |
|
Any news on upcoming release of new eusec version? Thank you! |
|
Moin! Gibt es einen Fortschritt zu melden? |
Adapter version
1.1.2 und 1.2.1
JS-Controller version
5.0.12
Node version
18.17.1 und 18.18.0
Operating System type
Linux
Operating system version
Bookworm Debian
Describe the bug
Hello Bropat,
This night Eufy made updates to the home bases and yesterday also to the app 4.7.3_1319.
When I go to the event list on my cell phone, the error messages appear in the ioBroker.
Otherwise the adapter works correctly.
Greetings
Fabio
Hallo Bropat,
diese Nacht hat Eufy Updates gemacht an den Homebases und gestern auch an der App 4.7.3_1319.
Wenn ich an meinen Handy in die Ereignissliste gehe kommen die Fehlermeldumngen im ioBroker.
Sonst arbeitet der Adapter korrekt.
Grüße
Fabio
To reproduce
Screenshots & Logfiles
Additional context
No response
The text was updated successfully, but these errors were encountered: