Mengubah Indikator Suhu Fahrenheit ke Celcius pada AC Gree

Remote

Salah satu remote AC merk yang ada dirumah sepertinya secara tidak sengaja berubah pengaturannya pada indikator suhu. Yang biasanya menggunakan satuan Celcius, tiba-tiba berubah menjadi Fahrenheit. Sebagai yang sudah terlalu terbiasa dengan satuan Celcius, tentu ini sedikit merepotkan.

Melakukan penghitungan rumus konversi dari Fahrenheit ke Celcius setiap kali ingin mengatur suhu tentu bukan pilihan yang bijak. Mungkin jadi sedikit lebih cerdas karena jadi belajar matematika, tapi saya memilih tidak.

Untuk mengembalikan ke mode Celcius — dan nanti bisa untuk kembali lagi ke Fahrenheight — caranya cukup mudah:

  1. Pastikan posisi AC dalam keadaan mati
  2. Tekan tombol “Mode” dan “minus” (untuk menurunkan suhu) secara bersamaan.
  3. Indikator akan langsung berubah.

Kalau ternyata ada sebab lain di AC Gree misal lalu muncul kode , bisa merujuk referensi kode error pada AC Gree.

WP-CLI Error: PHP Deprecated: implode(): Passing glue string after array is deprecated.

I use WP-CLI to maintain my WordPress sites. It’s simple, it handy, and it works without any issues.

For example, I can updates all my and (if updates are available) by executing wp theme update --all and wp plugin update --all. If core engine is available, I only need to run wp core update.

But there is a problem when I update recently. Running wp plugin update --all to update all available plugin updates give me an :

PHP Notice:  Trying to access array offset on value of type null in phar:///usr/local/bin/wp/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663
Notice: Trying to access array offset on value of type null in phar:///usr/local/bin/wp/vendor/wp-cli/extension-command/src/Plugin_Command.php on line 663

But, all updatable plugins were updated successfully. I tried to find the solutions, but I found nothing. I also try to use the nightly version via wp update --nightly, but still no luck.

Here are my wp --info

OS: Linux 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64
Shell: /bin/bash
PHP binary: /usr/bin/php7.4
PHP version: 7.4.3
php.ini used: /etc/php/7.4/cli/php.ini
MySQL binary: /usr/bin/mysql
MySQL version: mysql Ver 8.0.21-0ubuntu0.20.04.4 for Linux on x86_64 ((Ubuntu))
SQL modes:
WP-CLI root dir: phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir: phar://wp-cli.phar/vendor
WP_CLI phar path: /home/path/to/my/directory/
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 2.5.0-alpha-068c252

Problem 4C di Mesin Cuci Samsung

Kemarin, ketika saya mencuci, ada suara ‘notifikasi’ dari mesin cuci yang ada di rumah. Kebiasaan saya, ketika mencuci, begitu saya pencet tombol mulai — setelah pengaturan sesuai, tentu saja , saya langsung tinggal saja.

Setelah saya periksa, muncul di layar ada kode 4C. Sebelumnya, pernah juga mendapatkan kode error 5E. Ternyata kode 4C ini terkait dengan suplai air ke mesin cuci. Persis di sesi sebelumnya, tidak ada sama sekali. Solusinya? Tinggal pastikan saja ada air masuk.

Dalam kasus saya, masalah ini muncul karena tiba-tiba aliran air PDAM mati. Walaupun saya memang ada pakai pompa yang ambil dari tandon, tapi ini hanya ketika PDAM mati, dan saya menyadarinya. Atau, misal ketika debit air PDAM kecil sehingga aliran air tidak sampai ke lantai dua rumah.

Solusi Kode Masalah 5E Pada Mesin Cuci Samsung

Beberapa hari lalu, mesin cuci yang saya pakai di rumah mengalami masalah dengan menunjukkan code 5E (Atau SE?). Pencarian singkat mengenai kode permasalahan 5E ini mengarahkan bahwa masalah terkait dengan sistem pembuangan air. Jadi, mesin cuci tidak bisa menghabiskan/membuang seluruh air yang ada berdasarkan waktu yang telah diatur.

Kondisi ini terkait dengan kotornya pipa/selang pembuangan, dan juga ada kotoran dalam filter. Ini baru kali pertama saya alami setelah sekitar satu tahun sejak penggunaan.

