Geoff Berl

I noticed this as well, my thought was to put a date stamp comment in the code. To elaborate, before it's exported, modify the first line in the code to...

Another option, while very involved, would be to modify the entire exporting function to, rather than use the official VBA module export function, use a file stream. This would also...

Okay, I'll try to clarify The add in would (when exporting any object) add a date (exported date) to each object's code (in the first line). When running export again,...

> If you > manually updated the VBA outside of Excel that could happen, but again > you'd need to remember to manually change the date stamp. > NealHumphrey Not...

Personally, I follow the method described here, although I do not use release branches, I work on Dev to fix bugs and add in features planned for the next release,...

I can't seem to find anything that would cause this that we might have direct control over. An ugly but functional work around would be to add a class object...

Update, I had a hunch that it was related to the usage. I only turned the microwave on briefly to confirm that was the circuit. So I thought maybe it...

It was probably about 10 minutes between fixing the connection, opening the Emporia app and seeing the sensor, before I reloaded the integration. When that didn't work I restarted HASS,...