search

StyraHem / ShellyForHASS

Shelly smart home platform for Home Assistant
MIT License
619 stars 112 forks source link

No errors in log, but not working for me #52

Closed woody4165 closed 4 years ago

woody4165 commented 5 years ago

Hi

I've installed via HACS and I'm on version 0.0.15 My config is

shelly:
  discovery: true
  version: true
  show_id_in_name: true
  additional_information: true
  power_decimals: 2
  sensors: 
    - power
    - rssi
    - uptime
    - over_power
    - device_temp
    - over_temp
    - cloud
    - mqtt
    - battery

I don’t see them in MQTT integrations and I don't see any of the sensors requested (rssi, mqtt, cloud and so on). I’ve also tried to use the - all option instead of defining one by one.

I’ve also defined in the log

logger:
  default: error
  logs:
    custom_components.shelly: debug

but I don’t see any error.

In the log I see

2019-08-20 11:57:35 INFO (SyncWorker_5) [custom_components.shelly] Starting shelly, 0.0.15 2019-08-20 11:57:35 INFO (SyncWorker_5) [custom_components.shelly] pyShelly, 0.0.31

What can I check?

Thanks

woody4165 commented 5 years ago

I don't think so since the test.py script to check COAP message does not work on Hassio machine as well on a standard Linux machine. At least for me.

hakana commented 5 years ago

It working on for most people. But some having this problem. Im not a Linux /network expert. I think the problem is in the router and maybe not support IGMPv2 or simular.

woody4165 commented 5 years ago

Hi @hakana Today I will try to connect an Rpi3 with Hassio and a Shelly to a Mikrotik router, wired the first and wireless the second. And I will let you know if there is any news...

hakana commented 5 years ago

Great, look forward to get your result.

woody4165 commented 5 years ago

Just tried with a Mikrotik Access Point, HAP Lite, and magically it works. So, as you said, the problem is from my main router side (Fritz 7590) that does not manage properly the IGMP. I have tried with a fresh&clean Hassio install on an RPi3, but probably will work also on my virtualized environment. Now the question is if I want to put the Mikrotik as main or slave router and connect to it the Hassio server and all the Shellies, which implies, most probably, to have two subnets, one from the main modem/router and one from the Mikrotik. The Wifi signal of this Mikrotik device is very poor compared to the Fritz and to the Chinese AP that I already have. So I have to understand the best way to do it.

In any case, I have to thank @hakana for the time spent trying to help me and other people that have also different router than my Fritz and does not support correctly IGMP/COAP communication! I hope I can use someday this Custom Component that is very well done.

Thanks again!

Boogs77 commented 5 years ago

Good news to know, but... My system was working very well, but suddenly all shelly stop to be recognized.

Nothing was changed. My router, switched and ap remain the same.

errecla commented 5 years ago

bad news from me: I install last version of hassio (not home hassistant) and I see only sensor.shelly version. I dont' see shelly components.

woody4165 commented 5 years ago

Hi @hakana I would like to try one more thing. Since I'm pretty sure that this was working some time ago (I still have the sensor shsw defined in HA), I would like to try some old versions, older than the one I can see in HACS.

Is it possible?

Thanks

brama1966 commented 5 years ago