Karena kondisi ini, jadi secara otomatis pintu mesin cuci juga terkunci — karena ada air di dalamnya.

Solusi Error Code 5E/SE

Solusinya cukup sederhana, yaitu dengan cara mengosongkan terlebih dahulu air yang ada dalam mesin cuci, dan membersihkan filter.

Atau bisa juga melihat berikut ini.

Selain kode masalah 5E, beberapa kemungkinan kode masalah dan solusinya adalah sebagai berikut:

  • DE (Door Error): Pintu belum tertutup atau belum rapat (Pastikan Pintu tertutup dengan rapat)
  • 4E (Water Supply Error): Pastikan air pada keran harus bertekanan (50-800Kpa) dan selalu terbuka.
  • 5E (Drain Error): Bersihkan saringan pembuangan, dan pastikan selangnya terpasang dengan benar, dan tidak ada yang menyubat saluran pembuangan.
  • UE (Unbalance Error): Mesin bekerja dengan tidak seimbang, kemungkinan mesin berdiri dengan tidak stabil, cucian mengumpal/kusut (stop dulu proses mencuci dan keluarkan pakaiannya lalu masukan kembali satu persatu).
  • SUD (Foaming Detected): Sabun terlalu banyak sehingga kelebihan busa sabun, biarkan mesin bekerja sendiri untuk mengurangi busanya dan akan berjalan normal kembali.
  • UC (Power Error): Tegangan di rumah anda sedang tidak stabil sehingga secara otomatis perangkat akan menunda proses pencucian untuk melindungi diri dari kerusakan dan akan kembali bekerja apabila tegangan listrik sudah kembali normal.
  • LE/LE1 (Water Leakage Error): Ini terjadi disebabkan karena busa terlalu banyak deterjen, penutup filter pada pompa pembuangan atau pengeringan terlepas, atau ada kebocoran air terjadi di selang pembuangan.
  • OE/OF (Overflow Error): Pasokan air bekerja terus – menerus karena pendeteksi level air tidak bekerja, bisa juga dikarenakan selang pembuangan terlipat sehingga air tidak keluar dengan lancar.
  • 4C Kode error disebakan suplai air tidak tersedia: Pastikan air keran terbuka, pastikan selang air tidak tersumbat, pastikan keran air tidak membeku, pastikan mesin cuci beroperasi dengan tekanan air yang cukup. Ketika mesin cuci menampilkan error 4C, mesin cuci melakukan pengurasan selama 3 menit. Selama waktu tersebut tombol Power tidak berfungsi.
  • 4C2: Pastikan selang pasokan air dingin tersambung dengan kuat ke keran air dingin. Jika terhubung ke keran air panas, cucian dapat berubah bentuk dengan beberapa siklus

Kode Error Pada AC Gree

Sewaktu melakukan pemasangan unit AC dari di rumah baru-baru ini, saya mendapatkan informasi dari pihak teknisi resmi Gree kalau misal ada masalah, nanti kode kesalahan/masalah ( code) akan muncul dalam indikator suhu yang menyala di AC.

Saya baru tahu soal ini. Jadi, kalau misalnya ada masalah, disarankan untuk nantinya menghubungi layanan pelanggan. Tentu saja, saya juga tidak ingin ada masalah dengan AC di rumah. Dan, jika terjadi masalah maka AC secara otomatis tidak dapat digunakan. Hal ini untuk mencegah terjadinya kemungkinan masalah lainnya.

Masalah UseeTV Telkom Kode 1305

Kemarin lusa (Jumat), ketika saya mencoba untuk membuka koneksi UseeTV sebagai salah satu fitur dalam paket IndiHome Triple Play, saya mendapatkan permasalahan. Jadi, permasalahan ini karena perangkat STB (Set Top Box) IPTV gagal mendapatkan alamat IP ( Protocol). Kode kesalahan ( code) adalah 1305.

Pesan yang ditunjukkan dalam layar menyarankan solusi untuk permasalahan ini yaitu:

  1. Memeriksa apakah jaringan internet berjalan dalam kondisi normal. Saya lakukan pengecekan, dan semua dalam keadaan normal. Koneksi internet dapat diakses tanpa masalah.
  2. Restart perangkat STB melalui remote control. Saya juga sudah lakukan. Ketika selesai restart, permasalahan yang muncul masih sama.
  3. Restart perangkat modem dan diamkan beberapa menit. Disarankan waktu jeda adalah sekitar tiga menit. Saya coba langkah ini. Tetap tidak berhasil.

