search

jgyates / genmon

Generac (and other models) Generator Monitoring using a Raspberry Pi and WiFi
GNU General Public License v2.0
380 stars 78 forks source link

Genalexa question #303

Closed RoyRomeo closed 4 years ago

RoyRomeo commented 5 years ago

Use the template below if you have an issue or want to report a bug. If you have a question or a feature request you can ignore the questions below.

NOTE: If you are having issues with your serial connection, please read this page before posting:

https://github.com/jgyates/genmon/wiki/3.6---Serial-Troubleshooting

If you are having other issues, please see the following page:

https://github.com/jgyates/genmon/wiki/3.5---General-Troubleshooting

If you need to send you logs and registers to the developer, if you email is setup and working properly you can click send your logs on the About page in the web interface.

Expected Behavior

Ability to connect to Alexa

Actual Behavior

Amazon Alexa voice command add-on enabled, UPnP on router enabled, Alexa cannot discover generator.

Steps to Reproduce (including precondition)

{Please write here}

Screenshot or Pictures relating to the problem (if possible)

{Please write here}

Your Environment

jgyates commented 5 years ago

@RoyRomeo

One thing that you can do to help determine the source of the problem is to edit the file /etc/genmon/genalexa.conf and enable additional debug info to be collected.

 sudo nano /etc/genmon/genalexa.conf

Then add the line:

debug = True

Save the file by typing Ctrl+X, then type the letter y for yes, then enter.

Then restart genmon

cd /home/pi/genmon
./startgenmon.sh restart

Let genmon run and try to discover the generator. Then submit your logs on the about page.

@buschauer will be helping me debug this as he coded the genalexa app.

MichaelB2018 commented 5 years ago

Also, did you try discovery twice. I did see it before that the first time it timed out too quickly after 20 secs. So try a second time and enable debug so we see what's going on.

jgyates commented 5 years ago

@RoyRomeo

I checked in an update to genalexa.py (i did not update the version number) that adds some additional debug output. Can you give it another shot and send the log again?

Also, what version Echo do you have?

To clarify, when you discover devices, do you get any response at all?

RoyRomeo commented 5 years ago

Okay, logs sent.I believe I have the 1st generation Echo.I get "No new devices found" when I run discover devices.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Mon, Jul 29, 2019 8:55 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

@RoyRomeoI checked in an update to genalexa.py (i did not update the version number) that adds some additional debug output. Can you give it another shot and send the log again?Also, what version Echo do you have?To clarify, when you discover devices, do you get any response at all?— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

@RoyRomeo

I checked in one more update with some more debug info. Repeat the same process except do the discovery twice.

RoyRomeo commented 5 years ago

Repeated the process and did the discovery several times, no success.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Tue, Jul 30, 2019 6:40 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

@RoyRomeoI checked in one more update with some more debug info. Repeat the same process except do the discovery twice.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

Can you send the logs? The update contained additional debug info.

RoyRomeo commented 5 years ago

Just did.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Tue, Jul 30, 2019 7:48 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

Can you send the logs? The update contained additional debug info.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

I got your logs. Did you update to the latest version of genalexa.py? I do not see the additional debug info in the log file.

RoyRomeo commented 5 years ago

Where do I find the latest version of genalexa.py?

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Tue, Jul 30, 2019 7:53 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

I got your logs. Did you update to the latest version of genalexa.py? I do not see the additional debug info in the log file.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

Just go to the About page and click "Update to the latest". It will download the latest and restart the software.

jgyates commented 5 years ago

Also, I did not update the version info since this update only provides more debug info so it will tell you you are running the latest but update anyway.

RoyRomeo commented 5 years ago

Updated and resent logs.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Tue, Jul 30, 2019 8:01 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

Also, I did not update the version info since this update only provides more debug info so it will tell you you are running the latest but update anyway.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

RoyRomeo commented 5 years ago

Did the update.  Not sure if I submitted the logs last night, so I submitted again.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Tue, Jul 30, 2019 8:01 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