What ever versions are on github you can install. You don't need HACS to do it. HACS just makes it easier to install and keep update

Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: woody4165 notifications@github.com Date: 1/9/19 7:22 pm (GMT+10:00) To: StyraHem/ShellyForHASS ShellyForHASS@noreply.github.com Cc: George Georgas george@cnscomputers.com.au, Comment comment@noreply.github.com Subject: Re: [StyraHem/ShellyForHASS] No errors in log, but not working for me (#52)

Hi @hakanahttps://github.com/hakana I would like to try one more thing. Since I'm pretty sure that this was working some time ago (I still have the sensor shsw defined in HA), I would like to try some old versions, older than the one I can see in HACS.

Is it possible?

Thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/StyraHem/ShellyForHASS/issues/52?email_source=notifications&email_token=AMNWOQNNMHNL63LLJITI27DQHOCWRA5CNFSM4INTZDLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5T6HMQ#issuecomment-526902194, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMNWOQLEFHL4DICBZOHXCLTQHOCWRANCNFSM4INTZDLA.

hakana commented 5 years ago

Yes all code is in GitHub, there is only releases created for the last releases but you can find the code there.

woody4165 commented 5 years ago

I've installed 0.0.8 and now I remember why I have uninstalled first time. Now I can see all the sensors, but they turn from unknown to unavailable to the real state.

Probably the cause is the issue with IGMP and my modem/router, but with that version at least the communication was kind of working... Don't know until what version is "working", but in any case was not usable.

This just to let you know the reason why I uninstalled the first time.

hakana commented 5 years ago

We working on this issue together with the Shelly team

Boogs77 commented 5 years ago

Hi Hakana. A couples of days ago, I have noted one thing. After a router rebooting my shelly start to work again just for a couples of minutes.

hakana commented 5 years ago

Try igmp_fix: true and see if that helps

Boogs77 commented 5 years ago

I've tried but no changes!

uaparac commented 5 years ago

This version 0.1.0 does not work for me.

Misiu commented 5 years ago

We working on this issue together with the Shelly team

any updates from the Shelly team? I've just added igmp_fix: true and will check if this will help.

SuperCocov9 commented 4 years ago

Having the same problem, i can get remote acces hakana. intemo eg200 router

Misiu commented 4 years ago

@SuperCocov9 try steps described here: https://github.com/StyraHem/ShellyForHASS/issues/69#issuecomment-548322267 check ping, add igmp_fix: true and increase unavailable_after_sec it helped in my case.

SuperCocov9 commented 4 years ago

@Misiu now i am getting this xD Error fetching data: <PreparedRequest [GET]> from http://192.168.1.221/ failed with HTTPConnectionPool(host='192.168.1.221', port=80): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x6d12f8d0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) Conexión perdida. Reconectando...

Misiu commented 4 years ago

@SuperCocov9 add ping sensor:

binary_sensor:
  - platform: ping
    host: 192.168.1.221
    name: Shelly
    scan_interval: 30

it looks like HA can't make a request to Shelly. Check what IP does the Shelly device has, You can do that in Shelly app. Also, set a static IP for the device, this might help.

SuperCocov9 commented 4 years ago

@Misiu nevermid, that error was a crapy sensor i wrote for a shelly ht, still cant get shellyforhass working in any way, my cover and a switch appears as "not available", just that.

Misiu commented 4 years ago

@SuperCocov9 I had the exact same problem. Are Shelly devices always "not available"? add unavailable_after_sec to configuration.yaml and set its value to 180 (the default is 60)

SuperCocov9 commented 4 years ago

@misiu did it, rebooted, even the router, dame result...

Misiu commented 4 years ago

@SuperCocov9 sorry, can't do more. I'm still new to HA and Python. I just described the steps that helped in my case. It looks that we must wait for the next version of this integration. Hopefully, someday we will be able to use MQTT and Shelly cloud together. Write to Shelly's support about that (I did). Maybe if they get a lot of requests they'll implement this feature :)

chemelli74 commented 4 years ago

Hi,

I have the same issue as other users above.

Is there a way to add Shelly based on IP instead than discover them ?

Thank you,

Simone

errecla commented 4 years ago

Hi,

I have the same issue as other users above.

* test.py in homeassistant docker image: no go

* ShellyAdmin.exe (v1.0.0.28) on the laptop, perefctly detects the Shelly.

Is there a way to add Shelly based on IP instead than discover them ?

Thank you,

Simone

Ciao simone, are you in Italy and are you working woth Vodafone Station? I do and I have your some problem. I think that problem colud be Vodafone Station. Claudio

chemelli74 commented 4 years ago

Ciao simone, are you in Italy and are you working woth Vodafone Station? I do and I have your some problem. I think that problem colud be Vodafone Station. Claudio

Hi Claudio, yes I'm italian and I have the Vodafone Station. On my wndows laptop, multicast works like a charm so it should not be a network problem. The issue is more related to docker that seems to not allow multicast. I'm investigating.

Try the following exe, http://uniqhost.de/ShellyAdmin/setup.exe, and report back if it works for you.

Ciao,

Simone

chemelli74 commented 4 years ago

The issue is more related to docker that seems to not allow multicast. I'm investigating.

Seems more related to the NAS Synology itself. If i ssh on it and run the test, nothing happens.

Simone

hakana commented 4 years ago

Working with a version that can work without CoAP also, it will do polling and allow to add devices by ip.

chemelli74 commented 4 years ago

Working for me since 0.1.3b1.

@woody4165 is that true also for you ? If so can you please close the issue ?

Simone

chemelli74 commented 4 years ago

Hi all, just to inform that after 3 weeks of inactivities on very old thread, I'll proceed to close them. If later one someone verify that the issue is still there, a new issue need to be opened.

Thank you,

Simone

chemelli74 commented 4 years ago

No update for 21 days, closing

Simone