[Device Report] Panasonic F-YV32NN (ModelType NNW-L) — Missing CommandList / dehumidifier data attached
home-assistant_panasonic_debug_2025-11-12T07-07-08.590Z.log
Device: Panasonic F-YV32NN
ModelType: NNW-L
DeviceType: 4 (Dehumidifier)
Region: Taiwan (ems2.panasonic.com.tw)
Integration version: 2.12.0
Home Assistant Core: 2025.11.x
Mode during capture: 連續除濕 (from Panasonic Smart App)
Observation:
- The device is successfully detected and added under the Panasonic Smart App integration.
- Only humidity sensor shows valid values in HA.
- Other entities (switch/select/humidifier) fail to initialize with IndexError (list index out of range).
Files attached:
- home-assistant_panasonic_debug_2025-11-12T07-07-08.590Z.log (Each file is a direct copy from the integration debug log, with sensitive data such as auth and cptoken redacted.)
- Panasonic app screenshot
- HA dehumidifier feature screenshot
Thank you for reviewing this. Please let me know if more captures in other modes (e.g. Laundry Dry, Quiet) would help.
我試著把CommandType找出對應關係如下 0x00:電源 0=關機,1=開機
0x01:運轉模式 0=連續除濕 1=乾燥防霉(待機) 3=送風模式 4=衣物乾燥 6=濕度設定(透過其它 API 調整 %) 9=智慧節能 10=快速除濕 11=靜音除濕
0x02:倒數關機 (Remaining hours to OFF) N=N 小時後關機
0x07:環境濕度(%RH)
0x09:風向 0=固定 3=自動
0x0D:nanoeX 0=off 1=on
0x0E:風量 0=自動 1=弱 2=中 3=強
0x18:操作提示音 0=on 1=off
0x55:倒數開機(Remaining hours to ON) N=N 小時後開機
0x04:無規律 0x50:無規律
當模式為"連續除濕"時, app設定的目標濕度找不到對應的CommandType
把panasonic_smart_app/smart_app/init.py改成下面後就可以讀取到了。 判斷應該是Panasonic app沒有回傳CommandList, 所以在本地端做一個給NNW-L專用的CommandList。(ChatGPT寫的, 不知道有沒有side effects) init.py
Hi @s900552000,
Can you check every other day? For my machines, sometimes Panasonic does not send all data. Looks like some kind of rate-limiting on their side. I've had my F-YV28NH only getting sensor readings for several hours a day, without a CommandList in the response.
Groetjes,
把panasonic_smart_app/smart_app/init.py改成下面後就可以讀取到了。 判斷應該是Panasonic app沒有回傳CommandList, 所以在本地端做一個給NNW-L專用的CommandList。(ChatGPT寫的, 不知道有沒有side effects) init.py
看起來國際牌的新產品都不會回傳 CommandList,最近的 issue 都在反應類似的情況 (#138 #140 #147)
以專案的角度來看,我們需要先確認原廠是不是都將新產品的 CommandList 放在 app 端而不是從 API 取得,才能決定套件的架構要怎麼調整,但我前陣子一直抽不出時間,也不能確定最近有沒有能量來處理
若目前這樣的改法能解決你的問題的話就是好解法 👍
+1