Also, I did not update the version info since this update only provides more debug info so it will tell you you are running the latest but update anyway.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

Got them. thanks! I will let you know what we find.

jgyates commented 5 years ago

@RoyRomeo

Michael suggested trying this:

With a valid Alexa speaker in the house, use http://alexa.amazon.com. Select "Smart Home". Select "Devices". Scroll all the way down. Note down the number of devices ("Showing XX). Then select "Discover". I sometime have to do this twice myself. Not quite sure why. For debugging purposes try this 3 or 4 times, unless he sees the number of devices increasing. IF it increases (which it does for me), the new one will be listed at the top. Then send the log again.

RoyRomeo commented 5 years ago

Followed these steps, 1 device listed.  Selected "Discover" at least 6 times, but no new devices discovered.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Sun, Aug 4, 2019 3:23 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

@RoyRomeoMichael suggested trying this:With a valid Alexa speaker in the house, use http://alexa.amazon.com. Select "Smart Home". Select "Devices". Scroll all the way down. Note down the number of devices ("Showing XX). Then select "Discover". I sometime have to do this twice myself. Not quite sure why. For debugging purposes try this 3 or 4 times, unless he sees the number of devices increasing. IF it increases (which it does for me), the new one will be listed at the top. Then send the log again.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

MichaelB2018 commented 5 years ago

can you submit the logs again. Thanks.

RoyRomeo commented 5 years ago

Okay, just submitted them.

-----Original Message----- From: MichaelB2018 notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Sun, Aug 4, 2019 7:54 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

can you submit the logs again. Thanks.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jgyates commented 5 years ago

@RoyRomeo, below are some instructions from Michael for running a test using the library that genalexa is based on. This should tell is if the problem lies in the library or this projects implementation:

The log file is not providing any useful info. Not sure you has anything special in his network, maybe a internal firewall or similar? But let's take a step back and try the original FauxMo Library. 

Launch Pi ssh session with putty or locally through VNC and type following two commands Pi command prompt to update it. "sudo apt-get update" and "sudo apt-get upgrade" (This will take a while)

Download this github project as zip file with following command "wget 
 https://github.com/nassiramalik/IOT-Pi3-Alexa-Automation/archive/master.zip"

Unzip downloaded zip file with "unzip master.zip" command and type "cd IOT-Pi3-Alexa-Automation-master" command after unzip completes

Enter "sudo python3 RPi_name_port_gpio.py" command to run Pi IOT program

Give voice command to Alex to discover devices "Alexa discover devices" it will search your network and discover your Raspberry Pi 3 as an IOT device.

And let's see if this discovers any devices. There is also a nice Video to show Fauxmo in action

https://www.youtube.com/watch?v=uS5dTx8vjq4

and documentation is here

https://github.com/nassir-malik/IOT-Pi3-Alexa-Automation

RoyRomeo commented 5 years ago

Hi, Followed this process.  After the upgrade, there was a "node-red" error message stating that not all files were upgraded, some were left unchanged.  After running the last command, "sudo python3 RPi_name_port_gpio.py", there was an error that RPi module does not exist.  Anyway, tried "Alexa discover devices", no new devices found.