Karena tidak berhasil juga, akhirnya saya hubungi layanan pelanggan melalui akun @TelkomCare di . Saya sampaikan informasi nomor pelanggan saya. Tak lama berselang saya mendapatkan informasi bahwa laporan telah diterima, dan saya diberi nomor pelacakan kasus.

Keesokan harinya (Sabtu), saya mendapatkan telpon dari . Saya dipandu untuk melakukan pengecekan. Ternyata masih tidak berhasil juga. Dari pihak Telkom menyampaikan bahwa nanti akan dibantu dengan mendatangkan teknisi lapangan ke rumah.

Jadi, mari kita tunggu. Semoga tidak perlu sampai menunggu lama hampir tiga minggu seperti kasus sebelumnya.

Perbaruan informasi

  • Sejak masalah ini, memang tidak ada penanganan langsung teknisi datang ke rumah. Saya hanya mendapatkan beberapa kali pesan singkat melalui yang menginformasikan bahwa layanan masih dalam perbaikan.
  • Beberapa hari setelahnya, saya bahkan hampir tidak menyalakan televisi, jadi tidak melakukan pengecekan juga.
  • Kemudian, saya coba kembali sekitar 7 hari setelahnya. Dan, layanan ini telah kembali normal.

nginx error: client intended to send too large body

After moving this to DigitalOcean‘s , I found a problem when uploading a from my blog posting interface. Looking up from the log, it says "client intended to send too large body: 1122400 bytes". I wanted to upload a file larger than 1 MB. I’m using for the web , and the solution is pretty simple.

Edit /etc/nginx/nginx.conf file, and add client_max_body_size 20M; between http { }. Save the config file and start the nginx. Problem solved. If you need higher value, just change the 20 MB to something higher.

Solution: WhatsApp crashes on iOS 8 Beta

WhatsApp Logo
Last week, I finally decided to my 5 to 8 Beta 4. When the iOS Beta 1 was available, I took the risk to have it installed. But, it was too disappointing for too many and errors. I’m excited about the upcoming iOS 8 features, and I want to try some of the features. There is a discussion thread at MacRumors Forum which lists the application compatibility on iOS 8. Anyway, I have lots of apps installed right now. If you’re not sure about having the iOS Beta, you can wait for the official .
I have some applications that are not running well, and one of them was WhatsApp. It keeps crashing. I can accept the fact that some other applications are broken or crashed. But, is an app that I use on daily basis. After searching for solutions, there are two popular ways to fix this issue:

I chose the second option, because it’s pretty straight forward. Big thanks to Ritvij Pathak’s The Tech Portal. So, what was the problem? Quoting from the site:

The main reason for the crashes is typographic ligature. For those of you who didn’t get what it is, don’t fret, we didn’t either. Turns out it has something to do with two letters being read as one syllable. Ex: letter combos like ff, fi, ffi, fii, will make WhatsApp crash.

What I found was that WhatsApp crashed when I typed some words or there are some words that are already in the . So, I followed the instructions and had everything solved. I want to reproduce the solution based on my experience.
I need to download two applications: iExplorer and Navicat for SQLite. Both are paid applications but the trial version are available. After I had it installed, these are steps I did. Anyway, WhatsApp setting should be turned off.
Open iExplorer — your iPhone should be connected, of course — and navigate to Apps > WhatsApp > Documents. Export the ChatStorage.sqlite file by right-clicking on the file and choose the export destination of your choice. You will need this file later. Having the backup for this file is advisable. So, after exporting this file, duplicating this file won’t hurt.
iex-1972401972491724
Open Navicat for SQLite and import the ChatStorage.sqlite from the previous step. Navigate to and add a new query. Paste the query below, and Run it.

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'ff', 'f f')
where ZWAMESSAGE.ZTEXT like '%ff%';
update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fi', 'f i')
where ZWAMESSAGE.ZTEXT like '%fi%';
update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fl', 'f l')
where ZWAMESSAGE.ZTEXT like '%fl%';
CREATE TRIGGER insert_Ff AFTER INSERT ON ZWAMESSAGE
BEGIN
  UPDATE ZWAMESSAGE
  SET ZTEXT = replace( ZTEXT, 'ff', 'f f')
  WHERE ZWAMESSAGE.ZTEXT like '%ff%';
