Messages

1

BEAM IR/RF Wifi transceiver / Re: LinknLink App causes Beams to crash

« on: March 30, 2024, 10:48:56 AM »

Hi PegLeg,
do you have the IR events active on both beams?
Or does this also happen when the eRemote Blaster is not connected?
I can't imagine how the app could trigger this as it uses Bluetooth to find the eRemote Blaster.


LG,
Kalle

2

VoxCommando Basics and Core Features / Re: Group.Enable and Group.Disable

« on: March 02, 2023, 02:13:17 AM »

Hi bobsbrewewery,
can you specify more what exactly is not working?


I have tried the Groupe.Enable / Disable command, and it works fine.

3

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 22, 2022, 04:37:52 AM »

Glad to hear you solved the problem.
I wish you a Merry Christmas and a Happy New Year. 

Kalle

4

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 16, 2022, 02:50:16 PM »

Thanks for all the info.


If the second code was work for you, it is easy to shorten all you codes without an math or regec or what ever.
The only thing you have to do - take a look where is the large number is and cut it out to the last number before the next similar large number starts (include thecomma at the end).


example:


123,41,121,41,120,122,41,41,120,122,41,41,120,122,41,121,41,41,121,42,120,42,120,43,119,43,120,123,40,42,120,43,120,42,1201,57,106,53,110,128,36,125,38,124,39,123,40,122,41,41,121,42,120,43,119,123,40,42,120,122,41,42,120,122,41,121,42,41,121,42,120,42,120,42,120,43,119,123,40,42,120,42,120,42,1201,56,107,53,110,128,36,125,38,124,39,123,40,122,41,41,121,42,120,42,120,122,41,42,120,122,41,41,120,122,41,121,42,41,121,41,121,42,120,42,120,42,120,122,41,42,120,42,121,42,1201,56,107,52,111,128,36,125,38,124,39,122,40,122,41,41,121,42,120,42,120,122,41,41,120,122,41,41,121,122,41,121,42,40,121,41,121,42,120,42,120,42,120,122,41,41,120,42,121,42,1201,56,107,52,111,128,36,125,38,124,39,123,40,122,41,41,121,42,120,42,120,122,41,42,120,122,41,41,121,121,41,121,42,41,121,41,121,42,120,42,120,42,120,122,41,41,121,42,120,42,1201,56,107,52,111,128,36,125,38,124,39,122,40,122,41,41,121,42,120,42,120,122,41,41,121,122,41,41,121,121,41,121,42,40,121,41,121,42,121,42,120,42,120,122,41,41,121,42,121,42,1201,56,107,52,111,128,36,125,38,124,39,123,40,122,41,41,


This is your posted raw code and you can see the correct sequence ist starting at green and repeatedly continuous - the red marked is the code is not needed.


Kalle

5

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 15, 2022, 02:22:41 AM »

Now that makes me curious - I have a lot of 433MHz remotes and none of them produce such a start frequency. What I mean, your RF code starts with a relatively small sequence of numbers (initial code: 102,134,32,128,36,124,40,122,41, ...), which I have never seen before, no matter from which RF remote control - the initial code always starts with a large number.


I am in the lucky position to test your working code with two BEAM's and the BEAM Plugin (one BEAM transmits, one receives) and have the following result which you could try out.

/sendRFraw?code=1019,69,105,54B129,36DEDEDEE120EFEFDEEFDEEDDEDEEDEFEFCFEFDEEF45BDEDEDEDEFEB248,24DFCEDFEEDFEFEFEFEFEFEFEFEFEFEFEEFEFEFEFE

This is a part of your original code, which i have shortened:
/sendRFraw?code=1201,55,108,52,111,128,36,125,38,124,39,123,40,122,41,41,122,41,121,42,120,122,41,41,121,121,42,41,121,122,42,121,43,40,122,41,121,41,121,42,120,42,120,122,41,41,121,42,120,42,


In the Beam plugin there is the possibility to adjust the noise - try higher values, this will filter the sequences a bit or lower values to see more sequences but a lot of trash.
What surprises me is that you don't get anything in the BEAM plugin under "Compressed Code" when you try to learn the remote control with the BEAM.