-----Original Message----- From: jgyates notifications@github.com To: jgyates/genmon genmon@noreply.github.com Cc: RoyRomeo Joe.Pryor@Verizon.net; Mention mention@noreply.github.com Sent: Wed, Aug 7, 2019 4:36 pm Subject: Re: [jgyates/genmon] Genalexa question (#303)

@RoyRomeo, below are some instructions from Michael for running a test using the library that genalexa is based on. This should tell is if the problem lies in the library or this projects implementation:The log file is not providing any useful info. Not sure you has anything special in his network, maybe a internal firewall or similar? But let's take a step back and try the original FauxMo Library.Launch Pi ssh session with putty or locally through VNC and type following two commands Pi command prompt to update it. "sudo apt-get update" and "sudo apt-get upgrade" (This will take a while)

Download this github project as zip file with following command "wget https://github.com/nassiramalik/IOT-Pi3-Alexa-Automation/archive/master.zip"

Unzip downloaded zip file with "unzip master.zip" command and type "cd IOT-Pi3-Alexa-Automation-master" command after unzip completes

Enter "sudo python3 RPi_name_port_gpio.py" command to run Pi IOT program

Give voice command to Alex to discover devices "Alexa discover devices" it will search your network and discover your Raspberry Pi 3 as an IOT device. And let's see if this discovers any devices. There is also a nice Video to show Fauxmo in actionhttps://www.youtube.com/watch?v=uS5dTx8vjq4and documentation is herehttps://github.com/nassir-malik/IOT-Pi3-Alexa-Automation— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

liltux commented 5 years ago

@RoyRomeo , you have one of my pre-built devices, correct? If so, I am using node-red on the devices for wifi configuration. If you are not using a pre-built device, if you are using the version of raspbian that installs "Everything", I believe node-red is installed. During and apt-get update and apt-get upgrade, any additions to the main work flow to your node-red install will not be updated. Does not mean there is a problem, just if you wish the extra node-red modules to be updated you will have to perform manually through npm or node-red scripts.

jgyates commented 5 years ago

Just curious if anyone else has tried genalexa besides @RoyRomeo or @MichaelB2018? It looks like there may be some limitations with the FauxMo code that was used to built this. I don't have an Amazon dot so I am unable to test this.

RoyRomeo commented 4 years ago

Just got two new Amazon EchoShow 5 units and installed them. Went through the discovery process and they found my generator right away. I can now "turn on" and "turn off" the generator via Alexa. I guess my older Amazon Echo does not have the technology that is needed to discover the generator.

jgyates commented 4 years ago

That is a good data point. I will update the document to note this. Thanks for the follow up.

rwskinner commented 2 years ago

I have 2 Show 5's and several Echo Dots, and none of them will discover the generator using GenAlexa. I also turned on debug and submitted the logs but they keep failing to send.

The genalexa.log just shows the same thing over and over no matter how many times I try to discover.

2022-07-05 08:49:23,133 : Responding to search for generator 2022-07-05 08:49:23,134 : HTTP/1.1 200 OK CACHE-CONTROL: max-age=86400 DATE: Tue, 05 Jul 2022 13:49:23 GMT EXT: LOCATION: http://XXX.XXX.XXX.XXX:52004/setup.xml #XX blanked out for privacy OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 01-NLS: 73e844fd-1c59-442c-bdd4-90a98150c32b SERVER: Unspecified, UPnP/1.0, Unspecified ST: urn:Belkin:device: USN: uuid:Socket-1_0-3c767656e65726::urn:Belkin:device: X-User-Agent: redsonic

jgyates commented 2 years ago

Hi @rwskinner,

Two notes on genalexa: 

 1) The only real thing that this allows you to do is to test your generator by turning it on and off. It does not adjust the transfer switch to allow you to power your house form the generator.
2) I can offer only limited support for this add on as it was not written by me (submitted by one of the users of this project) and I do not have any Alexa devices to test with.

If you are still interested keep reading.

Your outbound email must be setup and working in order to submit your logs via the about page. Alternatively you can submit your logs manually with these two commands (change the ip addresses as needed):

 http://192.168.1.10:8000/cmd/get_logs

This will download a compressed archive of all of your logs. You can attached this file to this thread in the github web interface (not as an email attachment)

and this command:

  http://192.168.1.10:8000/cmd/support_data_json

The copy and paste the output to this thread.

rwskinner commented 2 years ago

You're correct, GenAlexa really provides no value to me. I was only reporting that I also saw the same issues the previous poster did.

As far as email, Genmon is emailing me all the updates just fine, and two days ago, I was able to ship logs just fine and perform a back up. Then I was notified of an upgrade and I did so. Then today, the logs sent to your email fail. I did forward the failed email response directly to you via the generatormonitor.software@gmail.com email address.

Thanks for exposing the manual process of shipping the logs.

aaciii commented 2 months ago

I have a Gen 3 Amazon Echo Dot, and I cannot get the generator to be discovered either.