END;
CREATE TRIGGER insert_Fi AFTER INSERT ON ZWAMESSAGE
BEGIN
  UPDATE ZWAMESSAGE
  SET ZTEXT = replace( ZTEXT, 'fi', 'f i')
  WHERE ZWAMESSAGE.ZTEXT like '%fi%';
END;
CREATE TRIGGER insert_Fl AFTER INSERT ON ZWAMESSAGE
BEGIN
  UPDATE ZWAMESSAGE
  SET ZTEXT = replace( ZTEXT, 'fl', 'f l')
  WHERE ZWAMESSAGE.ZTEXT like '%fl%';
END;

Your ChatStorage.sqlite has been updated. The next thing you need to do is bring the file back to the iPhone using iExplorer. Move it to the same place and if you’re asked to replace the file, just replace the file.
My previous errors with WhatsApp was fixed immediately. But, it seems that the errors still occur under different situation. The most common problem is that WhatsApp still keep crashing when I type some words in the window. For now, the temporary solution works, and let’s wait the official update from WhatsApp team. I’m sure they will fix it once iOS 8 is available.

Solved: Apple's App Store Purchase Using Visa

Last week, I got problem with my purchase at Apple’s App Store. I didn’t tried to purchased any paid apps after that. Today, I tried to purchase something on my . I was curious whether this problem had been sorted or not. And, it’s back to normal now. Fixed!

Apple's App Store: Your payment method was declined.

Few days ago, I heard that some friends complained about their ID. It had something to do with /billing info. I told them that I had my work without any issues. I also joined some discussion groups, and one of them were also discussing about this. Mine was working great. But, not until today, when I decided to purchase something from my .
I’m using .
My last transaction was made on my iPad on October 31, 2012. It went as I expected. So, it had been a week since my last purchase. I use the same billing details since I purchased my first app for my devices (, 4, and New iPad).
Payment Declined
After asking for confirmations from other friends, they’re all using Visa. I also searched for more details, the problem was solved after changing the to Master Card. I’m not lucky for this since I only have Visa right now. I am sure that I have no problem with my card. After my last purchase, I still make transaction using it.
There’s also a long discussion on this issue at Apple Support Communities, and it seems that Visa users only need to wait to get the problem sorted. Too bad.

Missing WordPress' Jetpack Statistics Data

I have been using Stats plugin for long time. And when Jetpack  was introduced, I had it installed right away. Everything works great. What I like about WordPress — from this plugin — is that it can give me some useful insight about my blog traffic. It’s not as detailed as Google Analytics, of course. But, it’s useful.
Yesterday, I made some modifications on the blog . I was not sure whether this problem has something to do with the issue or not. But, when I logged in to my WordPress and hit the Stats Page I found an . Something regarding the invalid token.
I disabled Jetpack plugin, and had it enabled again. I did it using the standard procedure: install, connect to WorPress.com , and configure.

All works. But, not the statistics. All statistics are gone.

I have some statistic profiles under a single WordPress.com account. I checked the other sites, and they’re all working. I’m still looking for a solution for this. I feel that all the statistics are stored at WordPress’ . I think I will try to contact them. For now, I think I will use Analytics data and server log.

Dear Flickr, I just want to buy a Flickr gift

But, it seems that something is broken.
Today, a friend contacted me to help him getting a Flickr Pro by activating a Flickr gift. This is not the first time for me purchasing gifts. Everything worked. Just worked. But, not today.

So, I wanted to buy my 11th Flickr gift — yes, 11th!. I went into what Flickr called “Place your order” page. I hit that blue “OK, I’M READY TO PAY” button. After that I was redirected to another login form for another authentication process. Sure, part of the checking processes, right? I gave my and nothing happened. Okey, may be it’s my web — even I was sure that nothing was wrong with my browser. The other browsers gave me the same results. It didn’t work. Okey, I waited.
Then, I tried again. But, I got a another respond. It was a message like this:

Sorry, Unable to process request at this time — 999.
Unfortunately we are unable to process your request at this time. This error is usually temporary. Please try again later.
If you continue to experience this error, it may be caused by one of the following:

  • You may want to scan your system for spyware and viruses, as they may interfere with your ability to connect to . For detailed information on spyware and virus protection, please visit the Yahoo! Security Center.
  • This problem may be due to unusual network activity coming from your Provider. We recommend that you report this problem to them.

While this error is usually temporary, if it continues and the above solutions don’t resolve your problem, please let us know.

Okey. I’ll wait. Yes, it’s weekend, and it was midnight. Dear Yahoo! — or Flickr — could you please fix that? My friend just want to have his Flickr upgraded. Thank you.
[Added later]: This issue had been solved. It seemed that there was something wrong with the gateway issue. My friend bought a Flickr Pro gift for himself. :)

Let's bring this blog back!

This blog goes nowhere. It’ still here, still up and running, but I realized that there is no single post in the last… (almost) two months. Not to make any excuses, but I think I was busy. I’m still updating my other blog, though.
Few days ago, when I was working on some -powered blogs, I found that there are some changes. I upgraded some blogs — including some installed , and I also found problems. But, the problems had been solved anyway. I logged in to my , and run some processes. One of the problems I found was a WordPress plugin called “Jetpack”. Anyway, if you haven’t heard about Jetpack, here is a little bit detail:

Jetpack is a plugin that connects to WordPress.com and enables awesome , powered by our infrastructure.

There are already some features included, but I think I only use of: WordPress.com Stats. Previously, I have WordPress.com Stats plugin installed, after having my blog upgraded to Version 3.1, the statistic plugin stopped working and left this message: “Your WordPress.com is not authorized to view the stats of this blog”. After searching some answers, most of the solutions mentioned about having Jetpack replaced WordPress.com Stats.
But, when I tried to activate Jetpack — by authenticating to  WordPress.com account — it didn’t run smoothly. I got this :

Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just lucky: xml_rpc-32601Try connecting again.

I tried again and again. I searched for a solution and the problem was because I have a plugin installed. By the way, I use W3 Total Cache. So, I disabled the cache settings, sent an authentication request, and voila! Problem solved. If you find problem just like what I had, now you know the solution.
I also made some modification here. I removed some features I considered as “not-too-important”. More importantly, it’s a matter of having some articles posted here. Shoot!

Gravity Photo Upload Error: XL Problem?

I have been using for more than a year and so far, I find that this is the best client for Symbian. I have it installed on my Nokia 5800 XpressMusic and N8. Using Gravity, it’s easy to share directly to some photo providers like , yfrog, img.ly, or even . Sound good? Yes.
But, it’s only when your internet provider works without any issues. Until today, I only use two mobile internet : and . Using Telkomsel, I almost found no problems. Everything is working. Well, not 100% great, but it’s still acceptable. Right now, I use XL internet service. I just want to try its service. Both offer the similar price for its data plan. XL has more offers when purchasing the mobile internet package.

The problem is — again, this is related to Gravity application — everytime I upload a photo, I always got Error: HTTP 401. Telkomsel didn’t give this kind of error. So, is it an issue from XL’s side? Maybe.
Wikipedia says:

401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided.The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.

Not good.
When I tweeted this problem, my friend Andrayogi also shared a same experience. So far, I’m happy with the internet performance by XL. Yes, I have been using XL service for almost 10 years. And this is the first time I use its ‘unlimited’ data plan. If this problem remains unsolved, I think I will be switching back to Telkomsel.

WordPress 3.0 Error: Briefly unavailable for scheduled maintenance

I have upgraded this blog to WordPress 3.0 not long after it was available for . Everything went without any major issues. I only use it without special hacks. One thing that makes this version a little bit different is that will bring your offline if there is/are something not working. For example, when you’re upgrading your . WordPress will temporarily bring your site under maintenance mode.
If all process were completed, you should be happy. Otherwise, you will need to do some extra works. WordPress will display this kind of message: “Briefly unavailable for scheduled maintenance.” You will be locked out from your admin area. Your will be inaccessible. Solution? Easy. You need to go to login to your webhosting , and remove .maintenance . You can find it in your blog folder — the same location with your wp-config.php.