Kalle

6

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 10, 2022, 02:53:38 AM »

Hi PegLeg,
nice to hear that your problem is solved.
You can also send the compressed code instead of the raw code which is displayed in the BEAM plugin.

example code: /sendRFraw?code=1130,39,104ABABABABABABABABABABBAABABABABABABABBAABBAABABA


or an other option is to use the BEAM WebUI for learning a code (if it possible) and maybe you have a code that looks like: /sendRF?code=4116&bits=24&n=1

7

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 02, 2022, 05:22:29 AM »

Try first a new chip, if this doesn't help, let me know and I can assemble you a complete new PCB Board with all components.

Best wishes,
Kalle

8

BEAM IR/RF Wifi transceiver / Re: BEAM documentation / news

« on: December 01, 2022, 04:39:53 PM »

Hi PegLeg,
the phantom code looks really bad - did you checked the BEAM plug-in RF settings if there is something wrong with the parameter?
If the Chip is damaged, the first one of your Amazon link is the best choice.


One other thing - are you sure you have only insert the 433MHz RF receiver in your BEAM? You can use only one receiver in the BEAM for learning RF codes (433MHz or 315MHz). So if you have both receiver installed, remove the 315MHz Chip first before start learning a code.


Kalle

9

General Discussion / Re: Still VOXing after all this time!

« on: September 09, 2022, 06:39:02 AM »

Hi guys,


I'm also still using VoxCommando.

It's a permanent fixture in my smarthome. I rarely use the voice input, but it is unbeatable for saving or forwarding status data and I can't imagine my home without it.
I have a mix of Z-wave / Zigbee / RF433 and infrared - VoxCommando is the only program that brings these devices together.


Kalle

10

VoxCommando Basics and Core Features / Re: Echo Dot Integration 2018

« on: August 25, 2022, 01:32:33 AM »

I have tested the aws code from James and also with this I get on the echo only an "OK" as confirmation, see attached image.
Maybe the problem is with the webserver or the settings.


The command is executed correctly, so it's not really a problem, it was always just nice to hear what "Alexa" had understood.
The voice output via VoxCommando works perfectly - who knows what was changed by Amazon in the past, considering how long the skill has existed.


Whether "Alexa" meanwhile releases the device variable, I can not tell you unfortunately.


Kalle

11

VoxCommando Basics and Core Features / Re: Echo Dot Integration 2018

« on: August 23, 2022, 03:37:49 AM »

Hi PegLeg,
do you get a confirmation via Alexa or does Alexa repeat the command?
At the moment I only get "OK" as confirmation and I am sure that she repeated the command before.
Do you know where I can set this in the code?


Kalle

12

VoxCommando Basics and Core Features / Re: Echo Dot Integration 2018

« on: August 19, 2022, 04:36:04 AM »

Now at least it works again.
The problem was my DDNS account, which had not updated the IP address.

@PegLeg: Like you, I changed the invocation name, but I never say the second word, otherwise Alexa always replies with "a problem with your skill.... blah, blah, blah".
It was pure coincidence that I noticed this, because I had not yet become accustomed to the second word.
In other words: If your first phrase is currently "Iron" and "Man" is your second phrase - try "Alexa, tell Iron lights please" - if it works, you can set your invocation name to Jarvis Jarvis or ironman ironman, so that the invocation name rule is met, but always speak only the first phrase to Alexa.


I know it sounds strange, but it worked for me and maybe for you too.


Kalle

13

VoxCommando Basics and Core Features / Re: Echo Dot Integration 2018

« on: August 18, 2022, 03:10:30 AM »

Yes, long time ago - maybe if James will find some time he can take a look on it.


stay tuned,


Kalle

14

VoxCommando Basics and Core Features / Re: Echo Dot Integration 2018

« on: August 18, 2022, 02:16:23 AM »

Hi PegLeg,


I noticed the same issue and have no idea how to solve it.


Kalle

15

Поддержка русского языка / Re: TTS Phrase Completion Event

« on: December 20, 2021, 03:22:45 AM »

You can try James suggestion with my command above by renaming the command so that it starts with ++