[RPi] Argon ONE Control Add-on (Support Thread)

The hopefully fixed version 0.0.8 is available. Please report if it's working now without fan fluctuation with the Argon One V3 case.

Can someone with a Argon One V3 case check if a "Double Tap" at the power button triggers Reboot like with Argon One V2 case?
If not, I need some information if it works after changing these lines in /flash/config.txt from:

dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
enable_uart=1

to

dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
dtparam=uart0=on

Followed by a reboot.

Fan pulses seem to have stopped with 0.0.8, but i don't think the double press works. Will try the alternative settings in the config file shortly.

I've installed version 0.0.10, and it looks to be performing as expected.

My remote is no longer working. Am using a SofaBaton, with the onboard IR receiver and a mecool_kii_pro keymap.

Edit: ignore that all sorted. Has anyone else found the range on the v3 IR receiver to be crap? I'm barely getting 6ft. Using a FLIRC as a temporary solution but would rather use the builtin receiver.

Can the addon be configured so it doesn't override /storage/.config/rc_maps.cfg on boot? I've changed it to support the remote I'm using but after a reboot its back to the argon40 remote.

Quote

Can the addon be configured so it doesn't override /storage/.config/rc_maps.cfg on boot? I've changed it to support the remote I'm using but after a reboot its back to the argon40 remote.

Before I look deeper into the code, does this "touch /storage/.config/argon40_rc.lock" don't work for you?

Regarding the range. I have seen your post in Argon40 forum. I can only report from a buddy of me, who is owner of a Argon One V1 and has added the IR Receiver manually. He reported a bad response to the IR signal until he has made a slot/hole in the transluent red plastic cover. Before made such irreversible changes you should check without the bottom assembled.

Edit:
In a short test with my universal remote control, I got a distance of about 4m/13 feet when I pointed the remote control frontal to the argon case. The further you go away, it seems more important to keep the remote control at the same heights as the case/IR sensor.

I have 8 devices running LE12 (and a few on CE21).

Quote from HarryH

Before I look deeper into the code, does this "touch /storage/.config/argon40_rc.lock" don't work for you?

Regarding the range. I have seen your post in Argon40 forum. I can only report from a buddy of me, who is owner of a Argon One V1 and has added the IR Receiver manually. He reported a bad response to the IR signal until he has made a slot/hole in the transluent red plastic cover. Before made such irreversible changes you should check without the bottom assembled.

Edit:
In a short test with my universal remote control, I got a distance of about 4m/13 feet when I pointed the remote control frontal to the argon case. The further you go away, it seems more important to keep the remote control at the same heights as the case/IR sensor.

Thanks "touch /storage/.config/argon40_rc.lock" sorted it.

Found my range issues are likely being caused by the remote rather than the sensor. Range on my SofaBaton U1 is terrible compared to my Flirc Skip 1s. Unfortunately, the range of devices supported by the Skip 1s is a big lack luster.

Quote from PANiCnz

Unfortunately, the range of devices supported by the Skip 1s is a big lack luster.

You know it's a programmable universal remote, right?

Hello HarryH ,

i installed your plugin but it killed my MCE-USB Remote. It worked again after i restored my backup. Is there a way to use your plugin but keep my MCE USB Receiver/Remote working?

Hi ApexDE ,

like mentioned at multiple places like the change message for 0.0.10 and "Breaking change" in the middle of the post #25 .
You can prevent the Addon from overwriting your remote control settings, if you drop a empty file with the name "argon40_rc.lock" in the ".config" folder.

touch /storage/.config/argon40_rc.lock

Oh gosh, haven't seen this. Sorry and thanks

i got the Argon Fan working again using your plugin, well done!

Why isn't the plugin in the LibreElec repository?

Quote from ApexDE

Why isn't the plugin in the LibreElec repository?

I doesn't have a automatic build process ready and I honestly currently don't know what's all required to make it part of a LE repo.
May be I must extent my test scenarios first, to prevent that I publish a buggy version.

