Graeme Miller

I am getting this also. I know that the state is 'None' and I see that the icon colour is set as expected but the Secondary info is blank. Also,...

I have this error too, occurring every few days and I note previous posts on [HA Community](https://community.home-assistant.io/t/texecom2mqtt-texecom-alarm-panel-and-mqtt-integration-with-ha-support/219354/606?u=hunterdrayman) about it. Would it be possible, please, to revert the behaviour of texecom2mqtt...

Thanks - might be just what I need.

In case anyone needs the Node-RED equivalent  `[{"id":"23254f671972abaa","type":"debug","z":"7e84ab06f46c8a03","name":"texecom2mqtt stopped","active":true,"tosidebar":false,"console":true,"tostatus":false,"complete":"\"The texecom addon became unavailable. Attempting restart.\"","targetType":"jsonata","statusVal":"","statusType":"auto","x":490,"y":440,"wires":[]},{"id":"39ec83dce9f97913","type":"api-call-service","z":"7e84ab06f46c8a03","name":"Start it","server":"82070ffe.b97dd","version":5,"debugenabled":false,"domain":"hassio","service":"addon_start","areaId":[],"deviceId":[],"entityId":[],"data":"{ \"addon\": \"c15a2434_texecom2mqtt\" }","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":430,"y":500,"wires":[[]]},{"id":"6097cfd23c08ee70","type":"poll-state","z":"7e84ab06f46c8a03","name":"Texecom2MQTT unavailable","server":"82070ffe.b97dd","version":3,"exposeAsEntityConfig":"","updateInterval":"15","updateIntervalType":"num","updateIntervalUnits":"minutes","outputInitially":false,"outputOnChanged":true,"entityId":"alarm_control_panel.texecom_alarm","stateType":"str","ifState":"unavailable","ifStateType":"str","ifStateOperator":"is","outputs":2,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"}],"x":160,"y":440,"wires":[["23254f671972abaa","39ec83dce9f97913"],[]]},{"id":"82070ffe.b97dd","type":"server","name":"Home Assistant","version":5,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true,"heartbeat":false,"heartbeatInterval":30,"areaSelector":"friendlyName","deviceSelector":"friendlyName","entitySelector":"friendlyName","statusSeparator":"at: ","statusYear":"hidden","statusMonth":"short","statusDay":"numeric","statusHourCycle":"h23","statusTimeFormat":"h:m","enableGlobalContextStore":true}]`

I am getting this too with 20 cores on twin Xeon x5675s and 12Gb of memory. This btop screen dump suggests it's CPU bound and that disk & memory aren't...

Just for a laugh I asked Google Bard how many cores are needed to run a 7B model: > A 7B model like Alpaca would need a cluster of multiple...