larryllix

We have further discovered that Alexa constantly makes mistakes on event times. I had an appointment yesterday at 10:45 AM and despite Alexa confirming the correct time each attempt, she logged the appointment in my google calendar at 2:00 PM 1:45 PM 1:00 PM on three separate attempts, one three weeks before, one the previous week, and once the previous day. This is making the event keeping by Alexa, untrustworthy, and therefore, useless. The times are lied about, and the dates are changed from the initial confirmation, to the final confirmation, during the same creation session. The dates seem to be a problem attempting events outside of the next week, further into the future. Alexa substitutes the same day of the week in the closer week. This has become regular occurrence now and all event bookings have to be checked with another method. When discovered to be incorrectly booked, a second and third attempt sometimes results in the same error.

2:00 AM happens twice in the same night, each year in the fall time change.

We have been finding the event handler making mistakes more frequently. You set an event for a certain date, then Alexa confirms the date and asks for time and description. The last thing Alexa does is repeat it all back to you, for final confirmation, but with a date one week earlier than confirmed previously. This is very annoying and sometimes it take five or six tries to make Alexa confirm the correct date, without subtracting a week in time.

Almost every device I have out of about 75 devices ends in "lights" without "several devices" reports anymore. I did have a lot of that until I took out many shorter forms of the names. I had many options for some devices eg. "Kitchen lights", "Kitchen bar lights", "Bar lights" This seemed to confuse the parsing algorithm, as it also finds the same words in a longer vocal phrase. Taking some of the shorter ones out resolve the problem for me. I found the phrasing "Alexa. Turn on xxxxxx" is much more reliable than the verb last, also. Using "the xxxxxx" works just as well as "the" seems to be an ignorable word. I have also found talking above a horizontal line to Alexa's side grills gets a lot of confusion, as well as talking to the corded side, both make her very deaf.

MS units are not capable of sending LowBatt Off, only On. UDI has created a workaround by faking the Off in ISY. See Michel's post above.

Sometimes antenna angle can help penetrate certain RF barriers.

Bienvenue et bon chance, mon ami!

Typically router signal strength is lower from routers on 5GHz and the signal doesnt seem to be reliable as far away. Try your 2.4GHz LAN SSID instead. I am having trouble with mine also and my 2.4GHz band is getting crowded.

Right click on the low battery node in the device tree and select query. It should be set to Off. Note: You cannot query most battery devices. ISY will set the Off sicne the low Batt signal never sends an Off, only an On. I have not found motion sensors to be reliable sending LowBatt signals. The red LED, on the front, will flash multiple times (instead of once) when it sees motion, but that may not be reliable either. When you do the seven tap Dark/Light send signal test you must change the level each time. If it was dark last time and still dark no change will be seen. You must alternate dark/light, wait 3-5 seconds, and then seven taps, each test.

Maybe. I have had to factory reset one thermostat 8.or 9 times before it would link properly. I would not give up yet, and factory reset it. Then use restore.

The links can change who it talks to but flashing is an internal firmware problem and shouldn't be link related.

IIRC he would need V5 for nodelink also.

You are looking for solar noon, which most PV fans are familiar with. Your formula is right on, but you will find it never varies, season to season. The longitudinal angle of the sun is always the same for the same time of day while the latitude angle changes. Calculate it once and use it for a time trigger. For DST you may need to use a seasonal condition or two programs based on calendar calcs. Easy in v5.

Just right click on the device and select Restore. Sometimes there is a link that is temporarily changed. Don't understand it completely, but it doesn't cause problems. Restore will fix it, even if just for looks.

No. Stu is attempting to lead you through a diagnostic process to find the problem,not for keeps. and... are all your jumpers on only one pin except for the number 5 pins? I don't think MSes have beepers in them.

V5.x has been out for over a year but all versions are in alpha release status. They have bugs. None combine protocol scenes yet. If you have no Zwave, v5.0.4 or v5.0.7 well with minimal problems

Different brand protocol devices will never actually interact, as in Insteon scenes. ISY 'combination scenes' will just be hidden programs, called scenes or some other label.

I flash a corner bulb red while the garage door is open. If the lights go out and my bedroom light goes on I flash it full brilliance until the garage door is closed If the car leaves I send notifications.

No but Hues do not have scenes in ISY as they are not Insteon. Scenes can be operated from programs and so can NRs

You trigger a program that turns on the scene and send out NRs also. I use a variable with a bank of programs, each triggered off a different value in the state variable. Value = 0 = off Any program can stuff a value into the variable and it all happens behind the scene automagically. After flashing a bulb or any temporary usage of a bulb or LED strip the whole room can be reset back by restoring the value to the variable in a few lines of ISY code. Your dup post can be deleted.

Zones will be normally closed electrical loops for security of system detection If you have no device connected you may need to short out the input or bypass the zone in the setup.

Sorry I told you wrong. Do NOT use the linking mode. Tap the same button, 7 times quickly, and the MS will send the dark/light report immediately and it will not need the 3 minutes to adjust to the dark and light. You will see any change in the Admin Console on the dark sensor.

Put the MS into linking mode again. Now tap the same button 7 times quickly and the MS will send the dark/light report immediately.

Many companies do that, especially on ebay and aliexpress adverts. It's just plain scamming using people's confusion and lack of knowledge against them to sell product. Who is going to take them on legally, when they live on the ther side of the world.

This may be a weak communications problem. Place a dual-band device (like OnOff or LampLinc) close to the motion sensor and try again. bon chance!