For example, this week I stumbled over the regression, that in version 0.0.13 I introduced throwing of a exception with setting "Fan always on" is enabled. If this setting is set to enabled, the fan isn't running. I thought I have tested, but it seems I didn't.
Version 0.0.12a shouldn't affected by this. And as temporary workaround with version 0.0.13, you can lower the threshold to get the fan running all the time.

Such things shouldn't happend with a Addon in a official repo...

Yes, that was my first test: Fan always on. And it didn't work so i thought the addon in general doesn't work.

Can you built in a switch for the Argon remote and the others so it doesn't break the other remotes when installing the addon without the lock file? I believe one should actively choose to use the Argon remote instead of the formerly used one. You could backupcopy the previously used remote config files also?

Quote from ApexDE

Yes, that was my first test: Fan always on. And it didn't work so i thought the addon in general doesn't work.

I wished, that such issues are reported here, and not silently switched back to an old version. Like the issue above, sometimes I detect that randomly only. And so long I believing all things are fine.

Quote

Can you built in a switch for the Argon remote and the others so it doesn't break the other remotes when installing the plugin without the lock file? I believe one should actively choose to use the Argon remote instead of the formerly used one. You could backupcopy the previously used remote files also?

It's not so easy like it sounds. In my opinion the best way would be, if a dialog were opened during the installation process if a existing configuration has been detected. But it seems that it's currently not supported by KODI for Addons, or I doesn't know the way for.

Because I wanted to force the migration to the modern way with ir-keytables, it was needed to delete the old lircd.conf, which was provided by the version < 0.0.10. Default this file doesn't exist in LE.
I don't have a statistic, which way (lircd vs. keymaps) the most users using with their own remote control configuration, and therefore I'm been unsure which files I should check to make this process bullet proof.

As a simple solution I thought about in the past, to add a switch to create/delete the lock file from menu. But this will not prevent, that your configuration will be overwritten during the first installation of the Addon. To prevent this, I must set the remote control file copy process default to off. It needs a restart of KODI to reload the remote config, as far as I know. But there are also users with the origin Argon IR remote, they need the configuration file from the Addon and may expect that the remote work out of the box, after the Addon is installed successful.

That's the conflict I'm in.

you could build in a switch where you can choose to use the argon receiver or "other ones" ? When switched to argon the previous configs are backuped and when turning off the previous backuped ones are copied back?

The Addon can't backup files, which are not exists during installation or after the settings menu was closed with OK.
Please be aware: The known switch object in the Addon settings menu isn't able to trigger directly an action! This could be create a gap in your idea and needs additional handling. For example if someone will change/add his own files, after the plugin was installed and is already running. Such edge cases must be taken into account.

I would prefer the way, to add the Argon IR remote to the existing list for coexistence, if that possible. But this depends on how the custom remotes were added.

Like I wrote before, the Addon (depending on the version) currently add only files to the ".config" directory like rc_maps.cfg and lircd.conf. This are 2 different ways to add a custom remote, but the resulting behavior is different.

Please can you provide more details, which file(s) you have restored, to make your remote control working again?

i did a full restore via the LibreElec Config Tool (Kodi Menu)

Okay, this looks like a little bit different constellation. If i'm right, then the remote you using relies on the default remote profiles. Or do you have added an "rc_map.cfg" or "lircd.conf" file manually in the past to get it work?
You can check if one of these files exists in the "/storage/.config" folder.

Hint: Instead of a restore the complete configuration, in your case it would be enough to delete the rc_maps.cfg in /storage/.config. Just for completeness also delete the remaining "/storage/.config/rc_keymaps/argon40.toml".

In this case, I already had on my to-do list to find a working merge solution.

Downloaded from github right now , but latest libreelec version gives installing error.

tried version 0.0.0.13 that installed without problems. so i guess ther's someting wrong.

btw in github the option issues is disabled ,no way to open a report.

thanks for all you are doing to keep alive this progect !