[NASA] Control Beep Sound #144
Labels
help wanted
Extra attention is needed
Comments
|
Hi @hnykda as I understand, the silence mode is a mode where the AC itself is more silent. I dont think this is related to the BEEP. What you can to is to turnoff the BEEP multiple times and look if the log contains the an equal message all the times 0-3sec after you turned it off. |
|
Yeah, I suspected something like that. So here I turned on the AC, and triggered the beep sound with the remote, and started checking logs for up to approx 10-30 seconds from that time. But it seems there is nothing useful? I asked chatgpt to find any inconsistencies, didn't find any, nor I can eyeball anything (it was on a unit with |
|
When you do that via remote I would expect that. Then the Indoor unit receives the remote command and execute it directly without sending any status via BUS. Can you check the same via Smartthing. There must be a message since there is no other way the command could be traval to to Indoor unit. |
|
This is my config: And here I toggle Sound Effect on/off for 5 times on 20.00.00 device. I can hear how the unit beeps when toggling off/on. But I don't see anything new or weird in the logs for 20.00.00. logs_ac-control-beta_logs (2).txt I can see that some packets are skipped though. Will try with |
|
here is a similar try with raw messages. Same, some packets are skipped. Could it be that we can't parse them for whatever reason? When I check the API on https://api.smartthings.com/v1/devices/{device-id}/status, I see that there is this diff:
|
|
What do you mean by skipped? Debug Log should log everything witch could be decoded. But we dont use everything since we dont know the meaning of most of the messages. Can you please make 3 examples where you change the volume from 100 to 0 with smartthings and three logs where that start exactly at the second where you made the change. |
|
Hi, I found message 0x42e5 which is filter clean interval in hours (if it is usefull to anybody), and message 0x4222 which seems to be filter working hours since last cleaning. We need now just the reset filter message to be able to implement all indoor unit filter related functionality and be one step closer to get rid of smartthings. I also found that message 0x8420 is providing energy consumption since last power on, and a custom sensor is working fine for it. Let me know if I can test things to improve the project. |
|
Oh nice findings. Yes I think to only option would be to do it from Smartthings. Since there must be a message witch goes from Smartthings hub to the indoor unit via F1/F2. |
Well, the packet numbers are having gaps in them. That's what I meant. But I expected that what you said is happening - there are more packets flying around but only some are those we parse and show. When you say debug log, do you mean the UART debug log or the raw messages? Because with raw messages I didn't seem to get any more of them. Does MQTT shows all, even the one it can't parse? When I try toggling it and have mqtt logging on, I get e.g. this (which I am having a hard time to figure out): btw. I don't have a hub when I tried that, this is all remotely from cloud. |
|
As far as I know, when you have Smart Thins connected to your AC, then you must have a device like "SAMSUNG | WiFi Interface MIM-H04EN | NASA" connected to your AC. That device connects your AC system to WIFI and makes a bridge or a hub to smartthings. Can you post your device list that gets logged? I assume there must be 3 devices listed. |
Then it has to be built in inside the AC. There was simply a guide in the manual to hold some button on remote for 5 seconds, the AC display showed "AP", and then I could add the (indoor) AC unit to my Smartthings.
Those are devices from here #144 (comment) - two indoor units. And then one outdoor unit. So that's the three you guessed? |
|
My unit, and Daniel's units have WiFi built in. From the service manual (I'm a hardware engineer) for my unit, if you look at connectors descriptions, you will see that the connectors expose more than one UART oof the main processor for different purposes (COM1 is for programming the main processor CN230, COM2 is for the wired remote connector CN340 - this is the white connector from where you can "steal" 12V for the atom, and there is the CN390 connector for external Wi-Fi with MAIN_RX-WIFI_TX and MAIN_TX-WIFI_RX signals) Same signals MAIN_TX-WIFI_RX and MAIN_TX-WIFI_TX can also be found on the display connector CN100. But either way, it may be possible that not all Wi-Fi messages get to F1F2 bus. I will try to "spy" on MAIN_RX-WIFI_TX to see if those messages are also NASA structured or not and if we can decode them on the F1F2 bus. If we can find out what the message is and replicate it on the F1F2 bus, it "might" be processed by the indoor unit even it is not intended for that interface (makes sense to have only one message processing loop in software). We'll see, I'll keep you posted My idea is: if we can use the Wired Remcon, RX and TX, so UART2 if I get it right, we can send messages that are getting 100% without errors to the mai processor, since it should not be possible to have packet collisions. The protocol should be the same, since the remcon is also NASA.
|
|
Wow. This is beyond my understanding, but sounds awesome! Thanks for doing this. Let me know if there is something I could help with. |
|
I tried again with this commit 0e3463e and here is a log when I try turning on the beep via API (I turned it on somewhere after 22:08:04): |
|
Hello @hnykda, I reviewed the log records again, but I couldn't find any logs related to the beep sound. When you try to control the beep sound, pay special attention to the log entries that start with "Undefined s:20.00.00." These logs should be triggered when you control the beep sound via the API or SmartThings. |
|
Hey. Yeah, I get that I am looking for those for |
You’re welcome. I would like you to try one more thing. Please set the variables debug_log_messages and debug_log_undefined_messages to false, and while monitoring the log screen, activate/deactivate the beep sound of the air conditioner through SmartThings. Try this frequently, and if any logs appear on the screen, please send them to me. |
|
Hello @hnykda |
|
Hi @omerfaruk-aran , thanks for trying to help, really appreciated! So I have this config, where the defaults for But when toggling the beep sound, I see nothing in the logs (the first yellow log appears when turning on the AC):
|
|
Hi @hnykda, First of all, we're here to help! It seems that when you try to toggle the beep sound through SmartThings, nothing appears in the logs. This might indicate that the beep sound cannot be controlled via SmartThings and that this setting can only be adjusted via the remote control. It might be a good idea to check if SmartThings supports such specific settings. In my experience, there should be a corresponding NASA packet for every command via SmartThings, but it’s essential to verify if there is a specific parameter for the beep sound. If SmartThings doesn't support this feature, the beep sound may only be controllable through the remote. Could you share a screenshot of the parameter settings section in SmartThings? |
|
Hi. I understand what you are saying, but I think it's simply not true. Here is a screenshot from the Smartthings android app: #121 (comment) , specifically this:
This is what I was toggling when sending you the logs above. I was not doing it via remote, but via smartthings app |
|
@hnykda This is great, when you toggle Sound Effect it should actually show a package. Can you try this at least 10 times, waiting 1 second between turning on/off again and again, and observe the result? |
|
Eh, I can try again, but this is literally what I did above. I waited like 5 seconds at least, and tried that maybe for 5 times? Do you want me to try it again regardless? 😁 |
So, the packages are supposed to arrive, but I don't understand why they haven't arrived yet. Do you have access to the SmartThings API? You can use the following endpoint: |
|
Sure, here it is: I can make API calls and also control it from the mysmarththings. Check it here, where I also record the ESPhome screen: |
|
It's really annoying. We'll keep looking until we find it. If we can't solve it, at worst we can solve it with an API plugin. :) |
|
Good idea. Thanks for your help and let me know if I could help any further. |
|
Hello, in the same vein, there is also the light (lighting) which is below the bit |
|
Any update on this? |
|
I don't know if this helps, but there are addresses here for "buzzer" control on intesis modbus devices. https://www.idx.co.za/wp-content/uploads/2021/01/samsung-nasa-vrf-modbus-user-manual.pdf |
|
I don't know if it helps |
|
@techyporcupine , @htht2001 ; Feedback on Intesis Modbus Device InformationUnfortunately, despite the helpful details in the shared modbus manual for buzzer control addresses, our current integration cannot use these to pinpoint or catch specific control packets for the buzzer in the Samsung system. This is mainly because the Modbus protocol differs from the packet structure we work with in either NASA or non-NASA protocols for Samsung VRF systems. Comments on S-NET Pro Programming CodesThe S-NET Pro configuration settings for the buzzer (highlighted in your screenshots) are intriguing. However, these options only adjust the indoor unit’s configuration via proprietary programming commands. Without additional packet capture or a deeper understanding of the S-NET interface behavior, we cannot utilize these options to intercept or control the buzzer through the communication packets our system processes. In summary, while these are great leads, they unfortunately do not provide us with enough information to identify or generate the control packet for the buzzer. Thank you for your contributions, and if you have further insights or if we manage to intercept packets from S-NET, we could continue this investigation. |
|
This is the logs I sent programming commands to via S-NET And that's the values I sent |
|
(That would be pretty cool if we could sniff the packet structure from S-NET if S-NET actually uses that modbus interface as well in the end) |
|
That’s a great idea, and I think it could provide valuable insights if we manage to sniff the packet structure from S-NET. However, I’m currently very busy working on an SAP Business One add-on related to inflation accounting in Turkey. I’ll definitely look into this further when I have some free time. Thanks for your patience and understanding! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
my ACs have an option to turn on the beeping sound when controlling the AC. I can control this via a remote or via Smarthings app.
I am trying to figure out how to add this, so I found that there are two promising codes in NASA spec. I added custom sensors like this:
but they are always set to 0 and 1, respectively (I can see them being logged), even when I change the settings. So I suspect it's not the correct code (and these are just some hardcoded values).
Any idea how this can be added?
Here is a full log when I was trying to toggle these:
logs_ac-control-beta_logs.txt
It seems to be similar to e.g. me trying to figure out #121 . In that case though, I can't even see/find the right code.
The text was updated successfully, but these errors were encountered: