Indigo Domotics

Autolog

Any insight to the following issue.

Went on holiday everything working fine - while away Nanoleaf went offline - just stayed on for the whole 2 weeks would not respond to Indigo or Nanoleaf App.

Came back and did a full reboot and reset Nanoleaf - re; inked to Nanoleaf App.

Now all looks Ok


Except if I try to turn On or Off etc


The IP address is correct and unchanged - fixed IP address



Then I get this error...

Code: Select all

Nanoleaf                        sent "Light Art" off
   Nanoleaf Error                  Problem turning OFF the device 'Light Art': HTTP Error code 400 unknown

Odd thing is that the Nanoleaf Plugin doesn't seem to discover any Nanoleaf devices but does let me change the brightness from within Indigo

from the Event Log

Code: Select all

 Nanoleaf                        sent "Light Art" set White Level to "0" and White Temperature to "4000"

So it is finding it and working, albeit only partially.

Any ideas?

There are no available Nanoleafs because it is already setup.

Not suggesting you do this but if you deleted it (the Indigo device) you would then find one available.

Have you tried pressing the authorise button? I think the authorisation code will have changed as you reset the nanoleaf.

Thx

Yes I had re-authorised .. so not that.

I'll delete it and start over.

Ta

OK deleted it.
Shut down plugin restarted it.

Added Nanoleaf Device
Model - Nanoleaf Device


Can't add IP address
MAC address etc


Buttons Update and Authorise have no effect.

So can't get it to work - related to forward update last week?

Busta999 wrote:

... So can't get it to work - related to forward update last week?

OK - I will try and look at it tomorrow.

What do you mean by "related to forward update last week?"?

Sorry autocorrect got the better of me.

The firmware update that came out last week.

I should have figured that out!

Done a quick bit of digging and it appears the API was changed or more particularly the old API (which was deprecated post beta) has now been removed. The Plugin, I think, is using the old beta API. I will check it out tomorrow PM as I am out in the morning. It should be fixable.

Excellent

Thanks


Sent from my iPhone using Tapatalk

A new pre-release is available on Github: Nanoleaf Controller (Version 1.3.0)

The firmware seems to be changing by the minute - latest update to 3.1.4 released this afternoon.

I have tested with the latest firmware and it works AFAICS. I have done a re-discovery and again that works.

If you update the firmware, the IP address may change and you will have to re-authorise - you need to press the power button on the nanoleaf for 5-7 seconds to be able to reauthorise it.

Let me know how you get on.

OK installed latest version from GitHub


On install got this

Code: Select all

Stopping plugin Nanoleaf (pid 32380)
   Nanoleaf                        Autolog 'Nanoleaf V1 Controller' Plugin shutdown requested
   Nanoleaf                        Stopping 'Light Art'
   Nanoleaf                        Autolog 'Nanoleaf V1 Controller'  Plugin shutdown complete
   Stopped plugin Nanoleaf
   Upgrading plugin Nanoleaf to newer version 1.3.0 (previous version moved to trash)
   Loading plugin "Nanoleaf 1.3.0"
   Starting plugin "Nanoleaf 1.3.0" (pid 4791)
   Nanoleaf                        Autolog 'Nanoleaf V1 Controller' initializing . . .
   Nanoleaf                        Host IP Address overridden and specified as: '192.168.1.10'
   Nanoleaf                        No monitoring or debugging requested
   Nanoleaf                        No monitoring or debugging requested
   Started plugin "Nanoleaf 1.3.0"
   Nanoleaf                        Initialising to poll at 300 second intervals
   Nanoleaf                        Autolog 'Nanoleaf V1 Controller' initialization complete
   Nanoleaf                        Starting  'Light Art' . . .
   Nanoleaf                        Discovering nanoleaf devices on network - this should take ~30.0 seconds . . .
   Nanoleaf                        . . . Started 'Light Art'
   Nanoleaf Error                  Discovering nanoleaf devices failed: Socket error while setting up host '192.168.1.10' discovery of nanoleaf devices!: [Errno 49] Can't assign requested address


So did an update and got

Code: Select all

Nanoleaf Error                  Error in plugin execution UiAction:

Traceback (most recent call last):
  File "plugin.py", line 904, in updateIpAddress
KeyError: (u'C1:74:0F:1D:5A:7A',)

 

Then did an authorise - and after pressing On button on Nanoleaf for 6 seconds it all started working again

Thanks for fixing it!!

Very much appreciated

OK - Thanks for testing and the the report and pleased that it is now working for you.

As it is working for you and as I didn't have any time allocated to look at the nanoleaf plugin - I will record the errors reported and look at them if I get any spare time.

I will now make this an official release.

I'm getting something similar to this issue above. Running version 1.40

Code: Select all

Nanoleaf Error                  Problem setting the effect on the device 'Indicator': HTTP Error code 400 unknown

The odd thing is that the device will reconnect and go back to an up status in Indigo.

I have three Nanoleafs, and only one of them has this issue.

Different Computers wrote:

... I have three Nanoleafs, and only one of them has this issue.

Are they all on the same Nanoleaf firmware version and what version(s)?

Two are older triangle sets, running 3.3.6. One of these has the issue.

One is a Canvas, running 5.01.

All three are listed as "up to date."

Different Computers wrote:

Two are older triangle sets, running 3.3.6. One of these has the issue.

One is a Canvas, running 5.01.

All three are listed as "up to date."

I am not sure there is much to go on there then.

Is it a particular command that is causing the issue and if you try it on one does it work and the other it doesn't?

As I mentioned in another post, my triangles are misbehaving and not connecting reliably. The Canvas is OK. So it makes it difficult for me to test but I will see if I can reproduce it but am not optimistic.
Basically, I had "retired" my triangles as they are more bother than they are worth at the moment.