Choose style:

Recent Posts

Pages: [1] 2 3 ... 10
1
Almond+ / Re: Almond+ AP and Static IP
« Last post by exboxnick on September 24, 2018, 11:02:27 pm »
Ok, I've done my homework (after forgetting all about this, sorry). In red is what the default DHCP assigned IP address is via my main router, and this is already configured in AP mode with separate WiFi names setup. for configuration's sake, I'd like to keep any AP and switch above a .240 IP address on my home network for ease of remembering which is which. See below, and compare times if you'd like, they were run simultaneously to show that for a moment, it did recognize the newer IP, and then it reverts back to the old .22. I have even tried manually assigning through my main router via MAC, no success.

C:\Users\%username%>time
The current time is: 21:57:37.64
Enter the new time:

C:\Users\%username%>ping 10.0.1.22 -n 50

Pinging 10.0.1.22 with 32 bytes of data:
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.1.250: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.1.22:
    Packets: Sent = 34, Received = 29, Lost = 5 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C

C:\Users\%username%>time
The current time is: 21:57:34.33
Enter the new time:

C:\Users\%username%>ping 10.0.1.250 -n 50

Pinging 10.0.1.250 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.

Ping statistics for 10.0.1.250:
    Packets: Sent = 21, Received = 17, Lost = 4 (19% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
2
Almond 3 / Re: Almond 3 locks up with blank white screen
« Last post by Ohiomedic on September 23, 2018, 10:52:12 pm »
The past couple of weeks Iíve started having this issue. It seems to be happening about every three days. Iím thinking of jumping ship to a SmartThings hub and router. The last firmware update was in March. Also the seem to jump ship on a product as soon as they bring out a new one, same thing seemed to happen with the A+.
3
Almond 3S / Re: Unable to get Z-Wave working on Almond 3S
« Last post by Tokyo on September 23, 2018, 01:27:31 am »
If you look at the conformance statement for both products, you can see that the devices to not list any controlled or supported command classes. It is up to the Z-Wave controller as to which command classes are supported; in this case the Almond 3 and Almond 3S. The Almond Plus has a built-in z-wave chip and been certified by the z-wave alliance and its conformance statement lists the command classes. While theoretically, the combination of Almond 3S and z-wave dongle could go through the certification process, this seems not to be the case.

Yes, the Almond does support command classes and I suspect at a minimum the command classes supported by the Almond Plus, but it is very well possible that they support more command classes and newer versions of the command classes.
4
Almond 3S / Re: Unable to access local / web interface on Almond 3S
« Last post by Tokyo on September 23, 2018, 01:19:14 am »
The web interface is enabled. It works in router mode, but not in access point mode.
5
Almond+ / Timers?
« Last post by mrmmc on September 21, 2018, 10:35:47 am »
How to create timers ? I need timer for light control

And... if I choose wrong zwave type how to change ?
 Or reset and new Connect?
6
Where can I buy sensors? / Re: Securifi sensors now on sale on Amazon
« Last post by Erwan on September 20, 2018, 01:23:42 pm »
is there any one who have this type of sensors and buy it because it is needed for me and  i searched the price in the amazon which is very expensive for me so if you have sell it
7
Almond+ / Re: All devices show up as inactive
« Last post by Shazster on September 19, 2018, 08:11:00 pm »
One of the reasons I gave up on Almond+. The active/inactive device list has never been accurate. Always-on devices on Ethernet connections would show as inactive when clearly powered on.
Moved my A+ to AP duties and my A2015 is now a repeater.
8
Almond+ / Re: Almond+ AP and Static IP
« Last post by exboxnick on September 19, 2018, 05:00:35 pm »
You can set a Static IP for AP mode using the web GUI.
Edit: finally remembered to check this...it is:  Web GUI -> Advanced -> OpenWRT -> Interfaces -> LAN submenu (or just click edit if you go into Interfaces)
I have not actually done this, but it provided entries to set the IPv4 and IPv6 info.

This doesn't actually work. I mean, it does, but then it defaults back to what it was originally. I have configured on my main router a MAC assigned IP and even that doesn't work after a reboot of the Almond+. I have run 2 continuous pings to the old and new IPs and I can watch the changeover happen, and then it reverts back. I have timestamped tests to show them done simultaneously.

I might hard reset my Almond+ and see if as I configure, it'll just automatically assume that IP, or change it into router mode, set it up, and then convert back to AP. Either way, I'd still use it for ZigBee and/or ZWave regardless if Wifi works.

But whomever said it earlier was right, with another AP configured, I had no problems configuring to be static IP for this AP. All devices are either MAC assigned or statically configured. I can post further details later if needed.
9
Almond+ / Re: All devices show up as inactive
« Last post by pdxsk8r on September 19, 2018, 04:24:37 pm »
Surprisingly all my active devices showed up as active again about 2 weeks ago, and I didn't do anything new.  Previously, I tried power cycling and it didn't help.  I didn't upgrade firmware.  So my auto-away and auto-home rules weren't functional for over 2 months and I was not getting alerts about doors getting opened while away and now they work again.  That's a little unsettling.  I just got an Almond Guard in the mail; I hope it doesn't have the same issue.
10
Peanut plug / Re: Opinions on the plug
« Last post by mparadis on September 19, 2018, 02:41:04 pm »
The control is all in the hub but the hub doesn't need to be connected to the internet for its scheduling. Any mains powered zigbee device in between the two should work.
Pages: [1] 2 3 ... 10

Page created in 0.048 seconds with 13 queries.