NOOOOoooooooooooo..........

Experiencing that the controller was not seemingly getting data reliably from some nodes, I tried to up the GW power from LOW to HIGH. I reflashed the GW last night and set it all back up.

This morning I find the spikes and ghost nodes are all back, along with long periods where node data is not presented on the dashboard.

I have now cleared the GW eeprom and reflashed again with LOW power, just to see what happens. I have rechecked all connections and will see how it goes.

If the issues continue I will re-enable all those DEBUG's and let you know.

@jkandasa After nearly 4 full days without issue I have returned the settings as suggested.

Whilst I am very happy that it is back working again, I guess now we will never know what exactly caused the issue or if it is likely to happen again (to me or others).

For V2.0 you might like to think about a page in the settings area with radio buttons to set the 'INFO' / 'DEBUG' etc parameters. Would be easier, especially for people who are new to linux.

@jkandasa

You will be happy to know that this issue is now SOLVED!

Since installing the latest SNAPSHOT 1.4.0, all the problems associated with this have gone away. It has all magically gone back to normal.

So no more spikes, dropouts, ghost nodes, or lockups. I am very hopeful again now!

Cheers!

@jkandasa

You will be happy to know that this issue is now SOLVED!

Since installing the latest SNAPSHOT 1.4.0, all the problems associated with this have gone away.

Thanks for all the contuning support and excellent work.

@jkandasa

You will be happy to know that this issue is now SOLVED!

Since installing the latest SNAPSHOT 1.4.0, all the problems associated with this have gone away.

Phew, what a little sod this problem has been, but we never gave up and all is well now.

Big thanks!

@skywatch I couldn't find a usb converter so I ordered a couple just in case.

FWIW I also added a temperature controlled 20mm fan to aid the cooling of the pi. Even with the big heatsink posted earlier in this thread, you can see the difference when the fan is activated.

I only used 4 components to make a fan controller that works with a python script to control the speed according to cpu temperature - so virtually noiseless in most circumstances.

Oh, I may have some news about this issue tomorrow as well....... (Queue suspence music from 1950's horror/scifi movie).....

@jkandasa I will try and replicate this tonight/tomorrow and send you the log.

So today I notice that the bmp280 (which presents only Temp, Hum and pressure (inc forecast) now also seems to have variable types HVACsetpointheat and Unit prefix.

I'd like to delete the erronous variable types but can't see a way to do this without deleting the whole sensor (and losing months of data collected by it).

Is it possible?

@jkandasa said in 1.3.0 and 400:Bad Request:

I hope we have some issue in the code. For good message, it says as bad.

That's what I thought. I am now using latest 1.4.0 snapshot FYI.

Trouble is that sometimes when this happens it resends the command. My amplifier only has one button that toggles the power on and off, no descrete commands. The result is the amp turns on and off and on and off and on and off (You get the idea and how annoying it is).

@jkandasa

I notice that whatever colour I choose in settings>metrics, I don't see it in the graph. Should the colour for temperature set in metrics be displayed on a mixed sensor graph?